Zvika,The reason transaction data is not being moved by the tool out of the box is because the way the import works would pretty much guarantee any refRecIds would be wrong. So the data would be there, but linking to it would be inconsistent and the only thing worse than no data is bad data. For this reason, the best practice recommendation is to move transaction data to a data warehouse and use PowerBI to access it. Remember that PowerBI reports can be embedded in D365 screens, so from an end user perspective it would be a seamless experience.
If someone really had to have transactions imported into D365 it could be done. They would have to either significantly modify the tool (it is X++) or manually update transaction refRecIds prior to import so they matched the imported master data. The effort involved in either case makes this practically impossible so it is easier to just say don’t do it. However, if someone wanted to put forth the effort, it could be done. Keep in mind that in the time it would take to prep just one transaction file for import into D365, the same developer could probably write dozens of PowerBI reports.
I know explaining a way to do something that is basically not worth it may seem silly, but once people understand how the tool works they may think it would be worthwhile trying. I just wanted to make sure the issue was clearly defined before anyone tried a workaround.
Site designed by Brightfind
Powered by Cobalt xRM and Higher Logic