@mgm05e
Well, I'll kind of start from your last point - "0 chance of a user from the wrong group finding there way into the sharepoint list with a link." This is going to be an issue from your app perspective. The app user is going to need access to the lists at least at a read only level. So, there is always a chance that someone can get to those lists.
If you want to address permission and security to records, then you need to look at that from a difference perspective. That of record level permissions - which requires the aid of PowerAutomate to accomplish.
Next, that video is addressing a VERY specific scenario. It is not a common one for all purposes. It is only in the scenario where you have a choice column that you want to group data by.
It sounds like you might be close to that, but you stated you only used this for the purpose of avoiding typos. That is all fine, but how does that translate into how you are displaying records in your Gallery?
Now, in relation to the Choices...when you do get the choices in your app, they will be all of the values of the 50 unique actions you mention. These will not be unique identifiers for records. In fact, quite the opposite, they are broad choices that may represent many records where the choice is selected.
So...I guess to really understand your scenario, can you explain how you are displaying data in the gallery and why choices as the display (beyond the video suggestion)? And, are you using a sub/nested gallery to actually get to the records that match that choice?
I'm just not clear on the stage between your Choices list and the real records in your case.
And, perhaps based on what I mentioned about permissions...this might all be a moot point anyway.
