SPO List columns are not being recognized by Power Apps (also not internal names)

(1) Share

Report

Posted on by Nuriel

153

Dear all,

I am currently having an issue, that my canvas app does not recognize some few columns of a connected SPO list. I tried using internal names which has worked for me in the past in similar cases, but in case of 1 or 2 columns it says that the column does not exist, both with the visible and the internal name.

I tried refreshing the connected list, removing it from the app and adding it back again - doesn't help.

Any idea what other reason might be behind this and how to fix it?

Thank you!

Categories:

Connecting to Data

All responses (14)

Answers (0)

Nuriel 153 on at

Like (1)

Report
SPO List columns are not being recognized by Power Apps (also not internal names)

I had an idea and went back in and did some testing. Important to know is that I have two sites, let's call it TopLevelSite and Subsite. List where I have problems are all on the subsite.

So I tried the following:

Created a lookup column in the list on subsite which looks up another list on subste -> power apps recognizes column

Created a site lookup column in the TopLevelSite which looks up list on TopLevelSite, added site lookup column to list on subsite -> power apps does not recognize. The list to which the site column looks up is by the way also connected to power apps.

Created a choice or text site column in the TopLevelSite, added site column to list on subsite -> power apps recognizes column

Thus, it seems that specifically site columns which lookup lists on other level sites are not being seen/recognized by power apps in this case as being present in the list at all.
Nuriel 153 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

Yes, I am in fact passing the ID via integrated sharepoint forms to the canvas app. But this is not the reason.

It looks same with ThisItem directly in the customized forms.

And actually just when adding the datacards in the edit forms - it shows the complete list of all columns available in the source list - just except those 7.

One thing came to me - this site and list have been recently migrated from SP 2016 to SP online by our IT. I know that they use Sharegate, but not much than that, since I don't have any insight there.

Is it possible that they broke the columns in some way? I just have not a faint idea, what else it could be and where to look...
mstavra 247 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

Can you show us how varThisItem is created?

Is it something similar to this?

Set(varThisItem, LookUp(YourSharePointList, ID = YourRecordID))

Have you tried using ThisItem.Projekt for testing purposes?

It is possible that this variable is not fetching all your columns because there is no other logical explanation left :)
Nuriel 153 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

I already did this to begin with :(

I checked all internal names of the mentioned columns and they unfortunately don't work either.
Pstork1 65,999 Most Valuable Professional on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

Check to verify the actual internal column name by looking at the end of the URL when accessing the settings for that column. The end or the url should have a paramter of field=. Whatever folows the = is the actual internal name of the column in SharePoint, As long as the column isn't a null value that should work in Power Apps.

I think mstavra's comment about preview or classic is referring to the designer in Power Automate.
Nuriel 153 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

This error I get, whenever I try to connect these missing columns to any kind of object (text, combobox, gallery - doesn't matter) in power apps.

With other columns (incl. other lookup columns) which are recognized, I have no issues
Nuriel 153 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

I am not exactly sure what you mean with new (preview) vs. classic. Is it this first greyed-out option when creating an app in power apps? If yes, it's not available to me.

I have been using the "Select external data" option, selecting the Sharepoint site, then the list and then creating a blank 3-screen app.
mstavra 247 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

Are you using the new form (preview) layout or the classic forms in power app? If your are using the new, check the old ones please.
mstavra 247 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

Let's see if this is a general issue or a form only issue.

Create a gallery and try to connect the missing columns. Create a text input and try to set the value to your missing columns.
Nuriel 153 on at

Like (1)

Report

SPO List columns are not being recognized by Power Apps (also not internal names)

Hi,

@mmbr1606: no, in the list in question I did not rename any columns after connecting to power apps for the first time. But even when I renamed columns in the past, it was not a problem, a simple refresh of the connector or using the internal name alwayls helped.

And the columns were not recognized, as mentioned, when I even created a new app with this list from scratch.

@mstavra: I tried your suggestion and in fact of 7 currently missing columns 1 did appear now in the app based on the list copy.

But, weirdly enough not the remaining 6. I also checked names for conflicts, but there should be none. I also don't know what would be different with that one column which appeared as opposed to the other ones.

All 7 are by the way lookup columns and no my list is not over the limit of 12 lookup columns (incl. created by etc..)

I also renamed one of those missing columns in the list copy to some random name which definitely can't conflict and created yet another app from scratch: this column still was not recognized