The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
I have two tables with a single-direction one-to-many relationship, joined on placement[Id] and UserFieldValuePivot[RecordId].
The issue is that, when I try to add userfieldvaluepivot fields to a table visual already displaying placement ids, the visual will show two rows per id that has a value in that field - one blank and one with the value.
EG Id is from placement, and RecordId and Agency come from UserFieldValuePivot
Is this normal behaviour? Or a bug? I can't work out why a blank row is duplicated. Ideally it would show the id only ONCE for one input for Agency.
For more context, I have made the UserFieldValuePivot table as a pivot of a table called UserFieldValue which pivoted on entity UserFieldValuePivot[Index]. When I previously pivoted around UserFieldValuePivot[RecordId], this issue did not arise.
Can anyone help??
The many table is a pivot table I created from another table called UserFieldValue.
Solved! Go to Solution.
your categorical data should always come from the one side and not the many, that is why you have a cartesian. if you need the agency, it should sit on the one side, otherwise this will happen because the many side will have different results. but that also depends on what key you used to link these 2 bits data together, the granularity might also be incorrect.
Proud to be a Super User!
Hi @Beth_H ,
Have you solved your problem? If so, can you share your solution here and mark the correct answer as a standard answer to help other members find it faster? Thank you very much for your kind cooperation!
Best Regards,
Clara Gong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
your categorical data should always come from the one side and not the many, that is why you have a cartesian. if you need the agency, it should sit on the one side, otherwise this will happen because the many side will have different results. but that also depends on what key you used to link these 2 bits data together, the granularity might also be incorrect.
Proud to be a Super User!