Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Reply
Ramkishor
Helper I
Helper I

Allow row version change tracking

Hello all,

 

I have a question , For a d365 f&o table to be available in power apps Azure synapse link for syncing it to Microsoft fabric a table property named "Allow version change tracking" needs to be enabled. But for a data entity if I enable the property that data entity is not visible in power apps . Is there any way that we can do for data entity or is it the same as the table.

 

If it is same as the table then why am i not seeing the data entity in the power apps ?

 

Any suggestions would be appreciated! 

 

Regards

Kishor

1 ACCEPTED SOLUTION
Ritaf1983
Super User
Super User

Hi @Ramkishor 

It looks like you’re mixing up a table and a data entity.
In Power Apps or Synapse Link, only physical Dataverse tables that have Change Tracking enabled can be synced.
Data entities from F&O are virtual objects, not real tables — so even if you enable “Allow row version change tracking,” they won’t appear in Power Apps.
That property only applies to actual SQL/F&O tables, not to entities.

To make it work, you have a few options:

Use the underlying table instead of the data entity and enable Change Tracking on it.

If you need the same structure as the entity, load the data into a real Dataverse table using Dual-Write, Dataflows, or ETL — then enable Change Tracking there.

Alternatively, use Export to Data Lake or Synapse Link for F&O and connect Fabric to that output.

Bottom line – you can’t make a data entity visible in Power Apps just by turning on Change Tracking.
Only physical tables with Change Tracking are supported.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

Regards,
Rita Fainshtein | Microsoft MVP
https://www.linkedin.com/in/rita-fainshtein/
Blog : https://www.madeiradata.com/profile/ritaf/profile

View solution in original post

4 REPLIES 4
Murtaza_Ghafoor
Resolver II
Resolver II

My suggestions are 



Recommendation:

  1. Enable “Allow version change tracking” on the base table(s) used by the entity.

  2. Sync those tables directly via Azure Synapse Link → Fabric → Lakehouse/Warehouse.

  3. If entity-level logic is required, recreate that logic in Fabric using Dataflows Gen2 or SQL views over synced table

Hi @Ramkishor ,
Thanks for reaching out to the Microsoft fabric community forum. 

 

I would also take a moment to thank @Murtaza_Ghafoor  and @Ritaf1983   , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

I hope the below details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .

Please go through the below document which may help you in resolving the issue.

Row version change tracking for tables and data entities - Finance & Operations | Dynamics 365 …

 

 

Best Regards, 
Community Support Team  

Hi @Ramkishor ,

I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We’re always here to support you .

 

Best Regards, 
Community Support Team 

Ritaf1983
Super User
Super User

Hi @Ramkishor 

It looks like you’re mixing up a table and a data entity.
In Power Apps or Synapse Link, only physical Dataverse tables that have Change Tracking enabled can be synced.
Data entities from F&O are virtual objects, not real tables — so even if you enable “Allow row version change tracking,” they won’t appear in Power Apps.
That property only applies to actual SQL/F&O tables, not to entities.

To make it work, you have a few options:

Use the underlying table instead of the data entity and enable Change Tracking on it.

If you need the same structure as the entity, load the data into a real Dataverse table using Dual-Write, Dataflows, or ETL — then enable Change Tracking there.

Alternatively, use Export to Data Lake or Synapse Link for F&O and connect Fabric to that output.

Bottom line – you can’t make a data entity visible in Power Apps just by turning on Change Tracking.
Only physical tables with Change Tracking are supported.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

Regards,
Rita Fainshtein | Microsoft MVP
https://www.linkedin.com/in/rita-fainshtein/
Blog : https://www.madeiradata.com/profile/ritaf/profile

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

Check out the November 2025 Power BI update to learn about new features.

Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors