Error In KPI Document, the indicator of speedometer or other widget does not change

Question

Error In KPI Document, when the data displayed the indicator of speedometer or other widget type does not change when I change the driver value in filtering ? 

Answer 1

Hi saraalfatih,

After creating the document following the official documentation, you need to use the KPI scheduler to schedule the KPI to run and make sure it runs without errors.

Also, you need to add some analytical drivers to your document in order for execution to filter your data.

Greetings
Alberto

Comments

I already did all of that but still in the same situation. The indictor does not move any where 

---

Hi saraalfatih,

can you send me more details regarding the configuration of the KPI and the document so I can try to replicate it on my environment?

Thank you.

Greetings
Alberto

---

Hi Alberto,

Iam using knowage data source ' CacheDs'  and using Meatsure/Rule Definition this query:

SELECT
product_name
,store_city

,the_month
,SUM(store_sales) as store_sales4
,SUM(store_cost) as store_cost4
,SUM(unit_sales) as unit_sales4
,t.the_year as YEAR
FROM sales_fact 
WHERE the_year=@YEAR_IN
 GROUP BY
 product_name
 ORDER BY store_sales DESC

After that I used '  ( store_sales4 - store_cost4 )  / unit_sales4) ' as a KPI Definition.

And then add a KPI Scheduler  ( using KPI Definition) in Filter tap I used LOV with year . Then using frequencies (start date, end date) and execute and every thing went well.

finally I went to create the KPI Document in KPI designer I choose Widget and add KPI Association then choose ( View as speedometer) with min and max value .

After all this I add analytical driver with value as years and output parameters as numbers.

then saved all that and execute the document but still the same issue in indicator.

Thank you

---

Hi saraalfatih,

I see your KPI did not run correctly, because you don't have a Success Count other than 0. Are you sure the CacheDs data source contains the sales_fact table you are querying?

Also, you can remove the WHERE condition from your query because the KPI filter is applied by matching aliases (as documented near to Fig. 629 "Then it is mandatory that the URL of the analytic driver must match the aliases of the attribute on which you have defined the grouping").

Also, when associating the LOV to the scheduler it is necessary to remember that "In case the LOV option is chosen, remember that the LOV must return one unique value." as documented near to Fig. 618.

Let me know if your KPI is working as a result of these changes.

Thank you.

Greetings

Alberto