cancel
Showing results for 
Search instead for 
Did you mean: 

Change Entity Schema Name on Import

Author Name: Richard Smith

Make it possible to change the entity schema name when importing an entity or solution.

Status: Under Review
Comments
D365Ideas_Admin
Regular Visitor
Status changed to: Under Review
 
D365Ideas_Admin
Regular Visitor
Nick, It would be great to do both. We are using CRM for rapid prototyping during design. Clients constantly clarify what they call things, and it gets confusing when they finally agree to a term that is significantly different from what we originally created. With my current client, we created tables for price levels which they actually now call price scales. Another example is trying to leverage a solution between 2 clients where the prefix should change between clients. I get that this has far reaching impacts, esp. doing this on the fly. Being able to export a current entity and then re-import it and make some changes to the entity or field names on the import would be great. Thanks. Richard
D365Ideas_Admin
Regular Visitor
Hi, Are you asking for the ability to update schema names in general, or the ability to update schema names specifically at import time? Thanks, Nick Patrick Program Manager Microsoft Dynamics CRM This posting is provided "as is" with no warranties, and confers no rights.
D365Ideas_Admin
Regular Visitor
Richard, thanks for the clarification. We'll think about ways to make this easier in future releases. Cheers. This posting is provided "as is" with no warranties, and confers no rights.
D365Ideas_Admin
Regular Visitor
I would like to be able to rename an entity's schema name in general. I often experience that entity names are changing as the requirements become better understood (and as new requirements are identified) and where a schema name chosen earlier in the development becomes inappropriate but has to stay because it is too much work to recreate the entity.
D365Ideas_Admin
Regular Visitor
Generally would be great - since this could save time with regard to existing entities. We are able to do some incredibly rapid prototyping in CRM because of the incredible toolset. However, we often need to completely rebuild the solution after design and before development to use the updated nomenclature, and to make sure that the UI field labels have some level of consistancy with the db names. If this was not possible for existing imported entities, it would be great to have it for Import, since we could export and import the entity with the changes. But we would need to be able to edit the table name (custom tables only), table prefix (e.g. crm_, gbs_), and individual custom field names.