Personalized Community is here!
Quickly customize your community to find the content you seek.
Check out the latest Sales updates!Learn about the key capabilities and features of Dynamics 365 Sales and experience some of the new features.
Download overview guide | Watch Sales video
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I just recognized that dozens of fields in our target environment do have an unmanaged layer, even when we only import managed solutions into this environment. (At least I thought so.)
These are Calculated Fields, Rollup Fields and some Global Option Set Fields.
I couldn't remove the Active Layer from these fields and after researching I found this
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/calculated-rollup-attributes?view=op-9-1#additional-limitations (refers to OnPrem)
and this interesting post:https://www.philcole.org/post/calculated-fields-and-managed-solutions/
So my assumption is
1) Calculated Fields always end up in unmanaged layer in target systems.
2) Updating Calculated Fields always requires "Overwrite Customizations" when importing Managed Solutions OR manually updating them in target environment.
Is there anybody out there who can confirm these two assumptions?If you have any "best practices" how you handle Calculated Fields in your projects with Managed Solutions I'd be happy to get some more advice here.
Here is an article which may help you.
Calculated Fields and Managed Solutions - (philcole.org)
Hi Nya, appreciate your help but this article was already referenced by me above and didn't answer my questions.
Business Applications communities