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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
vallem_reddy
New Member

Fabric Issue

The source column expected is not present in source side. Still I am getting this error.  ErrorCode=SourceColumnIsNotDefinedInDeltaMetadata,'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=Source column is not defined in delta metadata. Column name: IS_EXPIRED, file name: . Please import schema to reflect the latest.,Source=Microsoft.DataTransfer.ClientLibrary,'

 

2 ACCEPTED SOLUTIONS
burakkaragoz
Community Champion
Community Champion

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.

View solution in original post

v-pnaroju-msft
Community Support
Community Support

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:

  1. Manually verify your Delta table’s metadata to ensure that the column has been completely removed by executing: DESCRIBE DETAIL delta.<your-table-path>;
  2. 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.
  3. 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.

View solution in original post

3 REPLIES 3
v-pnaroju-msft
Community Support
Community Support

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:

  1. Manually verify your Delta table’s metadata to ensure that the column has been completely removed by executing: DESCRIBE DETAIL delta.<your-table-path>;
  2. 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.
  3. 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.

burakkaragoz
Community Champion
Community Champion

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.

Worked, thank you very much. Appreciate it.

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June FBC25 Carousel

Fabric Monthly Update - June 2025

Check out the June 2025 Fabric update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.