InfoPath Dev

 Okay, so I tried this approach: $xml = New-Object System.Xml.XmlDocument $xml.PreserveWhitespace = $false $xml.Load("C:\Users\Hilary Stoupa\Documents\~Temp\2020-09-22T09_02_19.xml") $xml.PreserveWhitespace = $true $xml.Save("C:\Users\Hilary Stoupa\Documents\~Temp\TST2020-09-22T09_02_19.xml") ...

I don't think the error stems from the address replacement. I think it has to do with something in the way the file is re-saved from PowerShell. He might want to look into Xml.PreserveWhitespace - I'm wondering about setting that to false before loading the XML and then setting to true before re-saving might help with this. I'm going ...

A template is an InfoPath form - the form itself, the XSN file that you work on in InfoPath Designer and publish. I had thought you were talking about removing the group from the schema in the XSN.

Well - that's why I was asking about whether the form is in production. You don't have to have a specific group for the section - you can bind a section to another field or group in the schema. But, in InfoPath Forms Services (browser) forms my experience has been that deleting a field or group from the template actually causes additional ...

By versioning I mean in the form template, the XSN, under form options > Versioning, is the template set to upgrade existing forms? Have you published the form again between being able to open certain forms yesterday that you can't open today?

You are opening this in the browser, right? and submitting in the browser? Your initial post makes it sound like you were using Filler for a bit - is that the case? And you said this is only happening on "older" forms? Do you have the form template published with the versioning set up upgrade existing XML? Oh - and I guess the next ...

The whitespace is in between the open / close tags for Submit. If you open the XML in a text editor, you can see a carriage return. In this screenshot, I've got it open in Notepad ++ and am showing all symbol characters. In my tests, if I removed the carriage return, the schema validation error went away.

I am able to repro the issue when I preview the XML you sent with the template you sent if I have the form set to not update the XML on open (under versioning settings). Removing the whitespace in the node fixes that.... but that doesn't explain how that is ending up with whitespace to begin with. Is this form in production yet? Or are ...

I just sent you an email via the forum - reply to it with your XML and your XSN and I'll take a peek and see if I can see the issue. :)

 You can promote your repeating fields as "merged" to display all the data in the library - that would give you a semi-colon delimited list of items. You could use Power Automate to write the items to a separate list if you are using SharePoint online - more here on that approach: https://www.youtube.com/watch?v=wJD-kKexkAM If you ...