For the parent table, the user opens a form and manually types in the project name. After they save the form, a group action triggers that adds a row to each of the child tables and automatically sets the project name as the one the user entered in the parent table.
And, how is the Key field of each of your child tables set?
You could be facing these problems due to the fact that you’re doing things non-standard. Most systems would simply expose the ref column and allow people to interact with that, instead of kicking off an automation to connecting the after the fact.
One of the beauties of app sheet is that you can do anything, just about any way that you want. However, when you stray away from the yellow brick road you encounter problems.
Generally speaking though… if things are connected together properly using refs, you should be able to simple call the delete action on the child records to accomplish the delete.
It’s all about having those [Related Whatever] VCs on the parent; it’s that list that’s giving you all the child record values
3 Likes
@scott192 - Here are the screenshot of the actions to create rows in child tables. The key column in each child table is Project Name. The formula I am using to set Project Name is [_THISROW].[Project Name]. All these create actions work perfectly. Upon testing, only the Wall Art child row is deleting properly with the parent. The rows from Accessories and Rugs will not delete even if the other sheets are removed.
Action 1: Group (triggered when form is saved from parent table)
Action 2: Create Accessory Page
Action 3: Create Wall Art Page
Action 2: Create Rug Page
Hi Multitech, I love Appsheet because there are so many work arounds in case you go off the straight path. However, in this case, I don’t feel like I have strayed too far off since I am using a standard action to create rows in child tables and there is standard function for those child rows to be deleted through the Ref type…I just think there is a problem with my Accessories and Rug child tables that’s not allowing the rows to be deleted with the parent. The Wall Art child rows delete fine when the parent is deleted.
1 Like
So you don’t have a separate key on each child table then? You are using the Ref back to the master as a Key?
Hmmm…I’ve never heard of doing data like this. I would advise you to add a new column to each of your child tables and name them something like ChildID. Regenerate the structure and use uniqueid() as the Initial Value in your newly added column. Make this the Key of your child table and set the Label to be the Project Name field. Keep the project name field as it is with a Ref back to the master.
See if that works now!
2 Likes
How are you accomplishing the delete? With a bot?
1 Like
This was a great idea, but same result. Only the child row from Wall Art is deleted while the Accessories and Rugs remain. I added a whole new “Test” table and slowly added identical virtual columns to see if that was tripping it up, but it was not - the rows of the new Test table would delete fine. I then deleted the initial table (Accessories) and renamed the Test table and source sheet to Accessories, and then poof the child rows stopped deleting again…it seems like the name of the Accessories and Rugs tables are causing issues, but I can’t pinpoint where.
1 Like
No bot, just using the default “Delete” action on the parent row. The child tables have a “Project Name” column that is set to Ref the “Project Name” in the parent table.
1 Like
SOLVED!!
@MultiTech you beautiful beast! You prompted me to look at the [Related Whatever] columns in the parent table. I deleted them for each respective child table, then saved and let the system recreate them automatically and now all the child rows delete properly.
Seems like the link between the Related VC and the child table got messed up internally even though they were showing correctly. Letting the system recreate them restored the correct relation.
THANK YOU everyone for your time and patience!
4 Likes
Glad you got it solved!
3 Likes
Do you know why this solution only seems to work on records created by individual/account initiating the action? That is, if I click on the action, it only deletes record(s) that I created, but ignores ones created by others - even though the list expression is supposed to filter all matching records.