InfoPath Dev

We actually do this a lot - we generally call them "config" forms. But we don't start with XML or an XSD - we just create a new blank form. Then the schema is editable from within the template, and we use the saved XML as a data source for other forms. Set the defaults in the form template....

The ones in the original fields don't blank out. Just any fields added on to the underlying schema.    Naw you have the idea of it.  This was just part of the requirements from my company. It definitely would take a lot less time to just open the XML file in UltraEdit and make the changes there. I may have to talk to them ...

Thanks Hilary I tried your code, and created a textbox named "UserID" in the record template, but there is an error said "Object reference not set to an instance of an object" do you have any idea why Thanks

I'm not sure why the defaults in the "original" fields get blanked out - that sounds kind of bug-ish, doesn't it? I'll try to remember to give this a spin later, and see what happens in my environment. That being said - it may just be easier to edit your XML file in a text editor - Notepad 2 has syntax highlighting, or if ...

I'm basically using this form to create an xml doc that I will use to update the secondary data source of another form.

No the fields are not locked.  I just create a form using an XML, not a schema. It throws in default values for every field when I create the form. When I update it, it doesn't provide default values for all of the new fields.  If that makes sense lol.

Your new XML has values in the fields for the defaults? Your form was originally based off an existing XML or schema, so is locked in the data source task pane?

I want to update my main data source (an .xml doc) and keep all the default values set in the fields in the .xml doc.  Even if I initially said yes to "using the existing data as default values", when I try to update it will not update any new values. Any updated info just becomes blank.  Is there anyway around ...

Looping in Patrick's comments...  Yes, qRules will work in the browser provided you enable the sandbox via central admin or publish as an admin deployed form template.   It looks like the issue from your form is related to the submit data connection to a Web Service. You may need to “Convert”the ...

Hey, first off, great job figuring this out - but also, thanks so much for posting your solution to help others!