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, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
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
When I change the tracking in the export project to Incremental, I get the following text:"If this is the first time an export will be done for the entity X after change tracking was enabled, then the first incremental export will be a full export. It is recommended to not have any data in the target tables for the entity X"My question is, what exactly triggers this "first time full export"? NOTHING I do works, which leaves me to believe this is some kind of a bug.
My process:I disabled change tracking on all the entities.Then I dropped the entities.Then I published them again.Then I enabled change tracking for primary table.Then I went to the export project with incremental enabled and ran "export now" option.Result = 0 records exported.
Whatever I do, it simply doesn't work as intended.The workaround for now is to have to export jobs, (one for full and one for incremental), though I've noticed that during the first push some entities show an error until you run the job again. At times like this I wonder if it wouldn't be easier to give customers a SELECT grant on the production AOS so that customers can read directly from the database as with AX09.... either the custom solution works, or it is a pain for customers, but I digress...
What is your exact question here? The first push needs to be a full push. Thereafter you can do the incremental updates. The reason is that change tracking will mark new created and updated records which will be picked up by the incremental push. When you enable it, the system is not aware what had been exported before or not. That is the reason why you need to do an initial full push.
What is the reason that you disabled the change tracking? And recreated everything from scratch?
Well, according to the messages from within D365, it states that after an entity has change tracking enabled, the first export (regardless if it's incremental or full) will be a full push. I just want to understand why it doesn't do a full push the first time, hence I recreated everything from scratch.
You are correct in your understanding: docs.microsoft.com/.../export-entities-to-your-own-database
When you deleted a change tracking and recreated it, then there is still history on the data project and also records will probably still exist in your BYOD database. That might be the reason why it is not doing the full push automatically. Can you verify if the tables in BYOD still had data?
The change tracking in D365 is essentially the same as that in SQL server.
From your process, you disabled it first and then you enabled it without any data changing.
In fact, the data in the database has not changed, change tracking was not triggered either.
And records of Change tracking record still exists, Disabling or enabling does not affect their records in the database.
To query the change data in the Azure SQL Server ,you can write T-SQL like this:
DECLARE @changeTrackingMinimumVersion INT = CHANGE_TRACKING_MIN_VALID_VERSION(OBJECT_ID('axdb.ax.custtable'));
FROM CHANGETABLE(CHANGES [axdb].[ax].[custtable], @changeTrackingMinimumVersion) AS AxDB;
You can refer to the following Doc to read more about change tracking:
additionally could validate your change trackings in this table
Business Applications communities