Dataverse Shortcut Delta Table Schema Not Updating After Source Column Precision Change

[akshaykhaneja]

I have a Dataverse shortcut in our Fabric Data Warehouse that syncs data from Power Apps/Dataverse into a Delta table in OneLake (Bronze layer).
Original State:

Dataverse columns latitude andlongitude were initially configured with limited decimal precision
Dataverse shortcut was created and Delta table schema was established with decimal(x,2) (2 decimal places)

Current State:

Source Dataverse columns have been updated to store full coordinate precision (8+ decimal places)
Power Apps shows correct full precision values:

Latitude: 32.81658800
Longitude: -117.007371...

Problem:

Delta table in OneLake Bronze layer still truncates values to 2 decimal places:

Latitude: 32.81
Longitude: -117.00

Multiple refresh operations have been performed, but schema does not update
Only data refreshes, not schema structure

[ssrithar · Accepted solution]

Hi @akshaykhaneja ,

Dataverse shortcuts in Fabric infer and lock the Delta schema at creation time. Subsequent Dataverse metadata changes (such as increasing decimal precision) do not propagate to the shortcut schema. Refresh only reloads data using the existing schema, which is why values are truncated. Currently the only way to update the schema is to recreate the shortcut, or to cast the columns to higher precision in a downstream Silver layer.

If this post helps, then please appreciate giving a Kudos or accepting as a Solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!

[v-sgandrathi]

Hi @akshaykhaneja,

we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.

Should you have any further questions, feel free to reach out.

Thank you for being a part of the Microsoft Fabric Community Forum!

[v-sgandrathi]

Hi @akshaykhaneja,

We haven’t heard from you on the last response and was just checking back to see if your query was answered.
Otherwise, will respond back with the more details and we will try to help.

Thank you.

[v-sgandrathi · Accepted solution]

Hi @akshaykhaneja,

Thank you @ssrithar for your response to the query.

Alongside the previously mentioned points, it's important to highlight that this behavior is intentional in the current Fabric Dataverse shortcut implementation, and currently, in-place schema evolution for shortcuts is not supported. Additionally, there is no automatic detection or alerting if Dataverse metadata (like precision or scale changes) differs from the locked Delta schema, which means data accuracy can be affected if not manually checked.

For governance and operations, it’s best to treat Dataverse shortcuts as schema-static ingestion objects and add a validation step to your data pipeline whenever Dataverse column definitions are updated. If recreating the schema isn’t possible due to downstream dependencies, another approach is to store raw values as strings in the Bronze layer (when feasible) and apply correct typing at the Silver or Gold layers to prevent irreversible truncation.

Thank you.

[ssrithar · Accepted solution]

Hi @akshaykhaneja ,

Dataverse shortcuts in Fabric infer and lock the Delta schema at creation time. Subsequent Dataverse metadata changes (such as increasing decimal precision) do not propagate to the shortcut schema. Refresh only reloads data using the existing schema, which is why values are truncated. Currently the only way to update the schema is to recreate the shortcut, or to cast the columns to higher precision in a downstream Silver layer.

If this post helps, then please appreciate giving a Kudos or accepting as a Solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!