Log In
Register
Home
New Member
August 5, 2022
Offline
With v1.0, most custom fields show up as SharePoint code names instead of display names, which is unacceptable.
People columns show up as display names, but they’ll display the value of ‘record’ to indicate there are many things to choose from. Once you click on the divergent arrows, you can select which fields to display, like ‘FirstName’ & ‘LastName’. This is acceptable.
With v2.0, the custom fields show up as display names, which is acceptable.
The people columns show up as ‘List’ but provide no method of breaking the values out into ‘FirstName’ ‘LastName’, like in v1.0. This is unacceptable.
How can I make one of the two unacceptable conditions acceptable?
See attached for screenshots.
New Member
August 5, 2022
Offline
I'm still interested in solving the v2.0 issue, but after messing around for two hours, I figured out the simple answer within 5 minutes of posting here:
With v1.0, most custom fields show up as SharePoint code names instead of display names, which is unacceptable.
Add the custom fields to Power Query and rename them in Power Query. You cannot rename them back in Excel, the Data >>> Refresh will just overwrite your changes.
I recommend creating a reference table so you know which codenames match to which display name.
1 Guest(s)
