Single SharePoint column doesn't update when patched by other users

[MacTorqIT]

This will be the first app I've created and developed using PowerApps, and I have been working on this particular app for a few weeks now on contract. I have also been working with an employee of the company who focuses on the business side of development, but has also helped me with a lot of testing.

At this point in time the app is focused around a single SharePoint List called 'Requests'. Because this list contains around 30 fields, I've been asked to break it up into several screens, requiring me to use the Patch function to submit the form.

During user-testing we discovered the 'Sales Rep' Lookup column did not contain the necessary data, which meant we needed to access CDS directly. This was initially an issue as I did not have the permissions required to access CDS, but was fixed when the companies' IT gave me the proper permissions. They also gave the employee working with me the same permissions.

The goal at this point is to give the users the 'Sales Rep' list directly from CDS, then populate several columns in the 'Request' SharePoint list based on their selection (i.e. Sales Rep Name, Sales Rep ID, Sales Rep Territory).

Right now I have added a SalesRepComboBox with it's items set to the filtered CDS list. In the 'OnChange' property of the SalesRepComboBox I Set the three variables required (varSalesRepName, varSalesRepID, varSalesRepTerritory) using SalesRepComboBox.Selected.Territory, etc.

After adding the three new columns (Sales Rep Name, Sales Rep ID, Sales Rep Territory) to the SharePoint 'Request' list (single-line text field) and then adding those fields to the SalesRepForm, I set the 'Default' property of the 'Sales Rep xxxxxxx_DataCard' to varSalesRepxxxxxxxx.

The issue is that this works perfectly for both the 'Sales Rep Name' and 'Sales Rep ID', but not for the 'Sales Rep Territory'. What's strange is that this is only the case for other users - I am able to successfully save the 'Sales Rep Territory' to the SharePoint 'Request' list; the employee I've been working with (who should have the same CDS permissions) cannot, only the Name and ID is saved.

Trying to debug myself, I simply added two Labels to the screen with the 'Text' property directly outputting the SalesRepComboBox.Selected.Territory, as well as DataCardValueSalesRepTerritory.Text (which is populated by the variable set when choosing the sales rep) - this again worked and displayed fine for me, but not for the employee I've been working with.

I've removed the field from the 'SalesRepForm' and re-added it with no luck, and was also able to find and change to a different column in CDS with the same Territory information with no luck (again, I was able to save the Territory information, but nobody else).

This will be my first time posting here as I've usually been able to find an answer to my problems, either here or elsewhere, but this one has me stumped - why does it work for me but nobody else, especially when I'm going through the exact same process to populate the other columns and all of the data is coming from the exact same chosen entity.

Any help would be appreciated, and let me know if anymore information is required.

Thanks,

Logan

[Drrickryp]

Hi @MacTorqIT 

I congratulate you on working with someone to help define the purpose of your app.  However, just from your description, it sounds like you are starting with a flawed design.  Almost no table needs 30 fields and probably should be normalized.  Before you get too deep into the weeds, I suggest you review my post regarding the principles of database design and how to create an app using PowerApps.  Start with https://powerusers.microsoft.com/t5/News-Announcements/Database-Design-Fundamentals-and-PowerApps-An... .    

[sperry1625]

I don't agree, 100%, with those comments.  When working and dealing with SharePoint lists as your data source, normalizing your data model is not always a great idea as SharePoint doesn't handle that very well and is complex to deal with in Power Apps.

Some normalization is possible, but don't go crazy.  SharePoint is not an RDMS so don't treat it like one.

Just my 2 cents.