In the two previous blog posts, I created a workflow to migrate the data from InfoPath documents to two custom SharePoint lists.
Next, I will convert the form using the FormTrek transformation tool. You can learn more about FormTrek by clicking here.
This is the Nintex form after transforming it from InfoPath form.
I make the form height a little bigger and add a list view control. I remove the Save and Cancel buttons, Task label, and the three task fields from the main body of the form. I add the Project ID control. I replace the Description control with the one that Nintex provides in List Columns.
Note: FormTrek will update the transformation tool so that the Description control is created as a multi-line control.
The updated list view control settings are displayed below:
After saving and publishing the form, it displays the data as seen below.
The content is migrated and the main InfoPath form is transformed to a Nintex form.
There are a few tasks that could be worked on in the future:
- Move file attachments from the InfoPath documents to the custom list.
- Configure the workflow to run on all documents.
- Add a way to create the project tasks within the project form. There are a number of blog posts on this topic.
I experienced two workflow errors while developing and testing for this blog post. I decided that it might be helpful to list them below.
First, I was getting an error when running the workflow.
I had to update my Nintex Workflow Database in Nintex Workflow Management.
After the upgrade ….
Then I ended the workflow.
I click OK to terminate the workflow.
The workflow is cancelled.
Second, I was getting an error on columns requiring different type of information. I assume the error occurred in the first Create item action.
I cancelled the workflow. I changed the Project Owner and Task Owner columns in the lists to be Single line of text. Then I changed the return value of tProjectOwner and tTaskOwner in the respective Create item actions to be plain text.