Create Action: Jump to related items form

Hello, users are getting slightly confused on what to do because I can’t quite take them exactly to where they need to go with the click of a button.

I am trying to have a button on a detail screen which says “Add to Collection”, when the user clicks it, it creates a new row in a different table and creates a relation between that item in both tables. This is successful. And currently upon clicking add - I can do all this and send the user to the Details Screen for the newly related item in the new database.

What I cannot get to work is to open the form for that new item in the same action. Can anyone provide a how to?

To summarize:
User views item A’s detail screen on Table A.
User clicks button which triggers action.
Action creates Item B on Table B and a relation to that item is added to both tables.
Action still running… User is taken to Item B’s detail screen on Table B.
Needed: Add to action or edit action so that user ends on for screen for Item B.

  • I do not achieve this with making the last two steps of the action being, show detail screen for related it, then open form. It opens the form for Table A.

Thank you.

The “pointer” of Glide is still on table A for the whole action, so it kind of explains why you can’t open a form for table B. May I ask why you need the “form” part of the flow? Isn’t it easier to just have another form button on the details screen of table B, or are they always required to open that form after the new row is added?

If it’s “required”, then I guess an option would be to change the last action to a Show New Screen, and then make that screen a custom form.

1 Like

You could combine the step adding a row in B and adding data into the columns into one:
create a screen based on a single row sheet, open that screen via a Go To action, populate a user specific field with your ID from the linked row in table A, have data entry fields based on user specific columns, let the user fill in all data, let the user press a button “save” (if data are correct) which trigges an action to add a new row with all new data and the ID (from table A) for the relation in one step.

Thanks everyone @christoph @Darren_Murphy @ThinhDinh , I will review your replies in detail and try them out. To answer a few questions and provide more detail:

The user is browsing a database (Table A), then clicking a button which adds that item to their personal inventory (Table B). Once the item is in their personal inventory, it’s data is composed wholly of their own user generated content, with just a relation back to the item in Table A.

The reason I want to go straight to the edit screen is because, when landing on the Detail Screen of their new item, there’s nothing to see, as they have not created any personal data relating to that item yet.

I thought about some Hints or buttons to tell them to add data - which would but I’m not sure when to make them not visible as all the data they can add is optional.

Imagine you are picking a car from a database, and then adding it to your owned cars and can enter all personal data about that car - purchase price, VIN number, condition, color, seller. Essentially thats the function.

I can absolutely just show an edit button (pencil edit is not prominent enough), but I was just trying to make the experience for the user very easy to understand what they are meant to do. Thanks again.

I almost never use standard forms to let users add data because I always check if data are correct and complete. Through the click on the selected car you could open that screen which I mentioned, gather all data into user specific fields and only then add the new row in B.

If you first add a row, you have to get to that row later, which would be possible via a relation and then update the fields with Set Column Values

1 Like

My thinking is you can use just a single form to do this. You write to table B instead, then show all the needed entry fields (purchase price, VIN number, condition, color, seller).

Then in the “on submit” action, you write a row to table A. Does that make sense?