Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
Thank you for a great post. Just one question. The timestamp does only handle "modify". So if for instance a new customer is created the customer does not get a new timestamp - it will be blank. This first happen when the customer is modfied. This means that new customer will not be extracted as the SQL Timestamp will be blank. Of course I can develop something in the export that all customers with a blank SQL Timestamp get's modfied. But is there a more clever solution ? Maybe a parameter to choose that inserts also get a timestamp or something else ?
Business Applications communities