Answered

Need help on understand what something means

(0) Share

Report

Posted on by Mattw112b

1,088

Within PowerApps I have a couple fields that are showing up different from each other with the same backend data source.

I'm wondering is anyone knows what causes PowerApps to see data source fields differently. For example:

"OpeningType" vs "Opening_x0020_Type"

In powerapps looking at a data source where both of these are the same. So in SharePoint List, this field is a Single Line of Text, 255 characters.

But on one SP List I have to do it "OpeningType" otherwise says invalid arguments and on the other it is the opposite, I have to put x0020 otherwise I get invalid arguments.

So what would force PowerApps to have to have it one way or another?

Thanks,

Terry

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

PowerAddict 7,316 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

The x0020 is needed when there is a gap between words. So if the SP list name is OpeningType, you would be able to use it as is. But if the SP list name is Opening Type, then you will have to use the x0020.

Let me know if this helps.

---
If you like this reply, please give kudos. And if this solves your problem, please accept this reply as the solution.

Thanks!
Hardit Bhatia
https://thepoweraddict.com

Was this reply helpful? Yes No
vanels 36 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,
When you create the field the first time, is better that name will be without gaps, for example NameForYourField and once it is created, you can rename it and put Name For Your Field, but the internal name will be the first you put (without gaps) and Powerapps takes it without gaps.

Byes

Was this reply helpful? Yes No
Verified answer

Mattw112b 1,088 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks I have been using SP and PAs for a long time so I know about _x0200_

So I guess my question was a dumb one.

Was just trying to understand an issue I'm seeing and my head started thinking this means something different than what I thought...

I have figured it out though.

So I was having an issue (I thought) where PowerApps was seeing the same datasource in two locations differently.

When I went into SharePoint and looked at the column names and types the two appeared exactly the same. So I was confused on why I had to put it in PA differently...

Fast forward I read this article:
https://persnicketypowerapps.blogspot.com/2018/08/breaking-powerapps-cannot-save-or-edit.html

And turns out that even though the column names looked the same in SharePoint, really behind the scenes the field must have been renamed at one point to look the same, but SharePoint doesn't change the name when you edit it.

So my field that looked like "Opening Type" was really "OpeningType" behind the scenes.

I renamed back to the old version, created a new column called "Opening Type", copied over everything from the old one and then deleted it. Worked perfectly to get PowerApps back on track.

Now I know never to rename a SharePoint field or change SharePoint type... just delete and re create.

Terry

Was this reply helpful? Yes No
PowerAddict 7,316 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Glad you were able to help yourself, nothing like it!

Was this reply helpful? Yes No