Are you sure you’re targeting the correct row with your single relation?
If you are using Show New Screen and moving to another table, then you’ll be landing on the first row in that table. So the single relation that you’re using for the Set Columns needs to be matching that row.
No I’m not really sure 
So the Trades table with the button goes to the Input table, which only has one row.
Here is the relation I made from the Trades to the Input table. I’m not sure is the User is the best field to make the relation? There is a relation from the Input to the Trades table as well that I use to transfer the data to the Trades table. But that relation doesn’t appear on the button action. Only the Trades-Input relation shows.
Add a single value column to the trades table and target the RowID from the input table.
Build a “single” relation from the single value column in the trades table to the RowID in the input table.
Now use that new relation in the set column action.
I’ve never used that, but it’s a nice idea.
I’ll generally create two template columns with the current users ID, and use those two to make the relation. But your approach seems equally effective and requires less columns 
Brilliant! It worked perfectly!
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
