Unless I've misunderstood something, there seems to be a major and surprising anomaly in Smart Fill, which turns out to be absolutely critical to my client's corporate model.
One can adjust Properties' decimal places okay. HOWEVER one can't reflect this in the Smart Fill criteria! SF can only accommodate a maximum of 2 decimal places! This has completely blown an important model out of the water, because at 2 decimal places, SF is insensitive to critical threshold values.
To illustrate by example: scientifically derived Properties are input as percentages in the present model, to four decimal places (i.e. 98.9999%). This means one needs to select SF criteria to 6 decimals (i.e. 0.989999) - but you can't.
Just in case it's not obvious [politely meant, of course]: the decimal place definition for any SF instance needs to be independently adjustable (i.e. not slaved to a decimal place setting anywhere else), because one might require SF thresholds that are more or less sensitive than the associated Properties.
This is clearly an anomaly, doubtless unintended. Could you please fix it urgently. Even a nice safe beta patch will do me for now!
Thanks as always,
David
London
One can adjust Properties' decimal places okay. HOWEVER one can't reflect this in the Smart Fill criteria! SF can only accommodate a maximum of 2 decimal places! This has completely blown an important model out of the water, because at 2 decimal places, SF is insensitive to critical threshold values.
To illustrate by example: scientifically derived Properties are input as percentages in the present model, to four decimal places (i.e. 98.9999%). This means one needs to select SF criteria to 6 decimals (i.e. 0.989999) - but you can't.
Just in case it's not obvious [politely meant, of course]: the decimal place definition for any SF instance needs to be independently adjustable (i.e. not slaved to a decimal place setting anywhere else), because one might require SF thresholds that are more or less sensitive than the associated Properties.
This is clearly an anomaly, doubtless unintended. Could you please fix it urgently. Even a nice safe beta patch will do me for now!
Thanks as always,
David
London