Reply To: How To Use License Codes and Configuration Keys for Dynamics AX?

Network of MS Dynamics D365, AX, NAV, GP, SL, CRM, RMS, POS professionals Forums Reply To: How To Use License Codes and Configuration Keys for Dynamics AX?

#12464

John
Participant

< ![CDATA[Hi Chloe, One of the first things that should be done on a Dynamics AX 2012 implementation project is to enable or disable license codes and configuration keys based on the scope of the project. With prior versions of AX, functionality was purchased a la carte based on your requirements, but with AX 2012 all functionality is included when you buy your licenses. As such, you have access to features and functionality that you may not need. Disabling those features and functionality eliminates the clutter in the system and makes it easier for end users to use. For example, if you don’t manufacture anything, you can probably disable all of the manufacturing and production license codes. Disabling a license code or configuration key removes the associated module or feature from the user interface. License codes control large groups of functionality like modules and can be enabled or disabled from the License information form (Menu path: System administration > Setup > Licensing > License information). License codes are associated with configuration keys. Configuration keys control functionality within a module at a more detailed level and can be enabled or disabled from the License configuration form (Menu path: System administration > Setup > Licensing > License configuration). After enabling or disabling features in either form, the system automatically does a database synchronization, which takes about half an hour or so. Microsoft recommends disabling the features and functionality that you don’t need as it makes the application less confusing and easier for end users to use. I fully agree, but there are a number of challenges. Specifically, if you deactivate features that you end up needing. First of all, you will probably spend a bunch of time hunting and troubleshooting to try to figure out why the system isn’t working the way you want. Then when you turn the features back on, you need to fully retest everything as the application has essentially changed. Leaving license codes and configuration keys that you don’t need to create issues as well. The business users will want to hide them with security or customization or you will have to address them with training. Turning off the features you don’t need eliminates that issue. Another challenge is simply knowing what each license code and configuration key controls. No matter how many times I’ve done this, there always seems to be some amount of trial and error and the list of license codes and configuration keys change with most releases. I think it is great that Microsoft keeps adding license codes and configuration keys as it gives us more control over the features and functions in the system. It does, however, make setting the license code and configuration keys more complicated. Getting the license code and configuration key settings right as early as possible is a very important part of an implementation project.]]>

Skip to toolbar