Re: Unresponsive control(s) when missing elements

Patrick Halstead — Fri, 30 Sep 2005 02:10:08 GMT

Hi Mark,
Adding fields should result in automatic schema upgrade. It may be that the new form's schema is subtly different causing the problem. To find out, look at your xsd file (XML Schema Definition). Open the form in the InfoPath Designer, extract form files from the file menu and open the schema.xsd file in notepad. Look at the schema specifically the toggleimagebox and toggleimage. My guess is that these don't have minOccurs="0" attribute on them. If so, try manually adding the attribute and value to make the fields optional. Then, right click on the manifest.xsf file and republish and try to open the old doc. Should work.

You can also use OnVersionUpgrade to add values when upgrading old forms.

Patrick Halstead [InfoPath MVP]
InfoPathDev

Unresponsive control(s) when missing elements

marked23 — Thu, 29 Sep 2005 00:50:05 GMT


Old Doc:
<togglebox>
	<togglelink>Test A</togglelink>
	<togglelinkbox>Test B</togglelinkbox>
</togglebox>

New Doc:
<togglebox paragraph="false">
	<togglelink>Test A</togglelink>
	<togglelinkbox>Test B</togglelinkbox>
	<toggleimagebox>Test C</toggleimagebox>
	<toggleimage>images/TestD.gif</toggleimage>
</togglebox>

I'm using a template to edit an XML doc... two snippets from different docs are seen above.

The "new doc" reflects the complete output that the latest template creates.

If I load the old doc with the new template, the controls tied to the missing elements don't work. They turn grey when I select them and are unresponsive to input.

I want InfoPath to ignore the fact that the old doc is missing a couple elements. OR, I want it to insert the missing elements as required. Is there some way to work around this?

It's fine that InfoPath is trying to tell me that something is missing, but it seems it offers no opportunity to correct the problem.

-Mark

General

Re: Unresponsive control(s) when missing elements

Unresponsive control(s) when missing elements