expression with values geater than dedicated value

[Vlad12]

Hi there, It's extremely simple in any programming language, but I cannot get how it define in qlik.

I have two columns: ID and Price. I want to show only IDs with prices which is greater than 150. I've read more then 10 topics in this community and found multistring guidelines. But I believe it should be extremely simple in qlik sense

Just smth like: 

sum(only(amount>=150))

but it doesn't work. Could you help me?

[marcus_sommer]

As condition within an expression you may apply:

sum({< Price = {">=150"}>} ID)

and as calculated dimension it might be something like:

aggr(only({< Price = {">=150"}>} ID), ID)

- Marcus

[Vlad12]

Maybe I'm stupid, but your expressions don't work

How I can just remove the id from the chart? 

[Vlad12]

Is it possible to use Python for filtering in the Qlik? 

[marcus_sommer]

Make sure that you use the right fields - above you mentioned ID and Price but the fields in your expression are id and prices. Qlik is case-sensitive for the naming of tables, fields and variables and doesn't forgives any mis-spelling.

Further the example is only to filter field-values and not filtering expression-results.

Why do you want now to remove the ID from the chart? In your question you said you want to display them ...

- Marcus

[marcus_sommer]

AFAIK no - at least not within the native Qlik, maybe within any extensions and/or mashups. But IMO it doesn't makes sense.

- Marcus

[Vlad12]

I've already spent 2 hours on that) Such things are obvious in SQL, Python, etc. but not here

[Vlad12]

may be I was wrong, I just need to display all IDs with prices which higher than 150. Of course I check the spelling

[OmarBenSalem]

change your measure as so and make sure that the ID and Price field are written like in your app; qlik is case sensitive :
COUNT({<ID={"=sum(Prices)>150"}>}ID)

[marcus_sommer]

Although I'm not very experienced with other programming tools I'm quite sure that Qlik isn't more difficult and complicated as SQL, Python and Co. - rather the opposite.

But it depends mostly on the used datamodel whereby the recommend approach is to develop it in the direction of a star-scheme. Of course there are other schemes possible, too but usually they are less performant and more complicated. Especially if you tries to transfer your SQL and Python experiences 1:1 to Qlik it could become quite hard. Easier is to start with the beginning, maybe from here:

Get started with developing qlik datamodels - Qlik Community - 1485839

 - Marcus