InfoPath Dev

Hello, I just saw the Qdabra webinar "Create Forms That Move Easily from DEV to PROD: Qdabra InfoPath Webinar" taught by Hilary Stoupa and it was great. I was using the relative UDCX references, but never thought about using a relative config.xml file. I wasn't able to attend the original session, so I hope my questions can still be answered. 1. When a form template is updated in DEV and then published in PROD, I have to remap fields. Is there a way to avoid this? 2. What's the best way to migrate SharePoint designer workflows? Thanks for your help.

Hi, I'm so glad you liked the webinar. What do you mean when you say "remap fields"? In my recent project where I used the SharePoint management shell to copy my site collection my workflow copied over as well and it just worked. It was so lovely. :)

I'm migrating the form from our DEV SharePoint server to our PROD SharePoint server. I noticed that when I publish in the past, the meta data for the fields are gone. When I look at the Field Promotion screen right before publish, it says that it will create new fields for each promoted field. So to prevent the loss of meta data, I go into each promoted field and map the InfoPath field to the SharePoint field. Hope that makes sense.

Hi, does my description sound familiar?

Sorry, I missed your follow up. Actually - yes, that is a problem and one I didn't think to talk about, I'm afraid. I don't know of a good way to prevent this - in the past, I've manually updated the GUIDs in the manifest (sounds awful but is really just a matter of getting the Prod template down and then copying the GUIDs to the dev template prior to publishing). In the project I'm referencing in the video we are using admin approved browser forms and haven't had an issue with the promoted properties because of this - if admin approving is an option it may reduce this headache for you.

That's too bad. It's a bit of a hassle, but not too much. Was just curious if there was a way to avoid it. Thanks for looking into it.