InfoPath Dev

Hi all,

I am working with a form that sends emails depending on the status of the form workflow process (request approved, rejected, under review, etc.)  When trying to add a lookup in the body of an email with the Current Item as the source, some fields are duplicated in the Field drop-down list.  For example, one of the fields on the InfoPath form is a text box for comments explaining why a request was denied.  This appears multiple times in the lookup and the number of times it appears increases as I test the form. 

I have deleted any old workflows in the workflow settings of the document library containing the form but nothing changes.  Any ideas?

 Thanks

Check your library settings.  Are you seeing this column more than once?

Hi Clayton!

Yes, the comments fields that appear numerous times in the library settings/columns section.  Also, the Used in field is blank for these except for one.

Like so:

Thanks

Something is creating those and duplicating them.  Obviously, you already know that, but I've never seen that happen before.  Workflows don't create columns, but publishing the form improperly can.

How do I clean the duplicates out?

Have to find out how they are getting there.  I'd start by going into the form template and clicking on Tools > Form Options > Property Promotion and see if you see dupes there.  If not, go through the publishing wizard until you get to the step that promotes fields and see if there are dupes there.  If you see no dupes, then I'd suggest creating a new form library and publishing this template there to see if it starts clean.  If so, then see if you can figure out exactly when and why the dupes begin occurring, if they do actually occur again.  From there, we can troubleshoot more, but based off current info, I can't think of much.

Thanks again, Clayton.

 I recreated the document library and the duplicates went away.  After repeated testing and workflows stopping due to errors, they started to appear again.  Possibly this is an artifact from the processing being interrupted. 

Moving on to the next issue.  I really wish SP had some more informative error messages; I guess that's because I'm used to VS and .Net.

David