Share via

Error saving tables in Power Apps

Larry Beard 0 Reputation points
2026-02-24T19:02:10.35+00:00

I'm getting this error when trying to save my tables in Power Apps. Please help!

Dataverse API request 'https://org48221df8.crm.dynamics.com/api/data/v9.1/CreateEntities' failed with status code: '400', response content: {"error":{"code":"0x80044371","message":"{"entityName":"tbdpublishercustomizationprefix_Worker","errorMessage":"Validation of value '{0}' of property '{1}' of {'2'} component with name '{3}' failed with exception {4}.\r\nData[0] = \"tbdpublishercustomizationprefix_Worker\"\r\nData[1] = \"name\"\r\nData[2] = \"Entity\"\r\nData[3] = \"tbdpublishercustomizationprefix_Worker\"\r\nData[4] = \"The schema name tbdpublishercustomizationprefix_Worker for type Entity 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.\""}"}}

Community Center | Not monitored
{count} votes

3 answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Gérard Oomens 119.9K Reputation points Volunteer Moderator
    2026-02-24T23:33:59.9066667+00:00

    Post/ask in the Power Apps forum:

    Explore Power Platform forums

    0 comments No comments

  3. Q&A Assist
    2026-02-24T19:10:08.78+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error you are experiencing when trying to save your tables in Power Apps is related to the naming convention of the entity you are attempting to create. The specific error message states that the schema name tbdpublishercustomizationprefix_Worker is invalid or missing. Here’s a breakdown of what this means and how to resolve it:

    Understanding the Error

    • Entity Naming Convention: In Microsoft Dataverse, all custom entities must start with a valid customization prefix. This prefix is defined by the publisher of the solution. The prefix helps to ensure that entity names are unique and do not conflict with other entities.
    • Error Details: The error message indicates that the validation of the entity name failed because it does not conform to the required naming conventions. The message specifies that the schema name must start with a valid customization prefix, which should match the prefix specified for the publisher of the solution.

    Steps to Resolve the Issue

    1. Check the Customization Prefix: Go to the solution where you are trying to create the entity and check the customization prefix defined for the publisher. This can usually be found in the solution settings or publisher settings.
    2. Modify the Entity Name: Ensure that the entity name you are trying to create starts with the correct customization prefix. For example, if your publisher prefix is tbd_, your entity name should be something like tbd_Worker instead of tbdpublishercustomizationprefix_Worker.
    3. Save Again: After adjusting the entity name to include the correct prefix, try saving the entity again.

    Additional Considerations

    • If you are unsure about the customization prefix, you may need to consult with your system administrator or the person who set up the Dataverse environment.
    • Ensure that all other components (like attributes and relationships) also follow the same naming conventions to prevent similar errors in the future.

    By following these steps, you should be able to resolve the error and successfully save your tables in Power Apps.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.