Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I'm working on wrapping up our data migration schema (using DIXF/DMF) for our upgrade from R2 to R3. We would like to import open sales order lines. However, we also need to import MarkupTrans records for the sales order headers, and Microsoft appears to have neglected that feature in the standard data entities.
Have you (or anyone you know) imported open sales orders using DIXF? If so, how did you import MarkupTrans (charges) for the sales order header? (e.g., delivery charges)
*(Note:I see there is a feature to import MarkupTrans information on the sales lines, but in our case we want to import it on the sales order header, which is where it is coming from in our R2 environment.)
Thanks in advance for any help you may be able to provide.
You can have a look how Microsoft implemented the Markup transactions for the sales order lines. You can then create a customization by applying similar logic.
Do you really want to make use of header charges?
I think a change from R2 to R3 might be a good opportunity to think about them.
From an accounting perspective I hate them because as soon as it comes to posting and analyzing those charges things get difficult.
Example: How much did you charge on freight for a specific item if the freight is added as header charge and the sales order includes multiple lines with different items? When you get those questions from your finance colleagues, you quickly end up in Excel doing some manual calculations.
If you don't get those kind of questions then you are probably fine with header charges.
Otherwise, I would recommend rethinking their usage.
I created a custom entity that allows me to import MarkupTrans (open charge transactions) on S/O and P/O headers, all from one source file, and it works well.
If anyone is curious about the details on this, just let me know and I’ll share.
Business Applications communities