New Sharepoint Column Not showing up in Patch Statement - But is showing in other areas

[Powertron]

So as the title, I have a sharepoint list which had 2 columns, <Name> and <Reason for Adding>.  I had a PowerApps list setup to add to these columns, Name from a People Picker and Reason for Adding from a text box.  This worked fine.

I then went to add a third column to the Sharepoint, a choice column.  The idea was to add a Role, and have this selectable from a Choice column.  I have a dropdown in my powerapps form with the following formular in Items :

Choices([@'ServerOrderForm-AdminList'].Role)

This works fine, and I see the following choices in the dropdown when the program is active : 

These are the correct choices as setup in Sharepoint.  If I change these columns in Sharepoint and Refresh the data source, they update in this dropdown.  Happy days, link working fine, right?

Wrong.

When I try to update my Patch statement to include this new column I see the following : 

All the advice I've found for this issue suggests refreshing the data source, or adding and removing the data source.  I've tried this - however even if that did work, why does one part of my powerapps form find that column fine, but another part of it doesn't?  Why does my Patch statement not recognize that there is a Role column there?  I thought it might be because it was a choice column and I needed to do Lookup() instead of just straight patching, but that doesn't work either : 

I've been slamming my head into a wall with this all afternoon, and I really want this win before the weekend 😄

Halp!

[4th8]

I have run into this before. It is rather annoying. Best I can figure it PowerApps has cached the schema for the list and does not check again for the new column. The only fix I have found is to come back to it later and it suddenly works. If anyone has a better option I would LOVE to hear it.

[phipps0218]

You are right it is to do with the caching. What I do is remove the datasourc3 as a connector and re add it. Or force a refresh to the connection by closing and reopening the application.

[Powertron]

I intitally thought it was a caching issue - but surely if it was cache the dropdown box wouldn't populate with the values from the Sharepoint list?  Like it KNOWS that column is there, because its pulling the Choice values from it.

[Powertron]

Also I've now left this over the weekend, which I would consider a reasonable time to "recache" this Sharepoint list, and the column is still not recognized.

[charlie_phipps]

You are patching a SharePoint Choice field?

This does not require a LookUp, you can patch a choice column like this:
Role: {Value: "Administrator"} 

[phipps0218]

You are patching a SharePoint Choice field?

This does not require a LookUp, you can patch a choice column like this:
Role: {Value: "Administrator"} 

[Powertron]

Even when trying to patch it that way the column name is not recognized : 

[phipps0218]

Can you send a picture of the formula but not with the error hovered over it. I think I know the issue but need to see this to confirm.

[Powertron · Accepted solution]

Genuinely not sure if "Dropdown1.Selected" is correct as the Checker isn't getting beyond the column name.  

Edit : I noticed the issue myself after taking a screenshot and checking it.  When adding the "Role:" column I had forgotten to move my "Curly Close" from after the "Title:" column.  With that moved the formula is no longer erroring.