I reported this issue as FMP 12, but can confirm that FMP 13 exhibits the same behavior on both Mac and Windows.
Thank you for the post.
I am unable to replicate. To attempt to replicate, I performed the following steps:
1. File > New Database
2. Created 2 tables: UI and DATA
a. Added "fk" text field to the UI table
b. Added "PK" serial number to the DATA table
c. Added "Name" text field to the DATA table
3. Added relationship from PK ---< fk
4. Added a portal on the UI table's layout showing records from DATA table
5. "Allow deletion of portal records" checkbox not checked
6. Added a button script to the portal row (script is empty)
7. Added 5 records to the portal
8. In Browse, clicked into DATA::Name field in the portal
9. Pressed and held the delete button > clicked the button script
Actual Result: Multiple attempts received no prompt at all.
I tested both the Windows and Mac versions of FileMaker Pro 12 and FileMaker Pro 13. Please let me know if I am missing a step to replicate.
Thank you for your post.
I am unable to replicate the issue. These are the steps I took:
1. I created a table, Names, with the following two fields:
ID (Number - Auto-enter Serial Number)
2. I created a table, PhoneNumbers, with the following two fields:
3. In the Relationships graph, I linked Names::ID to PhoneNumbers::ID
4. In the Names layout, I entered two records: TSGal and mtolman
5. In the PhoneNumbers layout, I entered three phone records with ID=1 (TSGal).
6. In the Names layout, I created a portal into PhoneNumbers, only displaying the Phone field.
7. I created a button in the portal to Refresh Object (Names::ID)
8. I entered Browse and the three portal records display for ID=1.
9. I put my cursor in Names, held down the Delete key, "TSGal" disappeared, and continuing to hold down the Delete key, I clicked the button in the portal. No dialog box appeared to delete the portal row.
Let me know what I'm doing differently than you so I can replicate the issue.
Thank you TSGal and TSFalcon.
Here is what you need to do to replicate this in your file that you created:
1. Instead of creating a button in the portal, click on a field in the portal and change that field to be a button.
2. Then go back into browse mode and click into your Names field and hold down delete and click the field in the portal that is a button and watch what happens - you will see the dialog that will let you delete that portal row.
A button object and a field grouped with a button object (what happens when you use button set up to turn a field into a button) should produce the same results.
I put two fields in a portal. Set up one as a button with "Copy" as a button action and the other was my names field.
If I hold down the backspace key, this clears the name field. So I put the cursor to the far left of all text, held down the backspace key and click the field/button.
This cleared the name field and did not pop up a dialog for deleting a record.
I'm still unable to replicate the issue. I changed the Phone field in the portal to a button that refresh the object Names::ID. With my cursor in Name and the delete key depressed, I click on the Phone field button, and no dialog appears.
In this case you actually have to click on the field into the portal and change that field to be a button (click on the field in the portal and then click format / button setup and change the field to a button).
I was able to replicate following the steps that TSGal outlined as long as it was the actual field in the portal that was a button. Please try it I have been able to reproduce on both Mac and Windows and in both FM 12 and 13.
PhilModJunk - the name field that you are clicking into and holding down delete needs to be in the parent record outside of the portal. then you need to have a field in the portal that is set as a button.
Now hold down the delete button in the name field and click the field in the portal that is set to be a button and volia you can delete the related portal record.
I know it is a weird combination, but I had an end user figure it out and cause all sorts of trouble. I promise if you carefully follow my steps you can reproduce this.
Here is my example file using TSGal's scenario.
I still cannot replicate. I have a primary key field on the test layout so I put the cursor to the left of the value in the field, held down the backspace key and clicked the field that I formatted as a button.
No dialog appears.
I then change the button to do a Refresh Object, held down the delete key and clicked again.
No such dialog appears.
One of our Support Technicians returned from our Developer's Conference and mentioned that he spoke with you. From what I was told, the key to this issue is that the file was created prior to FileMaker Pro 12, updated to FileMaker Pro 12/13, and then the issue occurs. Is that correct?
Yes, in doing some testing at the developer conference we determined that if we created the example file in FileMaker 12 it would exhibit this behavior. If we then upgraded that file to FileMaker 13 it would still exhibit that behavior. However, as soon as the script and layout are edited the behavior goes away. Also, if created from scratch natively in FileMaker 13 the behavior doesn't exist. So, you are correct, the file must be initially created in FileMaker 12 to reproduce this issue.