Hi everyone,I’m working on an app where I have a home screen (Screen A) with a navigation menu linked to Table A. I want one of the navigation buttons to perform the following steps using Advanced Actions:
The first step (navigating to Screen B) works as expected. However, when executing the second step, the “Add New Item” form is shown but it references Table A as the data source of the home screen instead of Table B. This results in a new item being added to the wrong table.How can I ensure that the “Add New Item” form correctly references Table B when navigating from Screen A?Any help or guidance would be greatly appreciated. Thank you in advance!
Forms can add rows to any table. You just need to make sure you set the Target table accordingly within the form. You don’t necessarily have to navigate to Screen B to open a form that writes to Table B.
Thank you Jeff, that was indeed a simple solution.
However, I have one additional requirement:
On Screen B, I have a “Table” component with “Add New Items” enabled, which opens a custom form I’ve already designed. The thing is, when I navigate to the form using the menu approach I initially described, a new blank form is shown instead.
Ideally, I would like to have only one form for adding new items and reuse it in both scenarios. This helps avoid redundancy, potential errors, and importantly, preserves the “slide in” effect when the form is opened.
I haven’t been able to achieve the slide in effect when using separate “Form screens”. Thanks!!
You should be able to change the action for the Add button on the collection to use the same custom action that you created for the button on Screen A. Because of the way you have the action set up, it will still run that extra action to go to the tab that it’s already on, but that shouldn’t be a big deal.
As for Slide In, you configure that on the action itself.
Thank you for your suggestion! Unfortunately, I can’t seem to make it work with just a single “Add New” form, because the custom actions are tied to specific data sources. Since I’m using Table A on Screen A and Table B on Screen B, I can’t select the custom action I want for the form linked to Table B.
Thank you for your help anyway, I really appreciate it!
Ah, got it. I think they used to be a little more ambiguous and not so strictly tied to a specific table.
Here’s another thought. Create a Custom Collection linked to Table B. Limit the collection to only 1 row. Add a button inside the custom collection and you should then be able to link it to your existing action.
