Issue | Description |
|---|---|
CCON-105770 | When you create a Microsoft Fabric Data Warehouse target at runtime where incoming string fields have a precision greater than 4000, the mapping automatically sets the precision to 8000 in the target without preserving the precision of the incoming field. (July 2025) |
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-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 |