Customer experience | Sales, Customer Insights,...

Calculated Fields in Managed Solutions

(1) Share

Report

Posted on by moko33

1,788

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)

experience.dynamics.com/.../

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.

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

Nya 29,060 on at

Like (0)

Report

Hi,

Here is an article which may help you.

Calculated Fields and Managed Solutions - (philcole.org)

Was this reply helpful? Yes No
moko33 1,788 on at

Like (0)

Report

Hi Nya, appreciate your help but this article was already referenced by me above and didn't answer my questions.

Was this reply helpful? Yes No
benny-moore 5 on at

Like (0)

Report

Noticed the same thing was happening, but on closer inspection I saw that the unmanaged layer was only modifying the modifiedon value.

My guess is that when the managed solution is imported, it immediately creates an unmanaged layer for every calculation field updating modified on. This also explains why you can't delete this layer; you can do so, but it's only ephemeral: Power Apps immediately creates a new unmanaged layer updating modifiedon to the current date/time.

In the above screenshot, I had recently deleted the previous unmanaged solution, which showed 03:55 as the time.

My assumption on this is that the unmanaged solution layer shouldn't be causing any problems, but having said that, the reason we stumbled on this thread in the first place is because our calculations weren't working in the managed solution...

Was this reply helpful? Yes No