(This mail was originally part of “FMP8 Max(Table Self:atum)+1”)

A number of records is added within a loop, the records have sequential
dates.

GetAsDate(Max(Table Self:atum)+1) is auto-entered data.
records are committed within the loop, after every “new record”.

When used with IWP, the trick doesn't work; max() never finds new dates
added with this loop. All new dates have the same value.


The internal relation (self) was based on a computation with global storage

When instead a computational field is used without the global storage
option, the records will be found with max(self:: etc) in next iterations.

When running in native mode, I don't see this different behaviour.

Is this a FM bug or a FM feature?