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