# Service Connect - Sub workflow activity in Doc Tracking missing **Category:** [Epicor ERP 10](https://www.epiusers.help/c/e10/5) **Created:** 2017-02-14 16:02 UTC **Views:** 4751 **Replies:** 30 **URL:** https://www.epiusers.help/t/service-connect-sub-workflow-activity-in-doc-tracking-missing/37278 --- ## Post #1 by @BBussey When having nested sub-workflows, shouldn't the sub workflow activity appear in the document tracking logs? I'm getting the activity of the parent workflow, which shows as completed, but the sub-workflow activity is not in the log. It shows one line for the sub-workflow in the tree-view, but no [+] to expand. I know I have an issue in the sub-workflow, but I have no way of debugging it without the logs. --- ## Post #2 by @carlosqt [quote="BBussey, post:1, topic:37278"] I'm getting the activity of the parent workflow, which shows as completed, but the sub-workflow activity is not in the log. It shows one line for the sub-workflow in the tree-view, but no [+] to expand. I know I have an issue in the sub-workflow, but I have no way of debugging it without the logs. [/quote] Hi Brian, You need to make sure your sub-workflow has Document Tracking set to Required. See screenshot below:

Let us know if that solves it. Carlos Quintanilla PSE --- ## Post #3 by @bw2868bond Whenever I have had issues like that, there has been a schema mismatch between the incoming data and what the workflow expected --- ## Post #4 by @BBussey I checked that already, and regenerated a new sub-workflow schema just to be certain. --- ## Post #5 by @BBussey Carlos, Just made that change and tested, still no additional data in the log. --- ## Post #6 by @SimsTrak You may want to attach screen shots of your subworkflow, it's hard to debug blind. Kevin --- ## Post #7 by @BBussey

The data are being carried through to the end, as this is the trace of the finish object of the parent workflow:

--- ## Post #8 by @BBussey

--- ## Post #9 by @Graeme_Fraser Hi Double check the x path in cycling. Recreate the subworkflow schema and select it again in the subworkflow flow. Check the logs of the main work flow to make sure there is data in the xml when the subworkflow is called. Graeme --- ## Post #10 by @BBussey Verified that the XPath was correct, re-selected and re-generated the sub-workflow schema.

Re-selected the sub-workflow in the sub-schema, still no success.

Definitely data passing through to the sub-workflow object, as shown in this trace detail of the object.

--- ## Post #11 by @bw2868bond Do you use sales territories / salesmen --- ## Post #12 by @BBussey The only thing that I am trying to do at this point is read in the data and grab the order number (if it exists) using the customer ID and customer P/O number, to verify that the workflow logic is sound. --- ## Post #13 by @bw2868bond You can try doing the lookup using the BL tester – login as the same user id the Service Connect workflow is using. --- ## Post #14 by @BBussey It is currently using the manager account, and the workflow and sub-workflow are using the same .NET references. I would think that any errors encountered still should be reported to the Document Tracking log, no? --- ## Post #15 by @bw2868bond Don’t know – just tossing out ideas --- ## Post #16 by @SimsTrak Everything looked good to me. I'd try adding another subworkflow in from scratch, see if it executes that one. It wouldn't be the first time I'd had to rebuild something that seemingly was done correctly the first time, and the "rebuilt" one works. Kevin --- ## Post #17 by @BBussey I will give it a shot. --- ## Post #18 by @Jaicker_Avila Here the problem, change de Multiplicity value to "Multiple"

Saludos \ Regards, Jaicker Avila *EPICOR *Software Consultant Tlf.: +584142226119 --- ## Post #19 by @BBussey Changed the multiplicity on the sub-workflow object in the main workflow, still no execution of the sub-workflow.

--- ## Post #20 by @BBussey I wrote a second real simple sub-workflow that just updates an inherited process variable called "audit trail", and that's not executing either. So the issue must be in the main workflow and one of the settings there.

--- ## Post #21 by @Noffie Bryan, have you tried taking a look at the "related event" tab within the trace details right around that sub-workflow to see if there are any good error messages there?

--- ## Post #22 by @BBussey Adam, it appears to be a clean execution.

All greens for all eight stages. --- ## Post #23 by @Jaicker_Avila You need change Root element too, to value "Row" '

Saludos \ Regards, Jaicker Avila *EPICOR *Software Consultant Tlf.: +584142226119 --- ## Post #24 by @Jaicker_Avila

Saludos \ Regards, Jaicker Avila *EPICOR *Software Consultant Tlf.: +584142226119 --- ## Post #25 by @BBussey I can't change the root element, as "table" is the only option in the pulldown and typing in "row" is not an option apparently. --- ## Post #26 by @Jaicker_Avila Change Imput Subworkflow Schema using SalesOrders_Subwf_row.xsd and later change Root Element to value "Row" and redefine Xpath

--- ## Post #27 by @BBussey I HAVE THE SOLUTION! :grinning: Just finished a WebEx session with Jatin Purshotam from Epicor Support, and he knew exactly where to check for and fix the problem, which I will document here for others who may encounter the same issue. The workflows turned out to be correct. The issue was with the Input Channel namespace. At some point, I changed input channels after already generating the schemas off the Excel workbook, so the namespace of the input channel and schema no longer matched. Also learned how to find these "hidden" errors: In the Activity Progress, double-click on the execution point in question. Also note the input channel name at the top of the tree.

Select the Processing Info tab and click the Validate button. The information appears in the textbox below. The Trace document namespace refers to the input channel, while the schema namespace is specified on the right. If they don't match, the sub-workflow won't execute (even though the parent workflow does). Highlight the schema namespace and copy it.

Open the Input Channel, click on the Configure button, select the Communicator properties tab, click on the ConversionCfg Value cell in the grid.

Click the Default button and the Text tab. Paste the namespace from the schema in the DefaultNamespace tags and remove the comment references.

Click the Validate button to insure the configuration is correct, Click OK.

Click OK to close the Configuration window and click OK again to save the changes to the Channel Configuration, and OK to save the Channel Properties.

The sub-workflow will now execute as intended.

The alternate solutions are: to change the namespace in the schema to match the input channel, which generally is how Epicor intended things to be; or to custom assign namespace designations to both the input channel and the related schemas. But either way, the issue was that the namespace was not consistent between the input channel and the schemas. Now I can move forward with various workflows, and know that I did have them designed correctly. Thanks to everyone for all the samples workflows, suggestions, and advice, it is greatly appreciated. --- ## Post #28 by @Noffie Cool - you know, I think we ran into that very thing, although we didn't have such a helpful way of determining the issue so thanks for that. Service Connect has a lot of steps to remember it seems. --- ## Post #29 by @Jaicker_Avila Excelent! Thanks for sharing the solution --- ## Post #30 by @BBussey One other thing to mention, which I ran into on my next workflow. If the Namespace changes, don't forget to re-map the XPath in the sub-workflow properties. The error does show up in the Activity Trace, but it isn't as obvious. The message is that the row is absent, not that the schemas don't match or can't be found.

--- ## Post #31 by @nneilitz Brian. You rock. 5 years later but thanks to you documenting this, I can stop my banging my head against the wall. Thx Nathan --- **Canonical:** https://www.epiusers.help/t/service-connect-sub-workflow-activity-in-doc-tracking-missing/37278 **Original content:** https://www.epiusers.help/t/service-connect-sub-workflow-activity-in-doc-tracking-missing/37278