Just wondering if anyone else has come across this.
We have a Custom SSRS Dynamic (or RDD) report that contains a single date parameter in the BAQ.
When we run the report manually it works fine - no issues.
When i schedule the report to run in the evening i am using the dynamic Date and are using the “Today” option.
When the report runs after the 1st day (the day we added the report to the schedule) i.e. day 2. The report numbers seem to be stuck using the original date.
The Epicor schedule does not appear to be using the dynamic “Today” date for the parameter.
Anyone encounter this before? I have a support ticket entered - however, right now support seems to be convinced this is a Time Zone problem
MS. @aosemwengie1: Thank you for the reply - I just tested my RDD as a direct submission to the task agent AND saved to a “Process Set”. In both cases when Check the “View Task Parameters” the date Dynamic field is NOT checked. Aaaaarg! Must be something i am doing.
What does it look like when you are actually submitting the report? This looks like its been opened from within the existing scheduled task. I mean if you put your report on the menu, and then go launch that menu item.
This is what it looks like when launched from the Memu.
It runs correctly if i select the Dynamic and Today options.
However, when i submit this to either the Task Agent or to a Process Set the report runs with whatever day the report was submitted. i.e. all of the scheduled reports will run daily but they will ALL use today 12-29-2025 as the date parameter.
But, what I found to be a satisfactory workaround is instead of having a parameter to set dynamically, just set the criteria inside the baq to be based on the Today constant. Yeah it doesn’t give you the flexibility of a parameter but if you are scheduling it then you want it to be the same every time anyway so . . .
Yes i have considered that and I may have to settle on the workaround. I would prefer Epicor Acknowledge the but so i will not have to bend over backward to create a report.
I traced out this behavior previously, and (from memory, so probably a little off…)
The issue is that for the report you are generating, you are calling /SubmitToAgent (for stock status report for example, Erp:Rpt:StockStatusReport/StockStatusReportSvcContract/SubmitToAgent), you can see the token being sent here as a supplemental field with “Token” tacked on (AsOfDate has the date value that was in the field before checking the “Dyanmic” box - AsOfDateToken captures the token):
This method calls a number of internal methods in a chain to validate that the report isn’t already running, evaluate dynamic parameters etc. You can see those BOs firing after the SubmitToAgent call in the App Server Log under EpicAdmin user.
One of those calls is to Ice.Core.GetTokenLib, which does the job of translating the “Token” parameters to real date parameters.
When the task gets saved to SysTasks table, the Token parameter is not saved, only the translated Date parameter that resulted from the call to GetTokenLib.
So, no token saved, no possibility for the functionality to work as designed/desired. Needs a retooling to save the token to SysTasks, and the token decoding logic needs to be shifted from SubmitToAgent to the BO that processes the SysTask when running the agent call.
