Forum Discussion
Fabric Issue
Hi vallem_reddy ,
That error usually means your source table or file doesn’t have the column Fabric is expecting, in this case “IS_EXPIRED”. Sometimes this can happen if the source schema changed but the delta metadata hasn’t been refreshed on the Fabric side.
Can you try re-importing or refreshing the schema in your dataset? If you’re using a dataflow or pipeline, there’s usually an option to “refresh schema” or “import schema” again. That’ll make sure Fabric sees all the latest columns from your source.
Also, double check that the file or table you’re reading from actually has the IS_EXPIRED column and it’s spelled exactly like that (case sensitive sometimes).
Let me know if you still hit the same error after refreshing, I’ve seen this get fixed by a re-import most of the time.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
Thankyou, burakkaragoz, for your response.
Hi vallem_reddy,We sincerely appreciate your inquiry posted on the Microsoft Fabric Community Forum.
As per my understanding, since the column IS_EXPIRED no longer exists in your source, but Fabric continues to expect it, this issue is likely due to stale schema metadata cached within Fabric. This is particularly common when working with Delta Lake or schema-bound sources.
Kindly follow the steps outlined below, which may help resolve the issue:
- Manually verify your Delta table’s metadata to ensure that the column has been completely removed by executing: DESCRIBE DETAIL delta.<your-table-path>;
- If refreshing the schema does not resolve the problem, please try removing and then re-adding the source transformation in your Dataflow Gen2 or Pipeline activity. This will force a fresh metadata load.
- For Delta tables, ensure that the schema is compacted and that no older snapshots retaining the IS_EXPIRED column are present.
If you find our response helpful, we kindly request you to mark it as the accepted solution and provide kudos. This will assist other community members who may encounter similar issues.
Should you have any further queries, please feel free to reach out to the Microsoft Fabric community.
Thank you.
Thankyou, burakkaragoz, for your response.
Hi vallem_reddy,
We sincerely appreciate your inquiry posted on the Microsoft Fabric Community Forum.
As per my understanding, since the column IS_EXPIRED no longer exists in your source, but Fabric continues to expect it, this issue is likely due to stale schema metadata cached within Fabric. This is particularly common when working with Delta Lake or schema-bound sources.
Kindly follow the steps outlined below, which may help resolve the issue:
- Manually verify your Delta table’s metadata to ensure that the column has been completely removed by executing: DESCRIBE DETAIL delta.<your-table-path>;
- If refreshing the schema does not resolve the problem, please try removing and then re-adding the source transformation in your Dataflow Gen2 or Pipeline activity. This will force a fresh metadata load.
- For Delta tables, ensure that the schema is compacted and that no older snapshots retaining the IS_EXPIRED column are present.
If you find our response helpful, we kindly request you to mark it as the accepted solution and provide kudos. This will assist other community members who may encounter similar issues.
Should you have any further queries, please feel free to reach out to the Microsoft Fabric community.
Thank you.