Repost: Triggered work objects - assignments not working correctly

 6 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
ThomasT
Advanced Member Send Private Message
Posts: 27
Advanced Member
I have a pflow which has a simple node to a work object (which calls a second pflow).

Within the second pflow there is a query. Query is name Query9100. Here's the query:

PROD=&FILE=REQLINE&FIELD=COMPANY;LINE-NBR;REQ-NUMBER&SELECT=COMPANY=%26REQ-NUMBER=&OUT=CSV&DELIM=~

Within the query loop there's a simple assignment node:

linenumber = Query9100_LINE_NBR

Should be simple thing, I believe.Works on all other flows I've worked on but maybe not workobjects...

Anyways when the 1st pflow runs, it calls the work object. The log file of the second work unit (the work object) has an error log. Within it, there is the error on the assignment:

ErrorLog in Process : ReqLineAction_V19 Workunit : 1044, ActivityType=ASSGN, ActivityName=Assign4680, ActivityId=ASSGN3 Date:12/07/2010 Time:13:31:26
Exception while evaluating expression: linenumber = Query9100_LINE_NBR;
ReferenceError: "Query9100_LINE_NBR" is not defined. (threadScript#1)

I have reviewed the flow, rebuilt the query and the assignment a few times, refreshed the pflow, used only point and click to define the variables including the global variable 'linenumber' ... pretty much everything. And this still does not work. It is somehow not working with this assignment of  Querry9100_LINE_NBR. (it says Query9100_LINE_NBR" is not defined)And I can't figure out why... unless there's another way to do the assignment? Or is there a patch??

Does anyone know why this would not work? Ideas?
ThomasT
Advanced Member Send Private Message
Posts: 27
Advanced Member
I might add that somehow the is not appearing in the original post above, but it is within the query.
ThomasT
Advanced Member Send Private Message
Posts: 27
Advanced Member
.. and also the COMPANY= is also not appearing in the post, but it is in the query.
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
Variables from a Query are non-persistant and some nodes clear them out (Branch, UserAction) which might include a WorkObject. I suggest you write the query values to variables (defined on the Start node) and try to use those in your WorkObject.
David Williams
ThomasT
Advanced Member Send Private Message
Posts: 27
Advanced Member
Ok tried that, 
I have a query loop which calls the workobject, but unfortunately and according to the wulog, the 2nd work object isn't called at all. Is there some other limit which says work objects can't be called or used within a query loop??
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
No. In fact Lawson has a flow (RQCreateLn) which is meant to have a WorkObject within a Query Loop.
Send me your flow and I'll take a look at it.
David Williams
Jason Beard
Veteran Member Send Private Message
Posts: 124
Veteran Member
If there was no record found in the query then you would get this error. Basically querynode_variablename does not exists unless there is at least 1 record returned in the query. Check the call that is made for Query9100 and make sure it is returning records/

Jason
Jason Beard
617-548-5568
jabeard3@gmail.com