Finance | Project Operations, Human Resources, ...

Dynamics Microsoft's best practices are not generally

(0) Share

Report

Posted on by xcarrillo

100

good, I would like to know if you have any guide where I explain that the best practices in most cases are not applied or Microsoft's best practices are not generally used or are not mandatory but are suggested.

I would like to know if any implementation of the previous versions of AX could be carried out without requiring that the best practices are necessary

All responses (10)

Answers (0)

Suggested answer

nmaenpaa 101,158 Moderator on at

Like (1)

Report

RE: Dynamics Microsoft's best practices are not generally

Yes, and we have answered your question. No need to repeat it :)

"Mandatory" would mean that there's some technical block, preventing you from violating best practices. Or some agreement with Microsoft where you would commit to having code that is free of best practice warnings/errors. There are no such technical blocks or agreements.

Only if you have agreed with your customer to develop code that has no BP warnings/errors, then it would be mandatory for you to obey that agreement.

If you don't have any open questions, could you please mark the helpful answer(s) to verified? Thanks!
xcarrillo 100 on at

Like (0)

Report

RE: Dynamics Microsoft's best practices are not generally

the question is .... whether it is mandatory to use best practices
xcarrillo 100 on at

Like (0)

Report

RE: Dynamics Microsoft's best practices are not generally

it is a technical question it is more to know if it is mandatory to use the best practices
Suggested answer

nmaenpaa 101,158 Moderator on at

Like (1)

Report

RE: Dynamics Microsoft's best practices are not generally

As others have mentioned and as stated in the product documentation, they are "best practices" = not mandatory. If they were mandatory, you would get compiler error in case of BP violations. However there's a good reason why MS has defined these best practices, so you should definetely not ignore them. Some bp issues can cause performance problems, localization problems or similar issues. Also I'm sure that most customers would like you to follow Microsoft's best practices when developing something for them.

A bit related, but if you're working with D365FO (you posted in AX forum so not sure which version you are using), Microsoft is planning to add some mandatory "best practice" checks with AppChecker functionality. Those rules could be considered "mandatory best practices". So in the future your code might not pass compilation even though it's following x++ syntax 100% correctly.

community.dynamics.com/.../d365-f-o-app-checker-build-your-code-as-per-ms-standards
saiijima on at

Like (0)

Report

RE: Dynamics Microsoft's best practices are not generally

Hi,xavieriini! I'd appreciate it if you could give me the details of your question!H
Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Dynamics Microsoft's best practices are not generally

Hi xavieriini,

Is this a technical related question or one that is more related to the functional side of AX?

(By the way, do you operate AX or D365FO)?

Best regards,

Ludwig
xcarrillo 100 on at

Like (0)

Report

RE: Dynamics Microsoft's best practices are not generally

Thank you very much for the information. Good to know that it is not necessary to be able to apply the best practices that I wanted to know.

in the doc indicates that it is recommended but not mandatory
Mea_ 60,278 on at

Like (1)

Report

RE: Dynamics Microsoft's best practices are not generally

nope, they are recommendations as stated here docs.microsoft.com/.../best-practices-for-microsoft-dynamics-ax-development so it's recommended to follow them but not mandatory.
xcarrillo 100 on at

Like (0)

Report

RE: Dynamics Microsoft's best practices are not generally

my question is more to the point of knowing if there is any documentation that says that best practice is mandatory
Suggested answer

Mea_ 60,278 on at

Like (0)

Report

RE: Dynamics Microsoft's best practices are not generally

It's not clear what is the question. BPs are quite generic and you can ignore them whenever they do not make sense, but you need to understand when it should be fixed and when it could be ignored.