Forum Discussion
New Measures corrupts data integrity
Community ChampionThere's no great mystery.
Under "in my report all lookss good" one of the columns is a measure (it looks like SUM(Wert)). The values are being calculated for each row but there will be blank values for Art = Aufwand so powerbi removes them.
In the last table, there are two measures SUM(Wert) and Measure. Measure evaluates to 1 for any row (it's a constant) so powerbi displayes the row so you now see rows you didn't see before
------
Also, the first picture showing the join results does not look good to me at all. It shows me 2 unrelated tables jammed together. If I asked you what the primary key (in database terms) is for that table, what would it be?
Hi HotChilli , thank you for looking into that.
Actually the Column "Art" is in the table LU_KONTORAHMEN, which is joined to the merged table. so all entries for account 7109 should get the same "Art"-Value assigned.
Yes, "Wert" is measure - but even if i show all columns (which would lead to SUM(Wert) == Wert, because i am on the lowest aggragation level), this happens.
I understand the first picture of the table ISTSOLLVGL looks ugly. but this is a full outer join showing accounts with budgets and actual bookings. it is possible that we dont have a match, but still need those value in the report.
my join key is period, branch and account.
to avoid null values in my non-measure values, i have created coalesce-similiar columns, where i use a logical like this:
branchall=
if table1.branch is null, then use table2.branch
etc.
hope this makes sense 🙂 if i can provide you with any info (data dump ..) to support you help, let me know!
really appriciate it!
i have cleaned up a bit an just left the relevant columns:
ISTSOLLVGL
:
Lookup Table for column "ART":
both are in a N:1 relationship based on Konto<>KontoAll