Good Morning,
With continuation to previous thread
Now i created one dll from that and i want to refer that in Ax 2009 to perform CRUD Operations.
But the Dll size is around 116 MB.
Will it have impact for Ax 09 if i add Dll in references. ?
If yes then can we shrink DLL size ?
Please show some light on this.
Regards,
Have a nice day.
It seems you mean a DLL built by compiling code generated by OData Client Code Generator.
Are you sure you need all the entities? EDMXTrimmer was already discussed in the previous thread; it can help you with this task as well.
Hi,
Why do you want to add this as a dll in AX 2009? You have an application that uses Odata to write records into D365 F&O.
Could you please explain your exact requirement?
Hi Gunjan,
the requirement is we need Sync integration between Ax 09 and D365fo. and from D365fo to Ax 09
We have Canada and US where canada is using D365 fo and now we want to make transfer order to US. But US is in 09 so we want to create transfer order in 09 and From 09 we want to create intercompany orders.
Please show some light on this.
Regards,
Have a nice day
Hi martin,
can you please guide me how to use EDMX trimmer.
When i download project and load that it is not loading it is saying loading project failed.
Please guide me .
Regards,
Have a nice day.
Are you sure that OData is the right tool for this purpose? Did you consider performance implications, for example. And what you'll do when F&O is unavailable (e.g. because of maintenance) and OData services aren't available? Wouldn't it be much better to export orders to files or save messages to a queue and process them asynchronously?
Regarding EDMXTrimmer, check out the links others gave you at the beginning of your previous thread.
Hi,
I think it will be difficult to use Odata in this scenario. Every time you change something in the entity, you will to regenerate oData client code, regenerate the dll and import it back into AX 2009.
As Martin suggested, it might be easier to use files for upload. You might want to consider using Recurring integrations, where you can generate files out of AX 2009 and use those for import into D365
Please look up these links -
Hi,
"Wouldn't it be much better to export orders to files or save messages to a queue and process them asynchronously?"
I read about Recurence integration scheduler .
There are concerns about that a dedicated vm should be allocated to that
we will not get real time alerts and Dual scheduling is not there.
I am not sure recure integration use data entities.
In that case as well if system is in maintenance mode can it insert in that situation ?
regards,
have a nice day
Hi gunjan,
Can you please show some light on what scenarios can we use Odata
Regards
I am not sure if you will need a dedicated VM for this.
Recurring jobs use the same data entities that you would be calling using Odata. You can also monitor the success and error folders to check if there were issues.
We have used Odata in .NET applications that interact with D365 and any other application (AX 2009 in your case).
You can use AIF to read data from AX 2009 and use Odata to write into D365 F&O.
How many entities are you looking to integrate from AX 2009 to D365?
Share
Report
All responses (
Answers (