InfoPath Dev

I had requested to modify 3 template, let say template A, B and C. I added a drop down list control for each of the template and publish to the sharepoint but there is one problem happen regarding to the old form in sharepoint.

Since template A is no problem, I don't know why when I open the old form by using template B and C then the new added drop down list (other control also the same) became disabled.

Can somebody tell me what happen and any solution for this problem? thx

Note: The problem happen only when I open the old form (form before the updated template), new form no effect.

usually this is because the field which the new dropdown was bound to does not exist in the old forms.

Check which field the drop down is bound to, where it stores its data.  Is this field in the previous forms or is it a new field?

My guess is it is new and therefore since there is no where to store the value in the old form then it disables itself.

Now I can confirmed that the drop down in the old form does not bound to the new field.

So, is it any way to make it bound to the new field?

There is a way but it requires code in the form load event which checks for the missing fields and creates the fields in old form's xml.

I am not sure how it is done but have worked with forms which had it.

Clay,

Can you show me a simple coding (or guideline) on how to check the missing field and create the field in old form's xml?

Because I'm quitea new bird in using infopath, so hope that you able to give me some advice for this infopath. Thanks a lot!

You should be able to build a form that can be dynamic. this case is where additional fields are added after the form is in production.

Unfortunately I do not have the code to do this.

If you would like to purchase a support credit you could get a developer who does to help you with this.  http://www.qdabra.com/products_all.asp?cat=12 

I just encountered the same problem.  Just found a solution too.  :)

This happens when you choose 'Do nothing' on version upgrade. To make the fields selectable/editable, republish the form with the following options. Go to Tools -> Form Options -> Versioning -> On version upgrade, choose "Automatically upgrade existing forms". Once the new version is uploaded in Central Admin, go back to your old forms, you should see your new fields as editable.

Hope this helps.

Yanling

Works Great!

It doesn't work for me.  My templates are fully trusted.  When I installed the new version, the new controls still disabled.

Has anyone else found a different solution?

Thanks

Hi,

Open “upgrade.xsl” in visual studio and search for your newly added field. If that field in not there in the upgrade.xsl then add it manually in upgrade.xsl file.  

Thanks for replying.

The newly added field is in the "upgrade.xsl".  It shows on the old form, but it's disabled.

make sure the control is itself not disabled by checking its properties....or that some condition disables it.

Make sure your newly added field should be there in the sampledata.xml and template.xml files.