Importing elastic table key error | Oracle Series

Issue

Upon importing a solution containing an elastic table, the following error is thrown:

Solution “xyz” failed to import: The schema name KeyForNoSqlEntityWithPKPartitionId for type EntityKey is invalid or missing.Custom attribute, entity, entitykey, option set and relationship names must start with a valid customization prefix.The prefix for a solution component should match the prefix that is specified for the publisher of the solution.

Investigation

I extracted the customizations.xml file, and then prefixed the key with the publisher’s prefix. That didn’t work, complaining that the key already existed!

Solution

As a practical workaround, consider the following steps until a permanent fix is provided by Microsoft:

1. Extract the customizations.xml file from the solution ZIP file
2. Find the key KeyForNoSqlEntityWithPKPartitionId and remove the whole XML entry (shown below)
3. Save the file
4. Add to the solution ZIP file again
5. Import

          <EntityKeys>
            <EntityKey>
              <Name>KeyForNoSqlEntityWithPKPartitionId</Name>
              <LogicalName>keyfornosqlentitywithpkpartitionid</LogicalName>
              <IntroducedVersion>1.0</IntroducedVersion>
              <IsSynchronous>1</IsSynchronous>
              <IsCustomizable>0</IsCustomizable>
              <EntityKeyAttributes>
                <AttributeName>xyz_id</AttributeName>
                <AttributeName>partitionid</AttributeName>
              </EntityKeyAttributes>
              <displaynames>
                <displayname description="xyz" languagecode="1033" />
              </displaynames>
            </EntityKey>
          </EntityKeys>

Dataverse creates the key anyway, although it’s missing from the solution.

More

Share

Tweet

Follow