Skip to main content
Solved

Parameter Input just like in Excel - VIEWS

  • May 28, 2024
  • 4 replies
  • 11 views
julia.bauer
Level 9
Forum|alt.badge.img+1

Hello everyone,

 

the following KPI is implemented within a view:

 

Safety Stock / Sum Demand of the next 12 M (= Coverage Range [Years])

 

This coverage range is visible within a table in the view.

 

I now want to incorporate the KPI as a filter. I created an attribute on the basis of the KPI:

image 

My Celonis users now want to filter the coverage range individually e.g. >0.5 and <0.6 or >1 etc. In Excel this is very easy to do. Does this also somehow work in Celonis?

As of right now I can only select the possible values from a list and without some intelligent clustering.

 

Thanks!

 

Best regards,

Julia Bauer

Best answer by matt.witty13

Hey @matt.witty13 ,

 

thanks for your reply. Yes that's the solution that I have wanted to implement. However, my users want a more flexible way to filter. This is the number filter from Excel which my users are accustomed to:

imageFrom my understanding and my experience, I have not come across which such possibillities in Celonis, yet? Have you?

 

Thank you!

 

Best regards

Julia

So the only thing I can think of is doing a Manual Input box and set it to a variable like ${Low_End} and one that's ${High End}. Then setting a view filter that's

 

FILTER [KPI] >= {low end} and [KPI] <= {high end}

    4 replies

    matt.witty13
    Level 10
    • matt.witty13
    • Level 10
    • 123 replies
    • May 28, 2024

    You can probably build a Quick Filter and have it be a button. In your knowledge model, build a Filter component that's

     

    FILTER ([the kpi] >.5 AND <.6) or ([the kpi] > 1);

     

    Something like that. Then your users can click the filter button and automatically see what they want to see.

    julia.bauer
    Level 9
    Forum|alt.badge.img+1
    • julia.bauer
    • Author
    • Level 9
    • 58 replies
    • May 29, 2024

    You can probably build a Quick Filter and have it be a button. In your knowledge model, build a Filter component that's

     

    FILTER ([the kpi] >.5 AND <.6) or ([the kpi] > 1);

     

    Something like that. Then your users can click the filter button and automatically see what they want to see.

    Hey @matt.witty13 ,

     

    thanks for your reply. Yes that's the solution that I have wanted to implement. However, my users want a more flexible way to filter. This is the number filter from Excel which my users are accustomed to:

    imageFrom my understanding and my experience, I have not come across which such possibillities in Celonis, yet? Have you?

     

    Thank you!

     

    Best regards

    Julia

    matt.witty13
    Level 10
    • matt.witty13
    • Level 10
    • 123 replies
    • Answer
    • May 29, 2024

    Hey @matt.witty13 ,

     

    thanks for your reply. Yes that's the solution that I have wanted to implement. However, my users want a more flexible way to filter. This is the number filter from Excel which my users are accustomed to:

    imageFrom my understanding and my experience, I have not come across which such possibillities in Celonis, yet? Have you?

     

    Thank you!

     

    Best regards

    Julia

    So the only thing I can think of is doing a Manual Input box and set it to a variable like ${Low_End} and one that's ${High End}. Then setting a view filter that's

     

    FILTER [KPI] >= {low end} and [KPI] <= {high end}

    julia.bauer
    Level 9
    Forum|alt.badge.img+1
    • julia.bauer
    • Author
    • Level 9
    • 58 replies
    • May 31, 2024

    Hey @matt.witty13 ,

     

    thanks for your reply. Yes that's the solution that I have wanted to implement. However, my users want a more flexible way to filter. This is the number filter from Excel which my users are accustomed to:

    imageFrom my understanding and my experience, I have not come across which such possibillities in Celonis, yet? Have you?

     

    Thank you!

     

    Best regards

    Julia

    Thank you @matt.witty13 !

    That's a great alternative even though it is not as flexible as Excel - but I think our users can work with it :-)


    Community Code of ConductAccessibility statement