Best practice for "Country/regional specific features" in license configuration

(0) Share

Report

Posted on by Community Member

Hi,

I wonder about last seen AX 2012 installations from other Microsoft AX partners. These installations have selected all country/regional specific features in license configuration. We select only the country/regional specific feature for the country the specific company is operating in. E.g. the company is from germany, only "Germany" is selected.

In my opinion it is totally wrong to select all country/regional specific features. E.g. I guess it can cause some troubles in ledger, but I don't find any Microsoft documentation or best practise about this.

What is your opinion about setting the country/regional specific features?

Regards, Dirk

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (4)

Verified answer

Vilmos Kintera 46,149 on at

Like (1)

Report
Copy link

Link copied!

Enabling more configurations than you need degrades AX performance by executing more business logic than it actually should. It also changes some functionality drastically in a not desired way.

Having them all on is a very bad practice for the above reasons. A developer and a functional consultant together should check what the changes are and decide whether that specific key is useful, and only turn on the ones really required.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thank you Vilmos, I totally agree with you.

I would appreciate some more comments from the community.

Regards, Dirk

Was this reply helpful? Yes No
Verified answer

Florian Hopfner 2,466 on at

Like (0)

Report
Copy link

Link copied!

I agree that only the configuration keys that are needed should be active. But I also worked in projects where this was not the case. It gave us a small benefit because we were able to leverage some country specific functionality which would not have been available. But it also introduced the drawback that after a system has lived some time with a configuration, you cannot easily deactivate some configuration keys without extensive testing and validation.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks @FH-Inway.

Yes, sometimes we use some other country specific functions too, but we activate only some single functions. And yes, changing the configuration in a live environment without testing can easily end up in chaos.

Was this reply helpful? Yes No
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello Dirk,

I agree with FH-Inway. There are some nice country-specific features that you can make available by activating additional Country-Region codes. Yet, the activation does only make sense if you know them and what to use them for...

Best regards,

Ludwig

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks Ludwig,

Yes, we use a testing environment with all country specific functions enabled to see all the functions. So we can decide which functions we use and activate for the respective customer requirements.

Was this reply helpful? Yes No
Verified answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hello Dirk,

The following two country-specific features might be interesting - at least for your accountants.

dynamicsax-fico.com/.../depreciation-forecast-report

dynamicsax-fico.com/.../preview-journal-transactions

Best regards,

Ludwig

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

I mark this thread as answered, but more comments are appreciated.

Was this reply helpful? Yes No