Qdabra Tools

Re: Modify InfoPath PI

Marzipan — Tue, 10 Jan 2012 21:20:25 GMT

I'd rather have the option of giving it the same number and therefore avoid this senario. I think this should be an optional feature of the tool.

Re: Modify InfoPath PI

Jimmy — Tue, 10 Jan 2012 21:15:30 GMT

I'd suggest increasing the template version number so that it's higher than the version of the documents being migrated to it.

Re: Modify InfoPath PI

Marzipan — Tue, 10 Jan 2012 21:04:49 GMT

To avoid this kind of warning.

Re: Modify InfoPath PI

Marzipan — Tue, 10 Jan 2012 16:03:36 GMT

I am using Qdabra's tool called "Modify InfoPath PI", not my own form.

Re: Modify InfoPath PI

Jimmy — Tue, 10 Jan 2012 16:02:58 GMT

Hello,

Typically there shouldn't be a need to modify the solutionVersion and there are good reasons not to change it. Having the XML files contain an older solutionVersion than the template they are being migrated to allows for automatic upgrades to take place. Do you have a specific need to modify the solutionVersion in your documents?

Re: Modify InfoPath PI

Hilary Stoupa — Tue, 10 Jan 2012 16:01:31 GMT

Looking at the code for the command, it appears that the new PI is entirely in the hands of the designer - that is, if you are talking about the InsertPi command.

The /data parameter is the data content of the PI you are inserting - you can include solutionVersion there.

What is your current command syntax?

Modify InfoPath PI

Marzipan — Tue, 10 Jan 2012 15:51:40 GMT

Shouldn't the "solutionVersion" in addition to the "href" also be replaced?