Share
ReportWe are using the Bring Your Own Database (BYOD) framework in Dynamics 365 Finance & Operations to export data to an external reporting and analytics database. To improve performance and minimize data movement, we use Incremental Export instead of full exports.
During our analysis, we found that the DimensionAttributeValueGroupCombination table has the following properties:
- Allow Change Tracking = No
- Allow Row Version Change Tracking = Yes
Since SQL Change Tracking is disabled for this table, data entities that depend on DimensionAttributeValueGroupCombination cannot fully participate in BYOD incremental synchronization. As a result, changes in this table are not detected through SQL Change Tracking, which impacts our incremental export strategy.
We are looking for guidance from Microsoft or the community on the following questions:
- Is there a supported way to enable Allow Change Tracking for the DimensionAttributeValueGroupCombination table?
- If enabling Change Tracking is not supported, what is the recommended approach for handling incremental exports for entities that depend on this table?
- Is there any Microsoft-recommended workaround or best practice to avoid running full exports while still keeping the BYOD database synchronized?
Our goal is to maintain efficient incremental synchronization without relying on full data exports.
Any guidance or recommendations from Microsoft or others who have encountered a similar scenario would be greatly appreciated.
All responses (
Answers (
433
