Thank you for the post.
I am not able to reproduce. To attempt to reproduce, I performed the following steps:
1. Using FileMaker Pro 13.0v9, I created two database “A.fmp12” and “B.fmp12”
2. Made B an external data source of A.
3. Each file has a single layout and created a text field title “Name”.
4. Created a many-to-many relationship between the two files from Name >——< Name.
5. To both files, added 3 records: TSGal (record one), TSFalcon (record two), and Scotty (record three).
6. Made the text field in A a scripted button for Go to Related Record based on the layout in B.
7. Clicked the button in FileMaker Pro 13.0v9 and was taken to the related record.
8. Closed the files and opened with FileMaker Pro 14.0.1
9. Clicked the button in FileMaker Pro 14.0.1 and was taken to the related record.
Since I cannot reproduce, would you be willing to send your example file for testing? If so, check your inbox at the top of this page for the submission instructions.
You are missing a few steps here, in between steps #6 and #7:
Step 6.1. In database B, show all records and switch to a DIFFERENT RECORD than the one you are expecting to go to in step #7.
Step 6.2. Hide database B by pulling down from the "Window" menu to "Hide Window".
Then, you can continue with Step #7.
Please let me know if that causes the bug to happen for you.
p.s. If you take the time to watch the entire video, you will see how to reproduce the bug. Please do not skim the video nor make assumptions about how the bug works. In the video, I clearly show how to reproduce the bug, and I also show how to NOT reproduce the bug.
Thank you for the reply and additional information.
I am able to replicate. This issue is specific to Mac OS X only and does not occur on Windows. Additionally, I forwarded a report to Testing and Development for review.
Great! Thanks, TSFalcon!
Thanks Scotty for pointing this one out !
A question : since it seem to be a refresh issue, i a was wondering what happened in the case where the action is a part of a long script that capture data in variables or export data etc...
I assume all the result would be correct, but "just" what appear in the window not.
Interesting question! I just tested this out by adding one step at the end of the script which sets a field in the related record (the record that wasn't refreshing properly).
And yes, FileMaker does behave properly -- the proper record does get its field set properly, even though it still displays the wrong record on the screen (even after setting the field). So it seems to be just some sort of a cosmetic refresh problem on the screen, since the underlying FileMaker engine is communicating with the proper record "underneath the hood".
Thanks for that.
One more thing : when you tried to work around the bug using a refresh window step, i assume your created a script on the external file where you added a refresh window step and then, on the main file, your main script was performing the external refresh subscript ?
Ah, good catch! I must have been calling the "Refresh Window" script incorrectly before, but you are correct: the "Refresh Window" script step actually works around this bug. If the original file calls a "Refresh Window" script step in the external file, then the proper record is displayed! Thanks! Good workaround!
scotty321 and Fred:
Testing has confirmed the issue and it has been sent to Development for review.
I have also attached the "Refresh Window" option as a viable workaround.
An entry in the Known Bugs List has been linked to this Issue Report. Any Comments/Questions/Suggested Corrections should be posted here or in a new thread. Please do not post such comments to the Known Bugs List thread.
scottworld and Fred(CH):
This issue has been addressed in FileMaker Pro 15.