Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Scott Morley]

Hi all,
For anyone interested, I wrote a review of the D365 Tech Conference last week in Seattle. Obviously I was not able to attend all the sessions, that would be a neat trick, so I only wrote about what I heard. If anyone else was there and would care to share, I would love to hear more on the topics I missed. My review can be found at The 2017 Dynamics 365 Tech Conference Review

Scott Morley		remove preview
The 2017 Dynamics 365 Tech Conference Review For those of us fortunate enough to attend the Dynamics 365 for Operations Tech Conference in Seattle last week, it offered a great learning experience. There was tons of content that Microsoft shared and I, personally, had a chance to catch up with some old friends and make some new ones. View this on Scott Morley >

——————————
Scott Morley
Principal Application Architect
OneNeck IT Solutions
Bend OR
——————————

[Faisal Fareed]

Great write up !!!

——————————
Faisal Fareed
MS Dynamics 365 Operation specialist
——————————
——————————————-

[Karin Wilkinson]

Great overwiew! Thanks Scott!

——————————
Karin Wilkinson
Independent AX Consultant
Max S.C. LLC
Deerfield Beach FL
——————————
——————————————-

[Enrique Melara]

Thanks a lot. 

Good advices.

——————————
Enrique Melara
Younger Optics
Torrance CA
——————————
——————————————-

[Luis Xavier Baena Mourão]

Thanks Scott.

——————————
Luis Xavier Baena Mourão
Technical Expert
Axllence Schweiz
Wallisellen
——————————
——————————————-

[Zvika Rimalt]

Thanks Scott, very helpful!

My important take away from it, is that if you upgrade from 2009, you can only keep your base data but not your transaction history. 

I know a couple of users who selected Dynamics AX 6 years ago under the assumption they can keep upgrading while keeping their transaction history. I can imagine they are not going to be too excited

——————————
Zvika Rimalt
Functional Solution Architect
Vancouver BC Canada
——————————
——————————————-

[Scott Morley]

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.

——————————
Scott Morley
Principal Application Architect
OneNeck IT Solutions
Bend OR
——————————
——————————————-

[Jacqui Devlin]

Very informative and well put thanks Scott

——————————
Jacqui Devlin
Hamilton City Council
Hamilton
New Zealand
——————————
——————————————-