Hi,
I am using a daily sales report and bursting it to users. I have a slicer to filter on the previous day.
#'[DailySales].[Day].[Day].[Day1]->:[PC].[@MEMBER].[' +timestampMask( _add_days ( $current_timestamp , -1 ) , 'dd' ) + ']' #
Say today is 13 the report will run for 12 . Say suppose there was an issue or delay and there is no data for 12 , then what would happen?
Will the burst still happen ?
Thanks,
Nithya
Quote from: nithya1224 on 13 Jan 2016 04:04:34 PM
Hi,
I am using a daily sales report and bursting it to users. I have a slicer to filter on the previous day.
#'[DailySales].[Day].[Day].[Day1]->:[PC].[@MEMBER].[' +timestampMask( _add_days ( $current_timestamp , -1 ) , 'dd' ) + ']' #
Say today is 13 the report will run for 12 . Say suppose there was an issue or delay and there is no data for 12 , then what would happen?
Will the burst still happen ?
Thanks,
Nithya
Yes it will still happen. Slicer filters affect the context of the measure values, but do not affect the member sets used in your rows and columns. I assume you have defined your burst groups based on member sets or levels? In this case the burst will happen and deliver zero values in each burst output.
MF.
One way around that would be to put your burst report inside an event that runs if there have been sales in the previous day.
Is there any documentation on event.
MFGF,
Say yesterday was 13 and there is no data for sales on 13 , there will not be a member called 13.
So slicer should throw an error right?
Burst is done only on the region .
Products
Region Sales
Slicer is time period that is day
Thnaks,
Manny
I imagine there is some documentation on events - a very quick google search has just turned up a useful IBM guide.
Quote from: nithya1224 on 14 Jan 2016 07:58:05 AM
Say yesterday was 13 and there is no data for sales on 13 , there will not be a member called 13.
So slicer should throw an error right?
Wouldn't that be fairly easy to test? Can you create a slicer to reference a member that doesn't exist and see what happens?
Yes I am doing that now !! will keep posted the result
So I tested the report and if there is an error in the scheduled report, the report will not be bursted. The Error will be shown in the run history .
Thanks,
Nithya