Ah.
I think you found the workaround for a subtle design flaw. So, I guess the rule is to make up your mind before making your schedule!
😉
Seriously though, I just tested to verify that the I.S. does not dynamically determine the data type of the fields retreived, but rather reads that type at the time the field is added to a schedule. If the data type is subsequently changed, the I.S. checks that and displays nothing if the types do not match. I created multiple fields for the same parameter, each with a different data type to see this behavior.
You could make a wish that the I.S. should dynamically change the type of any fields to that of the data retreived? (This would not always work, since there could be a combination of matching elements and params that were mistakenly programmed some with one data type and some with another....but the behavior would be no worse than today, and in cases such as yours, would be better.
😉 )
Karl
AC 28 USA and earlier • macOS Sequoia 15.3, MacBook Pro M2 Max 12CPU/30GPU cores, 32GB
One of the forum moderators