topic Re: Year field is not interpreted by Insight advisor in Insight Advisor

field

Qlik1_User1 — Fri, 05 Sep 2025 05:52:56 GMT

Hi,

I am using and i have a field as Ryr which is numeric (checked via isnum() as well) but when I am searching in its not interpreting it .. please suggest what is missing..

This is the data i am using, when i am searching a simple query like "premium for year" its giving below result, which is incorrect ,pls help

LOAD * INLINE
[
Client,RYear,Premium
A, 2019, 100
A, 2020, 200
B, 2021, 300
B, 2022, 400
B, 2023, 500
C, 2019, 600
C, 2020, 700
D, 2024, 800
D, 2025, 900
E, 2020, 1000
];

@hugo_andrade @igoralcantara @marksouzacosta @marcus_sommer

Re: Year field is not interpreted by Insight advisor

Qlik1_User1 — Wed, 13 Aug 2025 09:55:17 GMT

@kiseke8485 Please click on the image it will open up.

Re: Year field is not interpreted by Insight advisor

Qlik1_User1 — Mon, 01 Sep 2025 10:27:32 GMT

Hi @kiseke8485

This is the data i am using, when i am searching a simple query like "Show premium for year 2023" its giving below result, which is incorrect ,pls help
NOTE: Using HUB level IA chat bot.

Vocabulary

Logical Model

LOAD * INLINE
[
Client,RYear,Premium
A, 2019, 100
A, 2020, 200
B, 2021, 300
B, 2022, 400
B, 2023, 500
C, 2019, 600
C, 2020, 700
D, 2024, 800
D, 2025, 900
E, 2020, 1000
];

Re: Year field is not interpreted by Insight advisor

marcus_sommer — Tue, 02 Sep 2025 11:56:37 GMT

Never worked with this tool but the reason might be that Year <> RYear respectively the call has no valid references to the data.

Re: Year field is not interpreted by Insight advisor

Qlik1_User1 — Tue, 02 Sep 2025 13:15:21 GMT

@marcus_sommer Thanks, in Vocabulary we have mentioned the synonym for Ryear as Year which will solve that issue but still its not working.

Re: Year field is not interpreted by Insight advisor

marcus_sommer — Tue, 02 Sep 2025 13:42:04 GMT

Qlik acts case-sensitive - therefore check how the fields are really written because: Ryear <> RYear (like named in the inline-load).

Re: Year field is not interpreted by Insight advisor

hugo_andrade — Tue, 02 Sep 2025 14:51:04 GMT

Hi @Qlik1_User1,

Let's go step by step.

Are you able to get the Insight Advisor, ask to Show apps and see the app in question?

Let's troubleshoot step by step?

Re: Year field is not interpreted by Insight advisor

Qlik1_User1 — Wed, 03 Sep 2025 07:01:19 GMT

@hugo_andrade Yes I am able to get the app name.

Re: Year field is not interpreted by Insight advisor

Amit_Prajapati — Wed, 03 Sep 2025 08:05:35 GMT

Hi, In logical model mention classification as dimension instant of year and try !

Re: Year field is not interpreted by Insight advisor

Qlik1_User1 — Wed, 03 Sep 2025 10:09:49 GMT

@Amit_Prajapati Tried that as well but that too didn't work

Re: Year field is not interpreted by Insight advisor

Amit_Prajapati — Thu, 04 Sep 2025 10:06:34 GMT

I noticed that Insight Advisor needs a full date to work properly, so I used April 1st as the default day and month, and added the correct year for each entry.

LOAD * INLINE
[
Client,Date,Premium
A, 4/1/2019, 100
A, 4/1/2020, 200
B, 4/1/2021, 300
B, 4/1/2022, 400
B, 4/1/2023, 500
C, 4/1/2019, 600
C, 4/1/2020, 700
D, 4/1/2024, 800
D, 4/1/2025, 900
E, 4/1/2020, 1000
];

Then I created a Calendar group in the logical model.

Now, when I ask Insight Advisor to Show premium only for Year 2023 , it correctly returns 500.

Output :

Re: Year field is not interpreted by Insight advisor

Qlik1_User1 — Fri, 05 Sep 2025 05:49:18 GMT

Hi @Amit_Prajapati , thanks for the suggestion on year field but isn't it is a limitation on Qlik side.
Also, If i have a fields says yearmonth have values like '202401', 202402,.. 202412 and so on.
In that case how Insight advisor will work, as this is for required as well for user input

Re: field

Amit_Prajapati — Fri, 05 Sep 2025 07:14:25 GMT

From main script you can change the date formats or else you can give it date formate while using in script with the help of date function