Get( ModifiedFields ) doesn't work when using Replace Field Contents[ ] (4 Comments)

Issue report by Jeremiah Hammond

Product

FileMaker Pro

Version

13v5

Operating system version

OS X 10.10.2

Description of the issue

Get( ModifiedFields ) in a calculation field in the current table returns blank when doing a Replace Field Contents[ ] across a found set. I would expect the function to keep track of each individual record's modified fields as Replace Field Contents[ ] goes through each record in the found set. It should work like other record-specific Gets, like Get( RecordOpenState ) or Get( RecordModificationCount ).

Steps to reproduce the problem

Do the following all in the same table:

1. Create a regular user-modifiable field, like a first name field, age field, whatever you want.
2. Create a modification timestamp.
3. Create a text field with an auto-enter calculation that'll trigger when the modification timestamp changes. Have this auto-enter do something easily identifiable when Get( ModifiedFields ) is blank versus when it returns something. Here's an sample calc:

Let( [ trigger = modTStamp ] ; If( not IsEmpty( Get( ModifiedFields ) ) ; "It works!" ; "Uh oh" ) )

4. Get into a found set of a few records.
5. Type a value into the user-modifiable field.
6. Commit the record.
7. Click into the user-modifiable field and do a Replace Field Contents[ ] to apply the current record's value to the rest of the found set.
8. Notice the auto-enter calc you made in step 3 says "Uh oh" for all records in the found set.

Expected result

Get( ModifiedFields ) in a calculation in the current table should return the modified fields as Replace Field Contents[ ] goes through each record in the found set.

Actual result

Get( ModifiedFields ) returns blank as Replace Field Contents[ ] goes through each record in the found set.

Exact text of any error message(s) that appear

N/A

Configuration information

Get( ModifiedFields ) also returns blank when using Import Records[ ]. It seems the function doesn't work properly when doing a multi-record batch change on the data layer.

Workaround

None.