adaptisoft
Field notes

No. 05TroubleshootingALM

Importing elastic table key error

A fix for elastic-table solution import failures.

Ahmed Sawalhy

Principal Engineer

Jun 2024 / 1 min read

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

Share

Written by

Ahmed Sawalhy

Principal Engineer, Adaptisoft

One of the engineers who supervise Adaptisoft's agents — hands-on with Dynamics 365 since its first release.

Next field note · No. 04

Dynamics 365 Custom Workflow Jobs

A custom engine for running scheduled jobs in Dynamics 365.

Keep reading

See it working in your own tenant.

A short, read-only pilot. No data leaves your walls.

Book a pilot