Deployment is failing with this error (TST env to PROD) Powerapps

The error indicates an invalid or missing schema name for the RegardingObjectId attribute, and specifically that the name does not follow the required customization prefix rules for solution components.

To debug and resolve this in a Dataverse/Power Apps solution deployment from TST to PROD:

1. Identify the component causing the error
   • From the solution import error log in PROD, locate the component or table where RegardingObjectId is referenced.
   • RegardingObjectId is a common attribute used as a lookup/“regarding” field, and in some solutions (for example, in Customer Service) it is extended to target many custom tables. See the RegardingObjectId customization list in the SyncError table reference to understand how it can be targeted to many entities.
2. Check for invalid schema names or prefixes
   • In the source (TST) environment, open the solution and inspect any custom attributes, relationships, or entities related to the failing component.
   • Verify that:
     • Every custom attribute, entity, entity key, option set, and relationship has a schema name that starts with a valid customization prefix.
     • The prefix matches the publisher of the solution being imported.
   • If any attribute or relationship referencing RegardingObjectId uses a schema name without the correct prefix, rename it to use the correct publisher prefix.
3. Check for invalid or lingering relationships
   • Invalid or orphaned relationships can cause schema-related import errors. For example, an entity relationship that persists in the schema after changes can cause import failures.
   • Review relationships involving RegardingObjectId and remove or correct any that reference entities or attributes that no longer exist or that have invalid schema names.
4. Rebuild the solution metadata
   • Remove the affected table(s) and related components from the solution in TST.
   • Add the table(s) back with all required assets so that the solution’s XML includes complete and correct metadata (including primary name attributes and relationships).
   • Export the updated solution from TST and re-import into PROD.
5. Reattempt the import
   • After correcting schema names and relationships and rebuilding the solution, import again into PROD and confirm that the error no longer appears.

If the error persists, download the solution import log from PROD and focus on the specific component type (entity, attribute, relationship) flagged as invalid to locate the exact schema name that violates the prefix rule.

References:

• Sync Error (SyncError) table/entity reference (Microsoft Dynamics 365 Customer Service)
• Invalid Dependency (InvalidDependency) table/entity reference (Microsoft Dataverse)
• "PrimaryName attribute not found for entity" error occurs during solution import
• This solution package cannot be imported because it contains invalid XML error occurs in Microsoft Dynamics 365
• Error code 80040203 (Invalid Argument) error when importing a solution into Dynamics 365