Pipeline Copy Data decimal handling from Oracle source
Pipeline "copy data" activities built against and Oracle source with a Fabric warehouse target do not handle precise decimal values correctly.
For example, an Oracle NUMBER(3,2) should be able to copy to a Fabric warehouse decimal(3,2) without issue, but because of the intermediate staging to Parquet format, we get an error:
ErrorCode=DWCopyCommandOperationFailed,
'Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,
Message='DataWarehouse' Copy Command operation failed with error 'Column 'the column name' of type 'DECIMAL(9, 3)' is not compatible with external data type 'Parquet physical type: DOUBLE', please try with 'FLOAT'.
We would expect the data to be staged to a Parquet DECIMAL type and convert correctly into the Fabric warehouse.
Recent ideas
Separate Interactive and Background Compute Allocation to Prevent Throttling of Live Reports
Problem Statement When Fabric capacity utilization reaches or exceeds 100% in the last one-hour window, end users experience significant disruptions when accessing Power BI Fabric live reports. This...TilakArani5 minutes agoNew MemberNew0Views0likes0CommentsAccessibility issue in the Share dialog of embedded Power BI reports
Accessibility issue in the Share dialog of embedded Power BI reports I would like to share an accessibility finding identified while testing an embedded Power BI report published as part of the cont...ugartema45 minutes agoAdvocate INew62Views10likes1Comment- fbcideas_migusr3 hours agoNew MemberUnder Review381Views12likes4Comments
Display Table[Column] instead of Column Name in Conditional Formatting Dialogs
In large-scale Power BI semantic models, it is common to have identical column names across multiple fact and dimension tables. Examples include columns such as Status, Category, Region, Employee ID,...Manickambeeie5 hours agoNew MemberNew5Views0likes0Comments