I'm starting to learn X++ for the cloud version of F&O and found this page on the Microsoft docs site. I got it working and it seems great but I never see any posts about people using this approach. Has anyone run into any major disadvantages or know any reasons why I should avoid it?
Thanks
The usual use case for writing C# libraries is when you want to use an existing .NET API (for example, you want to consume external web services, you want to talk to Azure services, you want deserialize JSON to objects, you want to parse files with LINQ etc.).
If you consider creating a C# library and writing queries in LINQ, ask yourself what advantage would it bring to you. If you can simply write a query in native X++, it's clearly much less work, less things to manage and deploy, fewer boundary crossings (the interoperability has its quirks), you can utilize all X++ features and functions (the LINQ provider is limited in this respect), you'll be able to find objects by references in Visual Studio and so on. You would need strong arguments for giving up all these advantages. If you can do everything in X++ and you don't need to fetch data from AX to a .NET library for further processing, moving your business logic to C# doesn't sounds like a good idea.
There is one more layer you are adding to read data or accessing objects from F&O. It is not a best practice either. I think there will be performance impact due to extra layer of DLLs.
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Andrés Arias as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Sohaib Cheema 745 User Group Leader
Martin Dráb 597 Most Valuable Professional
André Arnaud de Cal... 580 Super User 2025 Season 2
