Hello,
I have come across something that I haven't managed to understand while working with dataflows. In one of my tables (after importing the dataflow in a powerbi report), some rows where duplicated (some doubled, some tripled) while the majority of them were correct, but when I went back to the table editor of the dataflow, no duplicate showed up. Because I thought the discrepancy was explained by the fact that while editing the dataflow you're only working on a preview, I reduced the dataflow to a single row as seen here :
But when I imported this table in a power BI report, I received two identical rows as seen here :
As anyone encountered something similar and know the explanation/solution to this problem ?
Thank you in advance,
Valentin
Hi,
I had this problem and had to take off the Incremental Refresh on the Power BI Service dataflow to remove the duplicates.
Hi @Anonymous - is it possible that the Join step (#"Requetes fusionnes 1") is creating the duplicate when expanded in the following step. If you moved your Filter in the final step (#"Lignes filtrees") before the join step, does the duplication appear now? If it does, this sugggests join join is Many to Many, not Many to One. Therefore you will need to remove the duplicate from the table on the Right Side of the join.
Hi @Anonymous ,
Please try the workaroud in this thread:
Make sure your target table has a Key set up that uniquely identifies each row (maybe just the name? or a composite of name and type?) Dataflow will pick up on the key on the table and for all the rows to be imported it will use the key to upsert instead of just inserting.
Best Regards,
Community Support Team _ kalyj
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hello,
I've tried adding a key using the Table.AddKey function (and while specifying that it is a primary key) on my single-row table, but I still get a duplicate when I import it.
Best Regards,
Valentin
Hi! @Anonymous
I would recommend you try to repro this with another Dataflow(DF). If the other DF is also giving you the same result then try changing the source. If that also doesn't help, then please raise a ticket to MS.
