Newbie Questions

Re: Schema updated but form not able to edit

Hilary Stoupa — Mon, 04 Feb 2013 16:09:40 GMT

You could also try manually updating the cached form template. Open InfoPath Filler and under New, you should see Recently Used Forms. Find your form. Right click and select Get update of this form.

Re: Schema updated but form not able to edit

ErnestoM — Mon, 04 Feb 2013 12:46:25 GMT

Hm, strange, that yellow bar should be coming up. I've seen it take up to 30 seconds to come up sometimes.

I think the expected behavior is that the existing XMLs will be opened with the latest version of the form template (XSN). Since that's not happening, I'm afraid it would take some troubleshooting to dig deeper: try different machines, test on a different form/form library, try clearing out the InfoPath cache...

Sorry, can't think of anything else at the time!

Re: Schema updated but form not able to edit

drfunk — Fri, 01 Feb 2013 19:18:47 GMT

No, I never see the prompt anywhere.

Re: Schema updated but form not able to edit

ErnestoM — Fri, 01 Feb 2013 16:50:08 GMT

After you open an existing form, does InfoPath prompt you to upgrade the template? This shows up as a yellow bar at the top.

Re: Schema updated but form not able to edit

drfunk — Fri, 01 Feb 2013 15:26:05 GMT

Thanks for your help.

The current settings are:

Version number; 1.0.0.11

Update template: Automatically update the template (recommended)

Update existing forms: Automatically upgrade existing forms (I changed it from Do nothing)

This did not make a difference, I still can't enter any values on the file that I had created earlier.

Any ideas?

Re: Schema updated but form not able to edit

ErnestoM — Fri, 01 Feb 2013 12:35:54 GMT

Hi,

How have you set up your versioning settings? You can check in File > Advanced Options.

It seems like the form is not upgrading, which would explain the inactive field.

Schema updated but form not able to edit

drfunk — Fri, 01 Feb 2013 02:20:16 GMT

Hello all, Let me briefly describe the process I'm following and the goal we want to achieve so there is a clear picture of the issue. We are using InfoPath 2010.

There is a schema file that we use to create a form. The users are entering data on this form and saving the file as xml for future processing. Now, there are changes to be expected to the schema, like adding new attributes that we should handle with this form. What we are doing:

- Creating a new form (data_form.xsn) based on the schema (source.xsd)

- Deliver the form to the user

- User fills the form and saves the file as xml (file_filled.xml)

Now, the file (source.xsd) has changed, a new attribute is present:

- Open the form (data_form.xsn) on design mode

- Select refresh fields

- Choosing the schema file that has the updates

- Remove old controls and reinsert the controls for the new schema, so the new attribute gets a field.

- Saving. When the user opens the form after the update, the new field is visible, but it is read only. I've checked the field on the designer and it is not marked as read only. Why would this be happening to the end user? Or am I expecting something from InfoPath that really can't support? I was under the impression that if you change the original form, the files created would be updated, saving time to the user by not re-doing the xml files all over. I know there might data loss if the attributes are removed from new schemas, but that's ok. Thank you all, looking forward for your feedback and comments.