InfoPath Dev

I've developed a master form that creates and submits multiple forms to a library using qRules.  If I run the master form as an infopath filler form, it creates and submits the forms perfectly.  But if I enable the form to be used from a web browser, when I submit the form, the href indicating where the template for each form resides is stripped out.

The form uses the InsertPI command as follows:

InsertPi /name=mso-infoPathSolution /data=name="urn:schemas-microsoft-com:office:infopath:WW208-CaregiverStrainIndex:-myXSD-2018-03-07T02-56-48" solutionVersion="1.0.0.15" productVersion="14.0.0.0" PIVersion="1.0.0.0" href="http://ww-sharepoint/ClientServices/Placement/FormTemplates/WW208-CaregiverStrainIndex.xsn" /dsname=WW208-caregiverStrainIndex

when submitted from an Infopath Filler, I see this in the created form:

<?mso-infoPathSolution name="urn:schemas-microsoft-com:office:infopath:WW208-CaregiverStrainIndex:-myXSD-2018-03-07T02-56-48" solutionVersion="1.0.0.15" productVersion="14.0.0.0" PIVersion="1.0.0.0" href="http://ww-sharepoint/ClientServices/Placement/FormTemplates/WW208-CaregiverStrainIndex.xsn"?>

But when submitted from a web browser, I see this:

<?mso-infoPathSolution name="urn:schemas-microsoft-com:office:infopath:WW208-CaregiverStrainIndex:-myXSD-2018-03-07T02-56-48" solutionVersion="1.0.0.15" productVersion="14.0.0" PIVersion="1.0.0.0" ?>

Is there something else I need to do in order to ready this form to be used in a web browser with qRules? 

Thanks

 

Oh how odd! Can you put the execution history on the form (from the qRules data source) and the command node and try your command? See if there are any clues in the errors or result node? Also, maybe try moving the href attribute between two others (just to see if that makes a difference).

 Hi Hilary, thanks for the suggestion.  When I show the results, the injection works fine from the filler, but from the browser the two injections fail, saying "The specified PI already exists".  So I guess I need to run the removePI instruction first in order to make this work.  Any idea why the web browser has the PI's but the filler doesn't?  Thanks again for your help!

No idea why the browser has the PI and the Filler doesn't! But I'd just add the remove command first, then you are covered. :-) EDITED TO ADD: wait, is there a remove pi command? I think we have to use Delete for this.... I'll go find the syntax.

I think Delete /xpath=/processing-instruction()[local-name(.) = "mso-infoPathSolution"] would do the trick.....

 Okay, I tried the RemovePI instruction, and it shows "success", but then the InsertPI still fails saying "The specified PI already exists".  So then I tried the Delete command you suggested, and that also completes successfully, but the InsertPi fails with the "already exists" error.  I'm thinking I need to somehow target the secondary data source xml?  Basically I have 14 different forms in a library, and this form is a "master" form that the user can fill in some client data and submit the 14 other forms with data prepopulated, so the actual master form doesn't get submitted, instead it submits all the secondary xml data sources...thoughts?

RemovePI is just for DBXL PI, I think. So use Delete and just add /dsname=WW208-caregiverStrainIndex to target the secondary data source.

 That did it, thanks a million Hilary!