Non existing column

(1) Share

Report

Posted on by Larifogo

I simply am TIRED of renaming columns of my SP list until this error disappears.

Anyone has better solutions?

The columns have literally THE SAME NAME! Guaranteed it's same, I used Ctrl+C/Ctrl+V, from the SP list itself and from the error notification, nothing works until I rename it into something completely different. Sometimes I need to rename the same column several times until power apps decides to accept a name, but then I go work into another thing within the app (not related to this formula, field or screen) and this error comes back.

Categories:

Error handling

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

WarrenBelz 153,079 Most Valuable Professional on at

Like (1)

Report
Hi @LS-06011411-0

You should not need to rename any columns in SharePoint, in fact it is not a good idea for many reasons to do it. Rather than let SharePoint "match the columns", take a few minutes to write some specific code - I am assuming here that you are updating existing records - if new records leave out the ID field. You will find that this also "future-proofs" your code to some degree.
Patch( 'FUP 2.0', ForAll( COL_DADOS as _Data, { ID: _Data.ID, Field1: _Data.Field1, Field2: _Data.Field2, Field3: _Data.Field3, . . . . . . . } ) )

Please click Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it a Like.
MVP (Business Applications) Visit my blog Practical Power Apps LinkedIn Buy me a coffee

Was this reply helpful? Yes No
Suggested answer

Larifogo 10 on at

Like (0)

Report
Hey!

Sorry about my venting yesterday. I was just frustrated of a whole day fighting the same bug.
Actually, this is a great solution that helped on another list presenting a similar issue. Thank you very much!

About the list from this question, the collection exists to help mass-upload registers into a list, but copying common data between each new register added, so the user doesn't need to type it several times. Unfortunately, I'm not sure this solution would work in that case, but upon further research, I found out that this error happens due to a bad sync of M365 between Power platform and the chosen data source.

Just like you said, the main reason for the error originated when I renamed my columns for the first time (during the list creation). FSR, the change left residual data that caused an internal conflict for M365 to properly identify and work with each column. Usually this wouldn't affect most of the PP functions, but affect badly the Patch function itself.

For future people with the “the specified column '_' does not exist. The function 'Patch' has some invalid arguments” issue just like me, here are my failed and working solutions:

Renaming the column until error disappeared worked partially and only in situations when the new name was completely different from the first one. Even then, sometimes for unknown reasons, it would solve the problem at first, and later come back if the same column needs to be referenced at ANY other part of the app

Deleting and recreating the column did not work because the new column, if it received the same name as the just deleted one (or any of the previous names you may have tried on the solution above), would be treated as the same column by M365 and inherit the same errors as well.

Deleting and recreating the fields and buttons associated with this error did not work, since the problem is not within the app but with the synchronization between PP and the data source.

Deleting and starting a new list was the only thing that completely eradicated this error for me. And no, it cannot be a new list imported from CSV or a new list based on an existing list, it HAS to be blank and populated column by column, otherwise the new list WILL inherit the desyncs from the older one.

Was this reply helpful? Yes No