I'm not sure what you mean by "non-specific ID"? Maybe you mean non-unique ID?
1) AppSheet does have a UNIQUE() function. You simply need to wrap it around a List expression to get a list of unique values. For example, I may want a list of Parent ID's from a Child table. There could be multiple children with the same parent. I would...
Get a list of ALL the Parent ID's from the Child table with this expression:
Child Table[Parent] - where [Parent] is the row key of the parent table
Then to get the unique list of Parent ID's I would use UNIQUE() like this:
UNIQUE(Child Table[Parent])
2) What you have already created - separate Forms and Tables for "Delivery" versus "Dispatch - is exactly the approach you want to take in an app. What you really need now is a parent table that ties together the rows from the two tables. You may already have that Parent table. Once you identify what that parent is and created it if necessary, then you simply need to add a REF column in each of the "Delivery" and "Dispatch" tables and assign them the parent row id that ties them together. This will automatically generate the list of related rows in that parent table for viewing in the app under the Parent row.
The Google Sheets method shown in the video is more for when users access the Sheets document directly. The individual Month tabs and All Months tab is for human readability purposes. In an AppSheet app, we have better ways to present the data for viewing so do not need to structure the data in the datasource for human eyes.
Thank you however I did not quite get the explanation for #1 can we discuss it a little bit more?
For #2 my apologies for the noob question how do I assign the REF Column that I made in the "Delivery" and "Dispatch" Table to tie them together?
For #1, maybe it's best if you show what you have tried and why it didn't work.
For #2 - I made some assumptions that you have a delivery and dispatch row for each order. But, I recognize you could actually have it the other way around - A Dispatch for each Delivery and each Delivery hase multiple orders involved. Again, it's probably better if you explain your current data structure and operational procedure for the rest of us to best help you and prevent confusion.
Hi again willow.
#1 Hope this made this clear I guess I could have structured my question much clearly since #2 will be a prerequisite to this one I have posted 2 video for this since I have realized in the first 1 that I did not show what I tried to do.
Link 1 https://youtu.be/rfq3Y5mPbDg
Link 2 https://youtu.be/f_oRiQqPpKg
#2 My apologies for the Video I was not able to download a screen recorder for my laptop.
User | Count |
---|---|
33 | |
30 | |
30 | |
19 | |
17 |