Best Practice to customize entities

(0) Share

Report

Posted on by fs92

Hi,
I'm currently looking for a best practice on how to customize default entities in CDS.

Use case description:

I want to extend the Project Entity for Project for the web to add some fields, change option sets, forms and views.
The entity customization should be packageable to a solution to roll it our to test and prod environments.

Questions:

Is it the right way to customize the default entity or create an own to extend the default entity?
What if Microsoft changes some entity default fields or settings on its own? Is my setting overwritten?
If rolling out the solution to another environment where a project entity is already in use, will be all settings overwritten or only added to the existing ones?

Cheers

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!
Hi @fs92,
The only best practices officially published by Microsoft are the following links:
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/best-practices-sdk
Note: it says on-premise but the same applies for online
For ALM, deployments and rolling out solutions as you mentioned, here's the Microsoft's ALM whitepaper: https://www.microsoft.com/en-us/download/details.aspx?id=57777
There are a lot of articles/blogs from the community that give tips, tricks and best practices. Here's a popular that I particularly like: https://crmtipoftheday.com/
For your specific questions:
Right way to customize entity? If you extend the entity and functionality with only supported customizations, then there's really no wrong way. The question of right/wrong becomes a design/architectural topic based on your requirements.
Microsoft will most likely enhance existing and implement new functionality and entities. The behavior depends on the solution layering. You are configuring in your "dev" environment as unmanaged. The unmanaged layer sits on top of managed so in theory your changes should take precedence, but it doesn't mean you will not be impacted by updates from Microsoft (e.g. a new optionset item or a new command bar button will appear in your solution until you remove)
More info on solution layers: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/solution-layers
Hope this helps!

Was this reply helpful? Yes No
fs92 63 on at

Like (0)

Report
Copy link

Link copied!

Hi @EricRegnier ,

thank you for your response this helped a lot!
One last question. You wrote: " If you extend the entity and functionality with only supported customizations, then there's really no wrong way."
What means supported customizations? Adding Fields, changing Option Sets, add or edit views and Forms?

Thank you for your help.

Cheers

Was this reply helpful? Yes No
Verified answer

EricRegnier 8,720 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

My pleasure, happy it helped! Adding fields, changing optionsets, updating entities, etc are all supported. Unsupported customizations are things like manipulating the DOM, using undocumented internal objects, building new functionality using features that are deprecated and going away.
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/customizations-supported

Was this reply helpful? Yes No