Crystal Report parameter no longer accepts job variable in 7.7.8 and 8.0

example: I have a report task that uses a job variable to offset the date for all tasks in a job.
Here is a screen shot of the parameter.
This works in 7.7.7
it does not in 7.7.8 and 8.0

We do not see exactly why as we cannot see anything changed here. What if you hard code the date in a USER Variable and use it there? Just to make sure that your calculation is not wrong or that Job Variable wrong.

---

I upgraded to 8.0 from 7.7.7, it stopped working.
I downgraded to 7.7.8, still not working.
I downgraded again to 7.7.7 and it worked again.
I'm not in a position to touch every job variable on all our systems after an upgrade.
There are too many and not enough time.
Your help would be appreciated, thanks.

Is there way you can set this up to see if the upgrade breaks the job variable on your end?

Can you tell us the exact value of the Job Variable?

---

It is a number, like 1. The variable is used in the DATENOWADD to push the date up or down.

I did some ore investigating. Here is what I found..
I copied a task from a 7.7.7 server to a 8.0 server.
I ran the report and I get bad dates evaluated from the parameters, but not the export filename.
This was the case as well when I first discovered the issue.

The date is correct in the filename. I get 17 in the filename using the DATENOWADD, which is the same in the parameter.
This works in 8.0 for filename: C:\ALL-billing_report_{DATENOWADD(Days|{JOB(Active|Variable|StartDateOffset)}|dd)}.pdf

The parameter does not, so there is something wrong in the code for Crystal report parameters.
This does not work from the same task:
{DATENOWADD(Days|{JOB(Active|Variable|StartDateOffset)}|MM/dd/yyyy)}
{DATENOWADD(Days|{JOB(Active|Variable|EndDateOffset)}|MM/dd/yyyy)}
StartDateOffset = -1
EndDateOffset = 0

Here are the dates from inside the exported PDF file after running the report:
Start Date
12/30/1899
End Date
12/30/1899
Notice that the dates were not evaluated correctly or at all..
One is supposed to be one less than the other and they are equal.

I will not be able to upgrade until this issue has been resolved.

Thanks

We would like to know if this is a general problem. What if you disable that Crystal reports Task and instead create a File write Task where you write the combined values and also the Job Variables alone to a file - does that work or same error?

---

I created a file with the date values and the job variable values in it.

Here are the results:
2015-12-27
2015-12-28
-1
0

Here is the code from the write task:
{DATENOWADD(Days|{JOB(Active|Variable|StartDateOffset)}|yyyy-MM-dd)}
{DATENOWADD(Days|{JOB(Active|Variable|EndDateOffset)}|yyyy-MM-dd)}
{JOB(Active|Variable|StartDateOffset)}
{JOB(Active|Variable|EndDateOffset)}