How to Implement Feature Toggles (Configuration Keys) in D365 CRM Similar to D365 F&O?

(0) Share

Report

Posted on by CM-01080439-0

Hi everyone,

In D365 Finance and Operations, we have Configuration Keys that allow us to enable or disable specific features at runtime. I'm trying to implement a similar concept in D365 CRM (Dataverse).

My idea is to create a custom table (e.g., "Feature Toggles") with Yes/No fields for each feature. I plan to create a single record in this table and use JavaScript, plugins, or Power Automate to check if a feature is enabled before showing certain sections or running logic.

For example:

On form load, retrieve the toggle record via JavaScript.
Show or hide sections, tabs, or fields based on the toggle values.

Has anyone used a similar approach?

Is there a better or more standard way to manage feature toggles in D365 CRM?
Any performance considerations or best practices I should follow?
Would using environment variables be more suitable in some cases

Thanks in advance for your suggestions and insights!

Categories:

Dynamics 365 general

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Jonas "Jones" Melgaard 4,893 Super User 2025 Season 2 on at

Like (0)

Report

How to Implement Feature Toggles (Configuration Keys) in D365 CRM Similar to D365 F&O?

Configuration keys aren't really run-time. You have to set the environment into maintenance mode, flip the configuration, and then go out of maintenance mode. This will trigger a synchronization of the data base. I'm more thinking feature management, this is more run-time.

But I digress.. There is no equal functionality in Power Platform (CRM).

You can use business rules to sort-of achieve this if you want a low-code solution.

But otherwise, as you said, you are looking into creating Javascript in the forms. I've seen it done a few times.

Was this reply helpful? Yes No