cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
joshbooker
Level 8

Primary Name required prevents Power Query Data Integration

I'm creating entities using Power Query Data Integration from SQL Server.  It's working great until I reach a table that has no text fields.  The error says "No column of type text, so no column can be selected to be the primary name field" 

The Next button is disabled so I cannot continue.

Bummer, guess I can't import that table so I set to 'Do not load'

Now hit Next and I get an error 'Primary Name field is required' on another entity.  Oh now I know it's required, but there is no field that is applicable on the Orders entity since OrderID is not text. 

Why exactly is number field not allowed?  Guess I'll choose ShipAddress and hope it can be changed later.

Bummer it cannot be changed later.

Ugh.  This is so reminicent of the dreaded Title in SharePoint.

Any ideas how to make this experience better?

1) allow number fields, Guids, etc

2) allow adding 'calculated' fields

3) allow nothing and add a field for me with a random value

4) allow changing the name field later.

Thanks for listening

 

 

 

 

 

 

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,931)