Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
dhasharadh
Creator III
Creator III

mis matches in a table due to new columns added in a dimension...??

Hi Experts,

Need help on the below issue.

as a part of our complete Business plan changes, we have to chnages all our Phase1 reports as per the latest plan we call them as Phase2 reports, we have around 6 Qlik apps and all are fine.

Phase1 : all reports will show till aug 2017

Phase 2 : along with phase1 reports data with new business logic it will show data till Today.

Validation : we validate the phase 2 reports by comparing the results with phase1 reports they have to macth till aug 2017(as we are using the same fact tables till Aug, and there are some changes in the dim tables)

all our reports are fine but coming to one report called GBR-Phase2 not in sink with GBR-Phase1 App.  and we are getting the below few Tariff plans as extra and which might be causing other Tariff plans to show mis matches when we compare.

Am Completely Confused , why this mis macthes...can any one guide me to identify the route cause for this.

when i compare both the results in an excel i found the below few columns are coming extra for Phase2 app.

Many Thanks in Advance.

   

   

4G Unlimited + Unlimited23
1500minutes+1GBData1
2500 Minutes + 2GB Data2
3 Replies
avinashelite

check your data association , data granularity and model once ...

share the sample so that we could dig more

dhasharadh
Creator III
Creator III
Author

Thanks avinash,

is adding new columns in a dimension is the reason for mis matches in the existing columns ??

Some thing like below is possible. like D and E are the new records coming in Phase2 which is effecting the existing Record counts. is it the cause for that issue of mis matches..??

   

Phase1Phase2
NameShareNameShare
A12A12
B13B11
C14C10
D3
E5
avinashelite

Yes definitely , because the values are getting split/distributed with the new dimension values and the old values are not retained so the comparison will have an impact here ..one way to address this is , ask the upstream to send the previous value where the values where tagged for E.G. in your case   B earlier it was 13 and now the values is 11 so where this additional value went ? to D and E ...