cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
designAV
Level: Powered On

_x0020_

Hi all, is there a quick fix for the issue of spaces in Excel files being replaced by _x0020_ in PowerApps? I've got a large Excel file with a lot of info (and therefore a lot of spaces). Thanks

2 ACCEPTED SOLUTIONS

Accepted Solutions
PowerApps Staff AndyPennell
PowerApps Staff

Re: _x0020_

Its not a bug. As you point out, spaces are important in the PA language. For this reason if a column name (from Excel or any other data source) contains a space (or other "weird" character) it is replaced with an escaped version (0x20 in the case of spaces).

 

Some data sources offer both an internal name (which is used in the PA language) and a display name (which is shown in the UI eg as a column header in a data table). Excel does not do this.

View solution in original post

nickduxfield
Level 8

Re: _x0020_

As others have mentioned, its not a bug.

First rule of thumb in Ms Access, SharePoint Lists, and any table, Dont crete columns with spaces. Even in website's addressbars you will see %20 to represent spaces, its the same thiing.

 

In SharePoint you first create a column with No spaces and that creates a clean clear readable Internal Column Name.

Then you can change the display name.

It helps a lot when someone else comes on the job and works on your project, they can easily read whata going on and it wont throw any weird un-troubleshoot-able errors.

 

Try to write like this:

 

ThisIsMyNewColumn (Internal Column Name (Shows in PowerApps etc))

This is my new column (Display Name of the above)

View solution in original post

5 REPLIES 5
Fields
Level: Powered On

Re: _x0020_

Hi there, 

 

As at my notice, i don't think that exists. In powerapps, every single space will have the _x0020_ in there. That's why, people advice to don't use spaces or any special character in that matter.

 

So no, there is no solution to that problem.

 

That's something people should avoid, spaces, special characters, and Numbers as first letter.

 

I hope i was helpfull. If you got a solution tho (That, again, i don't think it exists), feel free to share with us 🙂

Highlighted
designAV
Level: Powered On

Re: _x0020_

Thanks for that. It does baffle me a bit, I would've thought a bug like that would be ironed out early in the development stage of Powerapps. Spaces are kind of important in the use of language! 

PowerApps Staff AndyPennell
PowerApps Staff

Re: _x0020_

Its not a bug. As you point out, spaces are important in the PA language. For this reason if a column name (from Excel or any other data source) contains a space (or other "weird" character) it is replaced with an escaped version (0x20 in the case of spaces).

 

Some data sources offer both an internal name (which is used in the PA language) and a display name (which is shown in the UI eg as a column header in a data table). Excel does not do this.

View solution in original post

nickduxfield
Level 8

Re: _x0020_

As others have mentioned, its not a bug.

First rule of thumb in Ms Access, SharePoint Lists, and any table, Dont crete columns with spaces. Even in website's addressbars you will see %20 to represent spaces, its the same thiing.

 

In SharePoint you first create a column with No spaces and that creates a clean clear readable Internal Column Name.

Then you can change the display name.

It helps a lot when someone else comes on the job and works on your project, they can easily read whata going on and it wont throw any weird un-troubleshoot-able errors.

 

Try to write like this:

 

ThisIsMyNewColumn (Internal Column Name (Shows in PowerApps etc))

This is my new column (Display Name of the above)

View solution in original post

alirobe
Level: Power Up

Re: _x0020_

This is poor design.

 

I agree the underlying data structure needs an escaped space, but the displayed labels should un-escape automatically.

 

I do not agree that "First rule of thumb in Ms Access, SharePoint Lists, and any table, Dont crete columns with spaces."

 

This may be good advice for IT consultants, but PowerApps is designed for business users.

 

Spaces will be used.

 

PowerApps needs to deal with it the same way Access, SharePoint Lists, and Tables do: Escape in the back-end, and automatically un-escape in the front end. There is no reason why a front end user should ever see an escaped sequence. You say that Excel does not offer an unescaped label. The unescaped label is in the Excel sheet. The Excel sheet is simply XML, and the header cell value is unescaped, and visible to the excel user. So I'm afraid it's not a valid excuse. PowerApps could certainly get the value, and it could certainly display it. It simply hasn't been thought about enough.

Helpful resources

Announcements
thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

sixthImage

Power Platform World Tour

Find out where you can attend!

Power Platform 2019 release wave 2 plan

Power Platform 2019 release wave 2 plan

Features releasing from October 2019 through March 2020

fifthimage

Microsoft Learn

Learn how to build the business apps that you need.

Top Kudoed Authors (Last 30 Days)
Users online (5,329)