Forum Discussion
Helper IData Variances between dataflow output and Lakehouse data
Thanks to everyone for the responses and guidance in resolving the issue.
Steps tried:Setting amount column to Decimal.Type before writing into lakehouse - Failed
Pre-creating the table in lakehouse before writing into it and defining its data type - Failed
Ensuring the amount column in each of the combined queries was set to Decimal.Type (as last step) prior to combine - Failed
What eventually worked for me was setting the amount column to Decimal.Type at the point of import into every query that was part of the Table.Combine. I also set it as the last step. I did this as well for every column (numeric) that interacted/contributed to the amount column in each of the queries.
I hope this helps someone who faces the same issue. It was literally driving me nuts...
Super UserHi sufregs,
After the Table.Combine step, could you check whether the dataset in Power Query contains more or fewer rows than the table in your Lakehouse? The easiest way is to compare the row counts in both places, or validate by checking the sum of your amount column.
That should help you identify what’s happening before or during the combine step. One or more source tables used in the Table.Combine step might already be filtering rows, or the combine itself could be introducing duplicates.
Hope this helps. If so, please give kudos 👍 and mark as Accepted Solution ✔️ to help others. If you resolved your question, let us know what worked for you.
Helper IHi. The row count is the same before and after the combine step.