Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


thomas
2015-09-03T09:08:48Z
Hi

It seems to me that output parameters from procedures stopped working in 7.7.5. Example:

CREATE PROCEDURE p_test (
@num1 INT
,@num2 INT OUTPUT
)
AS
BEGIN
SET NOCOUNT ON;
SET @num2 = 1 + @num1;
END;

Call this procedure in a task, and in a later task try to access the output value:

{TASK(f54cdfe9-43ca-4898-9d6d-d310a4de3957,Result.Parameter.Value,num2)}

This worked in 7.7.4, but stopped working in 7.7.5, unless I am missing something.


Thomas
Sponsor
Forum information
Support
2015-09-03T09:43:32Z
Quick question: Is f54cdfe9-43ca-4898-9d6d-d310a4de3957 the previous Task and if so, does replacing it with PrevTask work?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
thomas
2015-09-03T09:48:34Z
Hi

It was the previous task, and replacing it with {TASK(PrevTask,Result.Parameter.Value,num2)}, did not make any difference.


Thomas
thomas
2015-09-03T10:06:28Z
I just noticed a (probably) related issue:

When I try to acces the number of rows from a query, it only works if it the output is from the previous task. So to test this, do the following:

1) Create a sql task that produces some rows

2) Create a random task as the next task

3)In a third task, try to access the number of rows from 1, eg {TASK(f54cdfe9-43ca-4898-9d6d-d310a4de3957,Result.NoRows)}

This fails even with a direct id. Then try to remove the second task and it works. I have to roll back to 7.7.4 so I can't test any more unfortunately.

Thomas
thomas
2015-09-03T10:16:28Z
I just rolled back to 7.7.4 and can confirm that both issues work as expected

thomas
Support
2015-09-03T13:39:58Z
Thanks for the report, this has now been fixed here:

http://www.visualcron.co....aspx?g=posts&t=5159 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top