I have two QVDs: one is a Fact table, and the other is a LinkTable.
I checked the QVDs by loading them separately, and the same rows appear in each one. However, when I load the entire application together, some rows disappear.
I found some examples of the missing data, but it doesn't make any sense.
If I load the LinkTable without the field that links to the FactTable, the data appears again.
I doubt that there any data are disappearing. Much more likely is that there are missing key-values in any side and then the set selections and/or the object-dimensionality will exclude some data from your view.
The cause is a poor respectively unexpected data-quality. This means that either the data-quality will be improved (ideally within the source or on the Qlik side by removing/replacing/populating the invalid data) or by a change of the data-model (not associating the tables else merging them - usually per concatenation).
Please provide a sample of the data, if you can replicate this in another app and send the application this would help too. This can be due to a few things like joins or alternative keys, like a syn key if the field is added... Just throwing some thoughts out here.
But seeing this would be the easiest way to assist you in solving your problem.
If you cant provide the data or cannot replicate this issue using "other data" perhaps a screenshot of the data model viewer might assist. (WIth and Without the field)
Regards Jandre
Mark the solution as accepted that solved your problem and if you found it useful, press the like button! Check out my YouTube Channel | Follow me on LinkedIn
Just found the problem. Thanks! But I still don’t understand it.
I have a table that contains access information, and it is interfering with my Fact table. Some territories were deleted by the users without my knowledge.
From my understanding, if a key doesn’t exist in both tables, it shouldn't be possible to filter by that key, but the data in the Fact table should still be there.
Example:
Access Table (Territory and User Information): 1, userA 2, userB
It's not missing - it's there. At least if you look directly on the fact-table. But if you for example build a view with territory as dimension and count(user) as expression you create a join between territory and user and there the missing/null/wrong key-values will have an impact.
The results in the views are not mandatory wrong - the count() will be correct and that one territory isn't displayed is also correct because there are no data for the given combination. If another result is wanted it will need some extra/adjusted steps within UI (is restricted and causing side-effects) or like above hinted some adjustments to the data-set and/or the data-model.
That’s exactly my point. I was checking only a single field—the one from the Fact table—and it wasn’t there. This happened in a simple table view with only that field.
For example, if I have three rows with a value of 10 each and perform a SUM() in a KPI without applying any other fields or filters, the expected output should be 30. However, I was getting 20 instead.
