topic Re: Re: Re: Pivot-table layout and data-model problem in QlikView

Pivot-table layout and data-model problem

andy — Wed, 10 Sep 2014 19:50:55 GMT

Hi folks,

I want to create something looking like this in Qlikview 11

The rule is that if there is a forecast-value that one shall be presented otherwise the result.

I have come somewhat near the layout above by taking sum(Result+Forecast) and also the budget for every month and then letting the built-in Total replace the 'Full Year'-columns.

Findings:

-The problem with sum(Result+Forecast) comes when there is both a result and a forecast for a month then we get into problem with almost double the true values.

-The problem with if(sum(Forecast)>0,sum(Forecast),sum(Result)) comes when looking at the total which will only contain the forecasts...

- A column cannot be hidden in a Pivot-table.

- Set-analysis cannot be used since it depends on a dimension and is only evaluated once per object.

I've created a small qvw example which is attached.

Any hints are highly appreciated

brgds

Andy

Re: Pivot-table layout and data-model problem

Wed, 10 Sep 2014 21:00:12 GMT

Hi Andreas,

Can not open your personal edition document.

How about using this expression

=SUM( If (Forecast >0, Forecast, Result))

The above expression evaluates the condition for each record and then sum up the output.

Regards,

Kalpesh

Re: Re: Pivot-table layout and data-model problem

andy — Thu, 11 Sep 2014 05:34:53 GMT

Hi,

Strange with the file, if my Qlikview lost the license and started in Personal Edition that should not stop you from opening the document. If you have a license you can open any file. Anyway I have re-attached the qvw now stored within a licensed Qlikview,

Regarding you hint, since the data for result, budget and forecast are concatenated the values do not stay on the same rows so that if-condition will result in the same result as sum(Result) + sum(ForecastResult)

Thanks anyway!

/Andreas

Re: Pivot-table layout and data-model problem

jonathandienst — Thu, 11 Sep 2014 05:56:21 GMT

How about:

Sum(Aggr(If(Sum(ForecastResult)<>0, Sum(ForecastResult), Sum(Result)), Year, Category, Costcenter, Month))

HTH

Jonathan

Re: Re: Re: Pivot-table layout and data-model problem

Thu, 11 Sep 2014 09:17:18 GMT

Hello,

In expression if(sum(ForecastResult)>0, sum(ForecastResult),sum(Result)), the values returned are not as the same as sum(Result) + sum(ForecastResult), becuase the dimensions it is based on. That yields the same result as you showed as desired result in your attached qvw file. (I made a small change in the attachment to show the diff between expressions).

In case you do not want the result as if(sum(ForecastResult)>0, sum(ForecastResult),sum(Result)), could you please specify what are the dimension conditions?

PFA.

Thanks!

Re: Re: Re: Pivot-table layout and data-model problem

andy — Fri, 12 Sep 2014 06:46:33 GMT

Hi,

As mentioned in the first post

-"-The problem with if(sum(Forecast)>0,sum(Forecast),sum(Result)) comes when looking at the total which will only contain the forecasts..."

The total column only sum the Forecast-values, the other columns are as wanted.

/Andreas

Re: Re: Re: Pivot-table layout and data-model problem

andy — Fri, 12 Sep 2014 07:13:03 GMT

Hi,

This solves the problem in the example-file, thanks!

(Tried it before but forgot a dimension in it)

In the real application there there are more categories than sales and cost and some of them are not included in the forecast, then this solution will get the result for these which is wrong.

If I modify the example and remove the forecast for Category=Sales then in September (there is a forecast as well as a result) the figures for Cost will come from the forecast (Correct) but for the Sales it will be the Result-figures which is incorrect since I would like that to be 0 or null();

Maybe the best solution is to add a forecast of 0 and in the IF-condition look for a _ForecastFlag instead?

/Andreas

Re: Re: Pivot-table layout and data-model problem

andy — Fri, 12 Sep 2014 08:52:16 GMT

Hi again,

I added a new table in the script holding a flag F or P for every month and forecast-label and then look at that flag in the The sum(Aggr expression posted by Jonathan. This should work for all the scenarios I can think of at the moment.

I attach the solution

Thanks for the help!

/Andreas