I have a SP list that I am writing to using a Patch statement in powerapps
I have a Name column of type: single line of text.
I am attempting to write the email address of the current user to the name column using User().Email in my patch statement. I am also writing the current time to a time column with Now(). (There are obviously other columns i am writing to but I even tried creating a button to just write the name and time to see if i could get that to work, it would not)
When i click on the button running the patch statement a new record is created and the time is entered in the time column, but the user email is NOT in that column, it is blank.
Patch(SPLISTNAME,Defaults(SPLISTNAME),{Time:Now(),Name:User().Email})
My column settings are 255 characters and not unique. I can go into the sharepoint list directly and manually enter a record, typing in an email in that column and it does save it.
Interestingly, I'm only having this trouble in my personal sandbox app; our dev app has this same "User().Email" code in a patch statement and I am NOT having issues with, it DOES write the user email to the name column in its sharepoint list. I have compared the code in the patch statement and do not see any differences. the name column in each respective SP list is a single line of text type.
What would be causing an identical patch statement to write all other columns except the name column using User().Email. I have not even been able to write a literal value to the name column with the patch statement. I've even tried setting a label's text to User().Email just to confirm the email is being retrieved (it is), and then writing the text value of that label to the name column in my patch statement and that doesnt work either.
Ironically, writing to the name column used to work in my app, but at some point it stopped working. I have refreshed my data source, i have even removed and readded my datasource to my app. I have not made any changes to the name column on my SPList. I have looked at this on multiple days to hopefully catch something that my tired eyes didnt see before but to no avail.
I guess in my sandbox version (where im trying out various functionality before adding it to our dev app) this is not critical since the name column does work in my dev app, but it's been nagging at me as to why it won't work.
