saving a DCR programatically using perl/CLT

Is there a way to save a DCR without ever opening the DCR? I was looking for a CLT to do this but could not find one. It may look like a strange requirement, but we are saving an XML as a DCR, but the XML has lot of empty elements. I find that opening the DCR and saving it gets rid of all the empty elements and could be a much simpler way of doing it than parsing empty elements and deleting them. Any perl modules that can help? I do not want to tell user to open and save this, as the user does not need to open the DCR at all, but just needs to deploy the content.

TIA

Find more posts tagged with

Comments

Migrateduser

I see where you're coming from but I don't believe that there are any CLT's to do this, as you have discovered. What I would do is save a DCR of this type and look at the XML it spits out. Then, use that XML as a type of template from which you can populate DCR fields, as necessary, but doing so programmatically. Save the XML file and once saved, set appropriate extended attributes.

That's really all. The only two things that make up a DCR are the appropriate XML and extended attributes.

Dave

suj

Thanks for the reply, Dave.

Actually, this is some thing that i'm doing now. Based on the kind of XML the DCR generates, I have designed an InfoPath form, but what it does is, even though I have put many elements as nillable (not required), it still put them as empty elements after user saves the InfoPath form. I wanted to fix this at the InfoPath level, but things are not happenning that way, so I wanted to try this at DCR level.

Migrateduser

I proudly admit that I have no expertise with InfoPath, mostly because it's a Microsoft product but don't get me started on that... other than that, you really haven't described *how* you're trying to accomplish this using DCR's, so I guess I have nothing to say.

ISCBorisB

Interesting... Post 1

...I find that opening the DCR and saving it gets rid of all the empty elements and could be a much simpler way of doing it than parsing empty elements and deleting them...

Post 2

...but what it does is, even though I have put many elements as nillable (not required), it still put them as empty elements after user saves the InfoPath form

So, which one is correct? Can not be both...

suj

I solved it at the InfoPath level. I had to empty the Template.xml of infopath to avoid the empty elements. Thanks for the inputs though!