I've got a powerapps setup for certain requests that our team wants tracked and handled in the application, so I set up a canvas app for input that temporarily has another screen for editing.
Using the built in powerapps templates, the request screen is a pretty simple form using powerapps forms that I added data cards to, and the editing screen is similarly relatively simple, with a table getting data from dataverse and a form for editing. The table are set up as one main table for requests, and then a table of US States (this has two columns, name and abbreviation) that I use a lookup column for in the main table.
Our issues come in when using the lookup column, it seems I can submit things just fine and they show up in the main table with the proper US state, but another individual whom I gave full security access to the main table, and read security access to the lookup table, cannot submit using the form without the lookup combobox clearing and it throwing an error. I'm unsure if this is a permissions error, the app didn't refresh properly, or perhaps something else.
The same data card doesn't show any data in it when trying to use the editing form, nor does it save any changes. It is set to a default of ThisItem.State (the column is called state) with the datafield being the lookup column, the update is set to StateDataCardValue.Selected. The combobox doesn't show anything for the item even though it does have a value in the dataverse table and I have no idea why. I've tried using a patch function similar to how this:
Solved: Save Lookup column in submit form powerapps pos set it up, but it doesn't seem to apply anything no matter what I do. I have a similar issue of the 'Created On' column also not showing any value despite being populated in dataverse, and I've tried many changes to how that data is passed (converting it to text, reformatting the datetime object) but it doesn't seem to show up in powerapps at all.
My workaround for the lookup column is just creating a choice column instead, but I figured I'd ask for other workarounds before going that route.
