Cognos bursting calculation uses date report saved instead of 'today'

[Anke]

Hi,

  I have been fighting with this report for several years... seriously... every time I think it is fixed, I find out months later it isn't!  We are on version 10.2.2 (moved to several months ago from 10.1.1)

This is a bursting report where it is calculating forms that are due for review in 30 days.  The issue is when I save the report, the calculation when burst is always grabbing the 'saved date' of the report.  For some reason, the report cannot get today's date.  My data item, initially used 'getdate', now current_date.  My report outputs 'todays date' to the report page and that is correct, but for some reason I cannot get the calculation to get 'today' (not 'today' as in when the report was saved).

If I run the report on-demand it works fine. 

Here is my calculation... when the report is saved, the 'current_date' is always pulling the 'save date' of the report ..which is 9/1/2017... and not 9/29/17 'today' for the calculation.

_days_between ( current_date , [Plan Review])

What am I doing wrong?

[CognosPaul]

So I understand, the report is bursted on the first, but when viewed today you want to see today's date, not the burst date?

[Anke]

Yes, the report was saved on 9/1/17.... today is 10/2.. I want 'todays getdate' to be 10/2 NOT 9/1/17.

[MFGF]

Yes, the report was saved on 9/1/17.... today is 10/2.. I want 'todays getdate' to be 10/2 NOT 9/1/17.

Hi,

Can I just get clarification here on what "the report was saved" actually means? Do you mean the date the report spec was last saved from within Report Studio, or do you mean the last time saved outputs were generated and saved by the bursting process?

MF.

[Anke]

Ok, yes, I was not clear on that.  From what I can tell, the report appears to be using the date the report is scheduled.

If I scheduled the report to run daily on 9/1/17...the report appears to be using the 9/1/17 date.  BUT ... if I were to go back into the schedule and make a change to the schedule... the 'date' is reset to today... I do not know that this 'save date' is visible anywhere.

For example... today, I went into the burst schedule and changed the burst time to run right now .... since I made a change on the schedule, when the burst run ran, it appears to be working correctly.  BUT IT ISN'T (because next time is run, it is pulling the date I made a change to the schedule as 'today's date'... it is like the report cannot go out side of itself to get the actual 'real' date.

I have been trying to fix this issue for several years... seriously.  Nothing ever fixes it. 

[MFGF]

Ok, yes, I was not clear on that.  From what I can tell, the report appears to be using the date the report is scheduled.

If I scheduled the report to run daily on 9/1/17...the report appears to be using the 9/1/17 date.  BUT ... if I were to go back into the schedule and make a change to the schedule... the 'date' is reset to today... I do not know that this 'save date' is visible anywhere.

For example... today, I went into the burst schedule and changed the burst time to run right now .... since I made a change on the schedule, when the burst run ran, it appears to be working correctly.  BUT IT ISN'T (because next time is run, it is pulling the date I made a change to the schedule as 'today's date'... it is like the report cannot go out side of itself to get the actual 'real' date.

I have been trying to fix this issue for several years... seriously.  Nothing ever fixes it.

Hi,

Sorry - this is a really basic question. Are you absolutely sure the schedule is running and generating outputs? It sounds to me like the report outputs are not getting regenerated? What happens if you change the number of saved output versions in the report properties to more than one? Do you see multiple rendered sets of burst outputs all with the same date, or just a single set?

MF.

[Anke]

I have multiple days output.... I have the schedule set to Run History Number of occurrences: 5, and Report output versions: 25.  Each time it runs there is a new date line with all of the burst outputs for the date. 

Do I have this set up correct?  When it is run, depending on who has output, not all get a burst report.... it looks ok to me, does the above look correct?