GP Rolling Column
You could use the taGetSopNumber econnect stored procedure. I add this to a my own stored procedure and table before sending to the SOP Transaction map to get all the pre-tasks ready.
DECLARE @I_tSOPTYPE tinyint
DECLARE @I_cDOCID char(15)
DECLARE @O_vSopNumber varchar(21)
–DECLARE @O_iErrorState int
SET @I_tSOPTYPE = 3
SET @I_cDOCID = 'based on some sort of query.
I'm trying to add taGetSopNumber as a new node under the Node Maintenance and I'm receiving and error 'The node does not exist'. Is there a reason I cannot add this node?
Mick, where do I use the code you supplied? Would I use this outside Smartconnect when I prepare my source data or as a task in the map? If so, would it be a task before the map or the document?
So you could have a field that has STDINV, STORD, etc and then pick that field in the rolling column setup to use the source data to grab the right number rather than coding it all.
I am not sure if that is out yet, but that might be something I end up doing a Tech Tuesday article on if you follow our blog where I'll go through an example of one.
If you would like to submit an answer or comment, please sign in to the eOne portal.