Interesting, now we have a mystery.
Functionally everything looks good, and you know the small stuff like naming columns correctly which helps a lot. The expressions look fine, especially if they work for all of the other columns. So really all to do is start troubleshooting to see what is happening to the data.
You can go through these things in order to try and find the precise issue.
- Are any of the columns hidden in the Excel file? I see they aren't now, but was someone using the file table hid the columns? That really shouldn't be an issue, but just something to double check while troubleshooting.
- If you run the flow without the expressions does it work? Like just put the dynamic content into the field without checking for empty and run the flow. See if the values appear in the SharePoint list.
- If you run the flow (with or without expressions) and look at the outputs of the Create/Update action, does it show values in the Update/Create item for those rows? Basically trying to see if Power Automate does have values, but then SharePoint is not accepting them. Or if Power Automate is not even getting the values in the field in the first place.
- Would having the number 0 zero in the column be a problem? If you had a number type column, I think zero would be preferred anyways. The coalesce() will take the first non-null value. So if you use coalesce and the Excel field is empty, it will use the string(0), which will then be turned into an integer zero. Instead of using if(empty( you could try the expression below.
int(coalesce(items('Publish')?['ProductLoss'],string('0'))
- I know it is painful, but can you delete the Update/Create item actions; then re-add them? Or honestly I would delete the whole flow and re-create it. This would make sure all of the connectors are completely refreshed Excel and SharePoint. But do not use the copy/clipboard, you would have to literally add new actions and re create them. If you use the copy actions, it could duplicate the problem or cause another issue.
Can you check through some of those bullet points and see if anything changes? Let me know if you see something or anything changes.
(The final test is delete the SP List columns that are causing problems and try again with new columns. If that doesn't work delete everything, SharePoint List and Flow. The file wouldn't necessarily have to be deleted.
I have seen issues where the SharePoint columns are not being recognized by PA and new columns have to be created, and if that doesn't work a new SP list has to be created. This sometimes happens if there are changes being made the SP List and PA kind of bugs and doesn't recognize it. It is not common, but it is something that has happened to me and I've seen others with the issue and that was the solution.)
