It seems like I have two issues here. The first one is about SharePoint List and the other one is in PowerApps. I'll explain them one at a time.
Any thoughts on this? Thanks!
Well, it's problematic because I have to figure out which internal name was mapped to the column name that was assigned. E.g. Filter('mydatasource', 'field_11',Ascending). In the past, I can use write as Filter('mydatasource', 'EmployeeName',Ascending).
Yep, that sure does make it hard to code.
To bottom line it for you, you are probably best to recreate your lists with the correct internal names. The internal names can't be changed once created.
Ive never tried importing from Excel, but I know importing from access gives the correct names, perhaps do that if you've got a lot of lists to create?
Even if you manage to get everything working with display names, at some point in your development cycle the internal names are going to rear their ugly head again, it's inevitable. If you don't want to be dealing with this for years to come, take the time now to get those names corrected.
I agree. The internal name is kind of a pain when the name is not right. I'm beginning to think it's a bug because it was working the way it should be a couple of weeks ago. Not sure what changed internally.
I didn't know you can create a list from Access and I tried that. That seems to help and I can create the right internal name in Sharepoint List. Thanks for that suggestion!
This is probably the last time I'm using Sharepoint List for this PowerApps dev. It's not the best platform for dev.
Hi guys thx for the hint with Access.
I had the same issue after importing a sheet / table from Excel.
When exporting the table from Access to SharePoint the names are as expected.