Answered

Weird behavior with SharePoint

(0) Share

Report

Posted on by Mattw112b

1,088

I have two separate SharePoint Sites that are the same (I created one from a template of the other). So all field names, settings, etc, same.

I have a PowerApp that uses a SP list in one site and I have a copy of the PowerApp that uses a SP list in the other site. I used export/import to get the duplicate PowerApp then went in and changed the data connections.

The weird part is the second powerapp comes up with an error in the formula for MaxLength on a dropdown box.

Original that works just fine:

DataSourceInfo([@VirtualPZone], DataSourceInfo.MaxLength, "OpeningType")

But in the duplicated PowerApp running with data from the duplicated SharePoint list, it doesn't like this formula and says the function has some invalid arguments. IT IS EXACTLY THE SAME..??

Then if I play with it, the only thing I can get it to accept without error is:

DataSourceInfo([@VirtualPZone], DataSourceInfo.MaxLength, "Opening_x0020_Type")

But then my PowerApp doesn't work...no errors just doesn't save the form.

How is this possible? Again everything is exactly the same between the two, just two different SP Sites that are exactly the same?

Thanks,

Terry

Categories:

Building Power Apps

All responses (4)

Answers (1)

Sort by

v-siky-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Mattw112IG ,

MaxLength means the Maximum number of characters that the column can hold.
I would recommend you to delete the original code and re-enter it manually.
If this still doesn't work, you can try to hardcode the Length in MaxLength property. In general, the max length of the column is 255, so just enter 255 into MaxLength property. Also, you can go to List settings, select the column to confirm the Maximum number of characters.
Hope this helps.
Sik
Verified answer

Mattw112b 1,088 on at

Like
a
(0)

Report
Copy link

Link copied!

I found that this was an issue with renaming a SP column. Even though it looks right on the backend it is still the original name. PowerApps wanted the original name and when I exported my package and reimported in a different environment it didn't like the name change.
Terry
v-siky-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Mattw112IG ,

Yes, you are right. PowerApps only recognizes the initial column name of SharePoint list, not the modified column name, which is a consistent universal problem.

Could you please mark your post as the Solution to help other members find it more readily?

Sik
high-solutions 26 on at

Like
a
(0)

Report
Copy link

Link copied!

Sorry for replying so late, but how exactly did you solve it?

I have somewhat the same problem but simply renaming it back to the original doesn't fix it for me, still same issue..