web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Active Discussion

Implementing Company-Specific Features with IFeatureRuntimeToggle

(0) ShareShare
ReportReport
Posted on by 97

Hello everyone,

I came across something valuable and wanted to share it with you all. As many of you may be aware, feature management was introduced some time ago. We can also develop custom features using this framework.

However, the standard feature management only handles features globally, across all companies. If you want to enable a feature for e.g. a specific company, you can still partially use the standard feature management. In particular, you can toggle menus, menu items, and table fields using the AOT "FeatureClass" property with only implementing the interface IFeatureRuntimeToggle.

Instead of implementing the IFeatureMetadata in your feature class, which would list your feature in the standard feature management list, you can implement the IFeatureRuntimeToggle as shown below. This interface includes the boolean isEnabled() method

[ExportAttribute(identifierStr(Microsoft.Dynamics.ApplicationPlatform.FeatureExposure.IFeatureRuntimeToggle))]
internal final class MyRuntimeToggleFeature implements IFeatureRuntimeToggle
{
    public boolean isEnabled()
    {
        return MyFeatureImplementation::isFeatureEnabled();
    }
}

I hope this information is helpful. With this you can build your own "feature management list" that could be more granular controlled for e.g. specific companies / data areas in the application.

  • André Arnaud de Calavon Profile Picture
    307,097 Super User 2026 Season 2 on at

    Hi Raphael,

    Thanks for sharing your knowledge. If you don't have a question, you can also request for a blog space on this community: Blog submission - Microsoft Dynamics 365 Community  

    In my opinion, the feature management is and should be considered to enable features globally for the application. Users first have the option to experiment with features, then it will be enabled by default and later made a mandatory feature. If you need features to be enabled by legal entity, you can better create a parameter to control the behavior. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 429 Most Valuable Professional

#2
CU10121822-0 Profile Picture

CU10121822-0 366

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 360 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans