Thank you for your post.
I am unable to replicate the issue. This is what I have done:
1. In FileMaker Pro 12.0v5 under Mac OS X 10.9.2, I created a database (12a.fmp12) with three text fields: Name, Address, CSZ
2. I created a script "Script created in 12" that contains the script step:
Show Custom Dialog [ "Dialog with OK and Cancel" ; "There should be 2 buttons, OK and Cancel" ]
3. I execute the script to confirm that both OK and Cancel are displayed.
4. I close the file, launch FileMaker Pro 13.0v1, and open the database file (12a.fmp12).
5. I run the script to verify there are two buttons.
6. I go into Manage Scripts, edit "Script created in 12", copy the script step to the clipboard, and close the script.
7. I create a new script, "Show Dialog pasted from clipboard", and paste in the script step. The script is then saved.
8. I execute the script, and the dialog box appears with both buttons.
Let me know what I'm doing differently than you so I can replicate the issue.
Your process is a little different than mine.
I have a database - ProdV12 which is V12. I have copied ProdV12 to ProdV13 and open ProdV13 in Version 13. With both versions open, I copy the script step from V12 and paste it into V13.
I have attached a screen shot of V12 and V13 side by side (V12 on the left), and what the details of the dialog look like when I show them on both versions.
I do run FORMATMATCH on my system, but I disabled it and the results remain the same.
I have another Mac Pro that has 12.0v3 and 13.0v1 and when I tried to copy this script step on it I found the same problem.
I am able to replicate the difference on both Mac OS X 10.9.2 and Windows 7. I have sent your posts along with my findings to our Development and Testing departments for review. When I receive any feedback, I will let you know.
Since FileMaker Pro 13 reads FileMaker Pro 12 files, is there a reason why you would have both applications open? Just curious.
I have both versions open as our production environment is still on V12. We have frozen development in V12, however we continue to apply bug fixes. Our V13 development needs have to have all the bug fixes applied to it so that when it does become production we aren't recreating the wheel.
We found a serious issue in our handling of backorders as it relates to linking already posted vendor invoices. i.e. the invoices were not being properly linked to the backorder, just to the invoiced portion of the order. Normally the backorder is created before the vendor invoices arrive so this issue has been present for years, but needed to be addressed. As the changes to the backorder script were extensive, the simplist means to apply it to development was copy the script.
As far as I know there is no such thing as "migrating" a file from 12 to 13. Maybe I'm missing something but this thread makes little sense to me. Are you saying a certain aspect or feature worked with 12 but fails in 13? Are you saying you have "12" files and "13" files? How? Not being sarcastic here. Just curious.
I'm saying I have a solution that is in production in V12 and the same solution is being enhanced for release in V13 (i.e. has features unique to V13). Once our current business cycle is complete (June timeframe) we will upgrade all our clients to V13 and switch over to the V13 release. In the mean time, any fixes that get applied to V12 need to get applied to V13.
If I take a script in V12 today and copy and paste a portion of the code into another script it works. If I take that same code and paste it into V13 the custom dialog step gets corrupted - it loses it buttons.
Sorry. I still don't understand what you mean by "paste into version 13".
V12 is our production environment (clients and server). Using V12 I apply maintenance to a script in say DB_v12_97. I copy the script contents to the clipboard. I startup V13 and open DB_V13_97 (started as DB_V12_97, but now contains V13 specific elements). I open the applicable script and past the clipboard. This copy gets a corrupted custom dialog.
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.
Thanks" I see what you mean.