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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

AX 2012 R3 Performance Optimization

(0) ShareShare
ReportReport
Posted on by 30

Hi All,

Always we did custamization based on client requirement. Some time we wrote code in application in some place which is actually not right place to write code. Which cause later AX performance issue.
Could you please elaborate me how to prevent from AX performance issues practically?

*This post is locked for comments

I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    301,119 Super User 2025 Season 2 on at

    Hi Arpan,

    If you spend some time on a technical design, you can think of the best place where to put the code, think of index use and other best practices.

    Also when creating views and queries you need to take some time for the correct design before the view might become huge for SQL server. In SQL server you can analyse execution plans and see where the queries can be improved.

    Also some kernel methods might take time where it would be possible to check something in another way. Prevent usage of SysDict... classes where you can use Dict... classes.

  • @rp@n Profile Picture
    30 on at

    Thanks Andre,

    I will follow your post.

    If we keep in mind below points before start custamization it will helpful for AX performance better :

    1. proper index in table

    2. follow BP Deviation

    3. Write code in Class level instead of Form

    4. Use Join instead of multiple while select statement

    5. Delete unnecessary code which is not in used

    6. Logic should be in proper way

    7. mentioned field name in while select statement

    If any other things please suggest.

    Thanks!

    Arpan Sen

  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    3. Write code in Class level instead of Form -> this makes no difference if the class is set to Called from. Rather than database operations (select, insert, update, delete) must execute on server-tier. Also you should not have many cross-tier calls between client and server.

    Writing unnecessarily large methods is also considered to be bad, they should be easily readable and could should be highly reusable. Use whatever you can from Standard, do not make customization unless it is unavoidable.

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…

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