The specified column '_' does not exist. The column with the most similar name is

[Mossie]

Hope you can help a beginner folks,

I've connected the power app to a sharepoint list. I'm adding an update button using patch. I'm getting this error message no matter what I try - The specified column '_' does not exist. The column with the most similar name is... So I've reconnected the list, removed and re-added  various lines in the patch function. Still no luck.

Here it is with the column internal names from the SP list.

Patch(
RLCFFF,
DataGallery.Selected,
{
field_3: ddNameRLC.Selected,
field_16: dcName1.Text,
field_17: dcSurname1.Text,
field_6: dcOrgAddress.Text,
field_7: dcEircodeOrg.Text,
DateCompleted: Value(dcDateCompleted.Text),
field_4: ddETBRegion.Selected,
field_5: dcNameOrg.Text,
}
)

Would appreciate if you can spot where I'm going wrong.

Thanks All

[PowerNuggets]

Hi @Mossie 

Try the below, 

Go to List Settings and edit the column definition.  Check the setting for Field= at the end of the URL address.  That is the internal name for the column that you should be using.  Make sure that is what you are using and not the display name.

if this helps solve your issue consider making the post as solved

KR,

[Joel-Garrison]

Howdy Team,

This might not be the case, but also make sure none of your columns have any trailing spaces or characters as well as this isn't supported by Power Apps in SharePoint Lists. I doubt that's the issue, but it's something that I've run into in the past. Also make sure you're using a support Column Type, please see the link below to what I'm discussing with Column Types and Spaces. Let me know if you have any other issues or details you can share.

Connect to SharePoint from a canvas app - Power Apps | Microsoft Learn

[Mossie]

Hi @PowerNuggets 

Thanks for considering.

Yes, I'm using the internal column names only, so that's not the issue unfortunately.

Mossie

[Mossie]

Hi @Joel-Garrison 

There are no spaces or characters. The column types are mostly single lines of text, some choice columns, a couple of date columns, that's it. There are no lookup columns.

Thanks for considering.

Mossie

[Joel-Garrison]

Thanks for the quick response... Can you discuss Fields 3 & 4 with us really quick? What controls are you using for this and what type of data? I just want to make sure you don't need to add a .Value or designate the Type() first. 

Thank you in advance!

[Mossie]

So field_3 and field_4 are internal names of choice columns in the SP list. The corresponding controls in the Edit Form dropdown controls.

[Mossie]

When I look at the fields in the Edit Form I notice that many of them have changed to be of custom type. Not sure why that is. I tried just using one that isn't custom type and it's the same error message.

[Mossie · Accepted solution]

I got a solution from a friend, by placing curly brackets around each line, as follows

Patch(
RLCFFF,
DataGallery.Selected,
{field_3: ddNameRLC.Selected},
{field_16: Name1.Text},
{field_17: Surname1.Text},
{field_6: OrgAddress.Text},
{field_7: EircodeOrg.Text},
DateCompleted: Value(DateCompleted.Text),
{field_4: ddETBRegion.Selected},
{field_5: NameOrg.Text}
)

That seems to have done the trick. Thanks for your suggestions in any case.

Mossie

[Joel-Garrison · Accepted solution]

Love it, that makes sense... but there's still a problem with how it's updating each field one by one instead of all together in one go.

Oh, and I just noticed something else when I looked at your post again. You have an extra comma at the end of this line.

field_5: dcNameOrg.Text, <-- Remove Comma

You should get rid of that comma and see if it makes any difference. :smile:

Commas are not needed for the last item in a table or a record.

It's awesome that you solved it, but give my suggestion a try and see if it follows the "Best practice" better. If not, then no worries, you can carry on. :smile:

~enjoy