Nintex Connect

The Official Community Site for Nintex Software Products, including Nintex Workflow 2007, 2010 and 2013; Nintex Workflow for Project Server 2010; Nintex Reporting 2008 and Nintex Analytics 2010; Nintex Forms 2010; Nintex Live and Nintex SmartLibrary.
Welcome to Nintex Connect Sign in | Join | Help

nintex workflow error due to addition of unwanted zero at the end of network Id

  •  06-01-2011, 3:39 PM

    nintex workflow error due to addition of unwanted zero at the end of network Id

    Hi,

    I am facing a weird problem in nintex workflow.  Initially we are promoting infopath field on to the nintex approvals. The infopath field contains a network Id of the approver. Once the work flow is initiated the networkId in the infopath field gets identified by the approvers list of nintex and sends an approval email to the respective user.when i add the network id of the approver to the list the id looks something like this  {ItemProperty:Requester_x0020_Ntwk_x0020_ID} .

    This worked for few days and it sent approval emails to the users for few days. 

    But the problem started when i republished the infopath form to the same library with some changes on others fields (Note: I dint  altered the Network Id field). Now when the workflow is initiated it throws an error something like this

    Failed to send notification. Cannot get the full name or e-mail address of user "{ItemProperty:Requester_x0020_Ntwk_x0020_ID0}".

    The thing i observed here is it is adding an unwanted zero for the network id at the end and the workflow is throwing an error as a result.

    To avoid this i again configured the network id in the workflow list the moment i add the network id it is showing the network id to be as follows

      {ItemProperty:Requester_x0020_Ntwk_x0020_ID0}.

    Now it is appended with a zero at the end of the Id. This Id will work for few days untill i republish the form and gets changed to ItemProperty:Requester_x0020_Ntwk_x0020_ID} and the workflow is again throwing an error.

    I tried a lot to find a solution for this but couldnt get a break through. Can anyone please help me with this issue or atleast let me know where the problem is. This issue is troubling a lot.

    Thanx in advance....
View Complete Thread
Powered by Community Server, by Telligent Systems