General

Re: I do not want a "my:" namespace

PaulRAnderson — Mon, 08 Apr 2013 15:31:16 GMT

Patrick,

I have no problem combining schema.dat and myschema.dat, and then removing mentions of myschema.dat to remove mentions of "my:" and to get rid of resulting duplicate definitions. I assume that's what you mean by using the scalpel.

But given that the form has the attribute to use additional namespaces, is there a way to change that or do I need to create a new form and move everything in manually? (Please tell me there's a way to change that attribute on the existing form.)

Paul

Re: I do not want a "my:" namespace

Patrick Halstead — Mon, 08 Apr 2013 05:19:57 GMT

Yes, you can do this but it's a bit complex since you have to manually update the form contents. I wouldn't bother because there are a lot of references. The simple way is when you originally created the form the dialog asked you if you wanted to include other schemas - that was the time to say yes and specify them. After creating the form is after the fact and requires laser-guided surgery. Happy to hand you a scalpel and show you how to do it, but it would probably take an hour since we'd have to verify it first before showing you.... :)

I do not want a "my:" namespace

PaulRAnderson — Wed, 03 Apr 2013 18:03:33 GMT

I do not want a "my:" namespace. I do not want the InfoPath 2010 GUI to use the "my:" namespace when adding a new field or group. I do not want both a schema.dat and myschema.dat file.

I've changed the xsd:schema statement per the topic "Prevent InfoPath From Autogenerating a Default Namespace Prefix" but after editing the schema.dat file, there's no behavior change in InfoPath and the 'xmlns:my=' statement returns in the schema.dat file and a new myschema.dat file is created.

Is there a way to never have a namespace prefix added to new fields or groups added via the GUI?

Paul