Hi

Using this date variable works in 8.2.5, but fails in 8.2.6



It sends an email with the subject: TranslateVariables->Unhandled error: Object reference not set to an instance of an object. on string

Edit: I just noticed that this also affected an excel task with the same translate variable error.

It seems like you are mixing paramter delimiters. You either need to use comma or pipe.

---

That's fine, but it works in 8.2.5, so there must have been a change on your side. I guess I'll have to reinstall 8.2.6 an test again.

I tested some more now, and it's not the date that fails I see now, it's the Result.NoRows that fails (not visible in the previous image as it was further to the right).
We fetch some data from the db and report the number of rows from that task.

I tested some more now, and it's not the date that fails I see now, it's the Result.NoRows that fails (not visible in the previous image as it was further to the right).
We fetch some data from the db and report the number of rows from that task.

Please paste the exact Variable that does not work here. Also the Task type.

---

It this variable that fails. I use it in the subject line of the email task. It also fails in an excel task. I don't think it's related to any task

So, just to be super clear:

1. the previous Task is a SQL Task?
2. you are using this exact Variable in the Notification or next Task: {TASK(PrevTask,Result.NoRows)}

---

Hi

This is a strange one. I didn't give you enough info I see now, sorry about that.

Task 1 is an sql query
Task 2 writes to file
Task 3 gets number of rows from 1, using then exact id like this: {TASK(9c07093a-a874-4e03-8e44-aa2f85511a9c,Result.NoRows)}

Here is the strange thing. When I create a new job on version 8.2.6, using the exact id works. I believe therefor that to replicate it you have to create the job in 8.2.5, and then upgrade to 8.2.6. That is when it fails. So it seems that there is something with the upgrade that does it. I will check more if I have time. There are no errors in the log, even with extended debugging on.

Hi

This is a strange one. I didn't give you enough info I see now, sorry about that.

Task 1 is an sql query
Task 2 writes to file
Task 3 gets number of rows from 1, using then exact id like this: {TASK(9c07093a-a874-4e03-8e44-aa2f85511a9c,Result.NoRows)}

Here is the strange thing. When I create a new job on version 8.2.6, using the exact id works. I believe therefor that to replicate it you have to create the job in 8.2.5, and then upgrade to 8.2.6. That is when it fails. So it seems that there is something with the upgrade that does it. I will check more if I have time. There are no errors in the log, even with extended debugging on.

It sounds like the Id or Task type has changed. The reason for the error is most likely that the Id is pointing to a Task that does not have this Result value (because it is really not a SQL Task).

---

How do explain that it fails when I upgrade to 8.2.6, and when I roll back to 8.2.5 it works again, without any other changes?

How do explain that it fails when I upgrade to 8.2.6, and when I roll back to 8.2.5 it works again, without any other changes?

I don't know. But the question is, if you do reselect the Variable in VC after upgrading - that it will have the same Id?

---

It's the same. Unfortunately I don't have time to test more on this due to work. We will just have to stick to 8.2.5 for a few months.