No Primary Key Information Available

Error Example:

An error occurred while executing connection '<connectionName>': No primary key information available: There is no primary key specified for the table '<entityName>'! Please define a primary key for the table to make the records identifiable.​​

Cause:

Generally, this error is due to one of the following situations:

• No defined key in the Primary Key field of a data entity that requires it.
• A key was defined in the Primary Key field but it is not the defined key of the data source itself, and this 'real' key was not added to the select statement.
• No defined primary key in the data source itself, which is required for some sources like SQL. 

Resolution/Workaround:

Make sure to go through these questions:

• Does the data source itself have a primary key defined within the data source?
• Are you using a key that is not the primary key as defined within the data source? If so, is it in the select statement (even if you don't plan to use it)?
• Is the Primary Key field blank in the Cloud Connector UI?

If you don't have a key listed at all in the Cloud Connector UI for that data entity, you must define one. There's no way around this. If you don't have a good option for a single field, you can use a combination of fields, separated by commas, to make a unique key.

If you have a key defined within the data source but it's not included in the select statement, you need to add it there.

If you don't have a key defined within the data source, you will need to add one there. This commonly occurs with MS SQL Server as it is looking for the defined key.

If you have everything properly set up but are still getting the error, then see Error Reading Back Keys Because Table 'X' No Longer Has a Primary Key Defined for resolution information as the M​etabase itself may be corrupted and need to be rebuilt.