So...... Yes. The report works perfectly until you schedule it. Then after the report runs the first time, the xml file hardcodes the date and the results for the "last seven days" will never change because the GETDATE statement is gone ie.
DATEADD(DAY, DATEDIFF(DAY, 7, GETDATE()), 0) and DATEADD(DAY, DATEDIFF(DAY, 0, GETDATE()), 0) this is what development gave me to try for the last seven days instead of the %LASTSEVENDAYS system variable. However, the result is the same
WHERE dbo.dt_wsus_computers.lastsynctime between '20141118' and '20141125 23:59:59.997' This is what the xml file looks like after the first scheduled run completes ( I got my report folders mixed up and this was wrong, fixed now)
The significance of the workaround document that Development wrote is that Pavlo?? in Development was trying to solve the hardcoding issue that the system is doing. I don't know why he thought using a report from Task History would help.
I realize that last xx days is not a filter option but if the code can be made to work for the last seven days, I can make it work for any number of days/months.
My issue is that the report will not work out of the box so we need to get that working first.
I just spoke with Phillip the Tech Support Manager and he assures me you are the man for the job.
Thank you for your help.