[SererraMike]

When I save a Sales Order that is a replacement for a Return Auth, I have a custom field on the SO that links it to the RA. When I save the SO, I’d like to browse back to the RA and add the SO# in custom field I have setup over there.

My workflow is setup to run after record submit. I’m using a Go To Record action, which works correctly as I’m redirected to the expected RA. Under the “Fields” section I’m choosing the field on my RA, and setting the value with a formula of {id} as transaction or document # is not available in the “Value Field” column. When I save my SO, however, the system takes me to the RA, but the field is not populated. When I check my logs, I can see the internal ID of the SO is captured n the workflow, but it doesn’t make it to the RA. Coincidentally this is pretty much the same way I’m setting the RA field on my SO (difference is I’m creating a new SO), so I can’t see why it won’t work.

Thanks

Mike
This is a cached copy. Click here to see the original post.

[k_dunc]

Hi Mike,

I don’t think a Workflow can add such details to a column field. Instead, you’d probably need a Workflow Action Script to handle the actual line item columns.

Cheers,

Kirk.

[chanarbon]

Hi Mike,

Similar to what Kirk mentioned above, workflow, on it’s own, does not support setting values for fields that’s on the line item. For the workflow action script, you need to get load the RA record then perform the setting of line item values of the RA nlobjRecord.

[SererraMike]

Thanks guys. I’m actually trying to do this at the main line though. No line level involved. On the SO I have an RA specified in a custom list/transaction field in the header. Upon save I want to go to that RA and stamp the SO in a transparent body field in the RA.

[k_dunc]

Hi Mike,

I still don’t believe you’re going to achieve this solely through standard Workflow Actions. I think the issue essentially is that the Workflow is set to work on one given record type (your SO), and upon saving that, you want it to make changes in another record type (an RA) for a record that already exists.

Yes, from a Workflow you can, upon saving, redirect the user to a different record – you’ve achieved that successfully already. And yes, you can also create a new record (of a different record type) from a Workflow, but you cannot, in my opinion, change an existing record of a different record type without using a Workflow Action Script. In a very simple WAS you can certainly achieve what you’re after, but I don’t believe it’s possible by only using standard Workflow Actions.

[SererraMike]

Thanks Kirk,

I was doing some additional testing and I noticed if I unchecked “Store Value” the workflow actually worked, it browsed back to my RA and populated the “Replacement SO” field, of course it lost the value once I clicked save as it wasn’t set to store. Any insights as to why that would work, but the other way wouldn’t?

At this point I’ve accepted that it’s just not going to work the way I want it to, unfortunately my scripting knowledge is zip, so I’ll have to reach out to have someone write up the WAS ,but I’m curious as to what’s actually happening.

Thanks for the help,

Mike

[Author]

Posts