Skip to main content

Hi everyone,

 

I am building a View, where I want to list some KPIs from my Knowledge Model on top of a table.

For that purpose, I first chose an Attribute List, as I see in the documentation that it can take KPIs as Input. Then I tried a KPI List instead, with the same KPIs from the Knowledge Model, and I noticed that the numbers displayed in each KPI are considerably different, when I use one component or the other. (I checked it and the numbers on the KPI List are right, and differ greatly from those in the Attribute List).

 

Does anybody know what the cause of this discrepancy might be?

 

How do Attribute Lists function overall? When should I use them? I was not able to find further information about that in the docs.

 

Thank you very much!

 

Javier

Hi @javier.desar ,

 

the KPI_List is the right component to use for showing your kpis numbers.

 

the attribute List tackles a specific object, so for example let say you have many Invoices with some attributtes, you will use the KPI_LIST to calculate for example Total Sales of all invoices, if you want to know more details about a specific Invoice you will use then attribute list of this invoice, e.g. Vendor details or even calculate a kpi for only this specific invoice (cycle Time) etc...

So The Attributte List is great to use with Profile Views.

I hope that helps

Very clear, I will go forward with the KPI list.

just a question on top of it to understand it completely :) so that means that I should filter the record, following the example, for an specific invoice, before showing it on the attribute list? or is it made by default, by choosing a random one if I do not select it in advance?

 

thank you @Rashid Laamouri 

Very clear, I will go forward with the KPI list.

just a question on top of it to understand it completely :) so that means that I should filter the record, following the example, for an specific invoice, before showing it on the attribute list? or is it made by default, by choosing a random one if I do not select it in advance?

 

thank you @Rashid Laamouri 

I am glad that you get the difference very clear.

You don't need to filter a record because when you create a record you set up first an identifier (Invoice_ID in our example)and this will be selected by default.

When you see this example from the celonis Documentaion:

image when setting up a profile view you need to select a column (here Vbeln instead of invoice_id) after saving this setting, the values of the column Vbeln will be clickable and you just click on a specific Vbeln and you get the attribute List of this specific Vbeln.

I encourage you to read this documentation, there are many Training videos that shows a step by step set up of a profile view so you will get a better idea.

Great, thank you for the explanation!

Community Code of ConductAccessibility statement