InfoPath form fields when promoted as columns in a SharePoint list do not show up as fields in Nintex workflow options, just as normal SharePoint list fields would do. Why?

[nabil]

I have created an InfoPath form and promoted some of its fields as columns in a SharePoint form library. They appear as columns fine but when I am trying to create a Nintex workflow based on the values of those columns, I cant do it. I do not see those columns in the Nintex Workflow control options. Only the standard SharePoint columns are showing up, not the promoted ones from InfoPath.

[#2]

Are you looking in Items Properties?

[nabil]

    I am using the 'Set field value' action and the list of fields only shows the 3 standard SharePoint fields (as shown above) and not the fields I have promoted from the InfoPath form.
 
 
 
 
 
 
 
 
 
 
 

[burkslm]

The 'Set Variable' action is retrieving the workflow variables not the SharePoint columns. So you can create a workflow variable called Test. In the Set Variable action, for Set click on the dropdown and Test should appear. Select that. By 'Equals', select 'List Lookup'. Then select the SharePoint field by the field value. That InfoPath field should appear with the other columns.

[ohrenstoepsel]

If you want to show up the fields you promoted from Infopath in Nintex Workflow you need to set the checkbox to true when promoting the fields: "Allow users to edit data in this field by using a datasheet or...".

Cheers

[#6]

I enabled this checkbox, and the fields are still not editable via Nintex or datasheet.  Any ideas?

[#7]

I too am running into this problem. Was anyone able to fix this?

[burkslm]

I hate to say this....but first you should try and steer away from InfoPath. Microsoft is going to stop supporting it and InfoPath has so many issues. With that said, you are more successful when using InfoPath to use them with SharePoint lists. Here are recommendations when to use a list or library. http://blogs.msdn.com/b/infopath/archive/2010/04/22/comparing-list-and-form-library-forms.aspx.

[#9]

No hate received We are trying to move people to Nintex Forms; however, we have plenty of legacy forms built over the years that will take time to get t00. Until then we still need to support many legacy InfoPath forms. So this still requires that people like Nabil and I asking these questions.

[burkslm]

Oh ok......I don't understand where the columns don't appear in the workflow.