@AndyHibbs, the issue with the spinballing file https://the.fmsoup.org/t/fmpa-memory-leak-when-looping-over-large-data-set-with-calculated-field-on-layout/378/33 is a good example why it is valuable to collecting this kind of information. It appears that the ‘Set Field By Name’ step is not the cause but an undocumented type conversion requirement (ref. link above).
I haven’t found any product documentation about the detrimental effect of omitting the type conversion in exactly this context.
So, the venerable ‘Set Field By Name’ can go off the list and ‘Type conversion’ should be on it.
1 Like