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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / When to customise Ax a...
Microsoft Dynamics AX (Archived)

When to customise Ax and when not to

(0) ShareShare
ReportReport
Posted on by UnaFresa 66

What design questions should we ask on whether to customise Ax to support a bespoke business process that Ax doesn’t support out of the box, or whether to write a discrete application to sit outside of Ax and interface with it to do this?

I'm specifically thinking of considerations when upgrading from R2 to R3 and the further implications this design decision will have when upgrading to 365

I know this is quite an open ended question so I'm looking forward to hearing about people's experiences

*This post is locked for comments

I have the same question (0)
  • Sohaib Cheema Profile Picture
    Sohaib Cheema 49,438 User Group Leader on at

    The short answer is: it is needed to customize application when

    1)     Standard application is not fulfilling the business process.

    AND

    2)    There is no alternative (easy to use, cheap to pay) technology

    Until 2012 there were not great alternatives as those are today, such as PowerApps etc., but today with cloud world, things are getting better when customization needs are getting less. Those will never finish 100% fully.

    You would need to go through FRD (Functional requirement document) for each business process of the organization and you would watch AX, to map the business process with requirement. Where you would feel that standard system cannot help you, you can thick to customize. I cannot think of hard rules around this question i.e. when to and when not to customize AX. Application provides the customization and/or extensibility which you can use when you need those.

    With this I would add that, for MSDyn365FO, customizations are not allowed any more, it is extensions based approach now, which allows to keep the base application as it was released.

  • UnaFresa Profile Picture
    UnaFresa 66 on at

    Thanks for that, when I said customise I should have chosen my words more carefully, I meant to extend as per the best practices

    I guess in the case of going to Ax 2012 R3 and then to 365 FO, the way the extension is written would be crucial in determining how easy it would be to upgrade to 365 FO, we have some current functionality in Ax which will need to be re-written to allow this

    We're still at the high level planning phase so this question arose because analysts are questioning whether it's worth customising Ax to do this at all if it doesn't support this process out of the box, but this will be an ongoing discussion

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans