Values Displayed as NULL in One Specific Hub – Same Variables Work in Others

[aaaaaaaaa]

I am experiencing an issue with Qlik Sense where certain values present in Excel or in the database are not correctly loaded into Qlik and instead appear as NULL (shown as a dash ). This problem occurs across all sheets within a specific hub, while in other hubs the data is correctly retrieved from both the database and the Excel files.

To clarify, a hub is a collection of related sheets, each hub having its own set of sheets.
For example, there are variables or fields that are shared across all hubs and sourced from the same Excel file, but they are not loaded correctly only in this specific hub. In all other hubs, they are retrieved and displayed as expected. Therefore, I know this issue is localized within Qlik for that specific hub.

Additionally, this error did not occur previously and the script has not been changed. The values shown as NULL are only those dated before a specific cutoff date, while all values after that date are loaded correctly.

[robert_mika]

Did you compare the values?

Did you try to move the sheets between hubs to see if that is the issue?

What is the part that Qlik load as NULL?

[aaaaaaaaa]

First of all, thank you for your interest and support.

Yes, I had already tried everything you suggested. I also created a new hub using the same script as the non working one, but it still doesn’t work. I want to emphasize that the script has never been modified over time, and it used to work fine.

I also considered it might be a memory issue, so I tried reducing the time range used in the script, but nothing changed.

At first, I thought it might be a problem with the cloud provider hosting our Qlik Sense service, but I’m now inclined to rule that out, as we haven’t received any official notification of recent changes or interventions from their side.

To answer your question, "What is the part that Qlik loads as null?"  if I try to call the variables in a table, some of them consistently show null values, at least until a recent date, after which they start working again as expected.

[Vegar]

It doesn't need to be null values you are seeing,  it could also be missing values.

Consider this data model.

* Load the Transaction table */

Transactions:

LOAD * INLINE [

    id, Date id, Amount

    1, 20231232, 125

    2, 20240101, 100

    3, 20240102, 150

    4, 20240103, 75

    5, 20240104, 200

];

/* Load Master Calendar

   This calendar covers the transaction dates plus three additional days.

*/

MasterCalendar:

LOAD * INLINE [

    [Date id], Date, Month

    20240101, 2024-01-01, Jan

    20240102, 2024-01-02, Jan

    20240103, 2024-01-03, Jan

    20240104, 2024-01-04, Jan

    20240105, 2024-01-05, Jan

    20240106, 2024-01-06, Jan  

];

If you create an object using Date as dimension then you will have null values for 2024-01-05 and 2024-01-06. Similar you will not find a any Date associated as 2023-12-31 (it is missing in the Master Calendar) In both cases there is not a null values issue, but a missing value issue. 

Could it be something related to this that is causing you problems?