Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello everyone,
I previously had coded into the data editor the following: and not match(KOSTL, '0017001020')
I now want to remove this, and apply it to a KPI field, where I take the sum of the total budget.
I have already tried the following: =sum({$-<KOSTL={'0017001020'}>} Budget) but this gives me a not-specified error in the code:
If at all relevant, the COSP budget is a master-element.
Thanks in advance!
It's not a field, but a Master Measure, that's why it's in purple. Nested aggregation (Sum in sum for exemple) are not allowed and then an error is triggered
So you can try:
{<KOSTL-={'0017001020'}>} [COSP Budget]
Hi,
Can you try this instead: sum({<KOSTL-={'0017001020'}>} Budget) ?
Regards
It still says error in formula 😕
COSP Budget field seems missing, that's why it's green colored. Can you check the field name ?
Weird... it even recommends it as a field to take
It's not a field, but a Master Measure, that's why it's in purple. Nested aggregation (Sum in sum for exemple) are not allowed and then an error is triggered
So you can try:
{<KOSTL-={'0017001020'}>} [COSP Budget]
Thanks for the info. It accepts it as a formula, though weirdly enough it seems to now not have filtered it out. If I take out the '-' it is also still the same value. Any idea what could cause this, or is that not possible to find out without a deeper dive into the data and data editor?
Ok, indeed you need to go deeper yes. First step is to obtains the formula behind [COSP Budget] Master Measure, because maybe some filters are already applied.
Thanks, I can't find any filters that should change it, since it itself is an addition of other master elements, none of which have filters that I believe you influence the ability to filter for this variable.
Thank you very much for your help regardless! Is it customary to accept your previous answer as a solution, since it at least got rid of the error message, or should I leave it untouched?
You're welcome, I hope you'll find out the problem.
I think you can mark it as a solution, so Qlik users with similar issue will have a solution which can apply to them.