Issue | Description |
|---|---|
CCON-103782 | When you map a date or datetime field in the source to a string data type in the target, the mapping writes data to the target in the MM/dd/yyyy hh:mm:ss format, a 12-hour format, instead of the MM/dd/yyyy HH:mm:ss format, a 24-hour format. This results in a data mismatch with the source. (April 2025) |
Issue | Description |
|---|---|
CCON-105123 | When you select Update Override in the Microsoft Fabric Data Warehouse target properties to override the default update SQL statement that the Secure Agent generates and also enable alter and apply changes to refresh the schema in the task, the task does not alter the target schema or add new fields from the source. (April 2025) |
CCON-102404 | Even though you cannot read from multiple Microsoft Fabric Data Warehouse objects, the Multiple Objects option appears in the Source Type property. When you configure a Source transformation to read from multiple Microsoft Fabric Data Warehouse objects, the mapping fails with the following error: [ERROR] Failed to run the Microsoft Fabric Data Warehouse mapping because of the following error: [Invalid column name 'c_smallint'.] (November 2024) |
Issue | Description |
|---|---|
CCON-103362 | When you write to a Microsoft Fabric Data Warehouse target, the mapping might fail with the following error if the staging table in Microsoft Fabric Lakehouse is not accessible: Failed to execute the command after the 4 retry attempts and the following error occurred: [java.lang.RuntimeException: java.lang.RuntimeException: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'TestSyncLH.dbo.TempTable_e305ce21-fc49-4f08-ae7d-638e63bbfaf7'.] Workaround: To resolve the issue with the staging table in Microsoft Fabric Lakehouse, configure a pre-SQL command in the Microsoft Fabric Data Warehouse target properties that queries the Microsoft Fabric Lakehouse, and then run the mapping again. (February 2025) Microsoft ticket number: 2501090040011982 |