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)

Implications of Creating a ReadOnly dataservice directly pointing to AX database??

(0) ShareShare
ReportReport
Posted on by

Hi Community,

I am considering creating a Readonly OData service which points directly to the AX database.

Do you see any potential issues with this approach? 

Appreciate your insights..

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    237,965 Most Valuable Professional on at

    Are you aware that readonly OData services are supported in Dynamics AX 2012 out of the box? Is there any reason why you can't use them?

  • Community Member Profile Picture
    on at

    Thanks Martin,

    Yes, I am aware, and tried them, but they are 1. extremely limited in functionality (I mean none of the query parameters works), 2. Very Slow ,3. Need flexibility to add some Auditing & external user authorization logic.

  • Verified answer
    Martin Dráb Profile Picture
    237,965 Most Valuable Professional on at

    If you have a problem with standard services, please explain it - somebody may be able top help you. Nevertheless I admit that performance may be a problem.

    To answer your original question: accessing AX database directly is definitely not recommended and this applies to read-only access, although it's surely much less dangerous than writing. Nevertheless you would bypass all security, wouldn't be able to use any AX business logic (foreign key expansion, display methods etc.), would have to deal with table inheritance and generally depend on implementation details. That's the reason why you should always go through AOS.

    That being said, there are cases when direct reading from DB may be appropriate, but I wouldn't use it for anything complex, because you would likely end up reimplementing a lot of AX logic (including things mentioned above and existing queries).

    Nevertheless you haven't yet tried all options before giving up - namely, consider implementing your OData service with calling the AX query service rather than constructing SQL queries.

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