I’m trying to set up a “My Jobs” list on my home screen so that users can have a custom view of their upcoming jobs. For some reason, when linking a button to save a job to the list, I can’t seem to reference any other row than the first row on my jobs data sheet. How do I go about referencing the second, third, fourth rows and so on?
You can use a Single Value->Whole row column, that takes N from start (or end). This requires that you know the “row number” of the row you want to link to.
Another way is to use a Query column, and apply one or more filters that cause it to only match values in the row you’re interested in.
Yet another way is to create a single relation, matching a value in the current row with a value in the target row.
All 3 of the above essentially give you the same result, and you can use a Set Column Values action to change a value in the matched (linked) row.
If we go back to your initial screen shots, I see that you have a table with a list of Jobs.
Then I see what looks like a details screen, with a Text input component and a Button.
I’ll assume that screen is attached to the first row in your Jobs table.
Keeping what you have there, you would need to target that Text input at a User Specific column. That column can either be in the same table, or it can be in your User Profile table. Either way works. What you then need to do is create a Single Relation column that matches the user supplied Job number with the Job number in your Jobs table. You can then use that relation in the action on your Button. Assuming you want to navigate to the Details screen for the selected Job, the action would be “Show Details Screen”, and the target will be the Single Relation column.
All that said, you are relying on a user knowing the exact Job number. Wouldn’t it be simpler to present a list of Jobs as a collection, and allow the user to navigate to any job just by clicking on the Job collection item?
My apologies, I appreciate it’s not clear from the screenshots but the “Go to Job” button will take the user to a specific screen where there is a button to add that job to favourites.
The reason that the user has to know the job number is to reduce the possibility of them accessing jobs that aren’t theirs.