Based on the design, the datalink could be error handling but since the document status is not being used to stop the workflow if no result comes back.
I think there are a few ways you can add clarity to the workflow design.
Always use a datalink @@Exception Document Status with an Is task.
Use Is task <Input: Document Status> <Output: _*Exception>
Add an Exception task <*Input: _Exception>
Add a branch to workflow so that the user can review the Document Status and validate whether the Inputs are empty or the datalink is non-functional.
I would also test the Datalink on its own to validate that the datalink is working.
Yes that would separate the datalink from the Field Group handling. I think that may be part of the issue. There are possibly other problems in here. I would suggest go through the workflow and validate each action, possibly turn off actions and tasks as necessary, but I think first checking your datalink results would help know if the datalink is functional.
Which “Datalink” action is currently active? There seems to be screenshots of the same “Datalink” action using different tasks and/or disabled.
The error in general typically means that the value it is trying to use as an input isn’t found. Without seeing the exact tasks, actions, steps and datalink itself there are a lot of unknowns. Based off what I can tell, $Field.LotNum isn’t available for the “DataLink Field Group” task that is designed to use the LotLookup datalink to populate the ECMImport field group. Without sharing the URL or any other identifiable details, are you able to provide screenshots of the Content Fields and the datalink being used? The latter can be found in the Admin > DataLink panel under LotLookup.
Thank you all We’ve fixed the issue with the assistance of Epicor Support. Found out that the issue was related in Integration>Datalink and Integration>Integrations Authentication. The user account password was change on Kinetic but failed to change it also on the ECM.
