nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

calling one DCT from other DCT

annu1

Hi,

Is it possible to call one DCT from another DCT.

Actully we have a one DCT with some global fields which should be the part of other DCT.we dont want to re writte the same in others DCT.

Is there any way except of creating one global xml and substitute the same in all the DCT.

Thanks
Anu

Find more posts tagged with

Comments

nipper

read about inlines. Do some searching. This is very common.

annu1

I am not getting u'r point .could u pls elaborate more might be we both are not at the same point.

I have one Datacpture.cfg file with all the validation and fields and I want to use the same datacpture file inside other datacapture file.is it possible,pls give examaple how i can call in inline(is it same way as we call the ipl file with inline command)

Thanks

nipper

This is trivial.

Write a perl script that reads another file (be it a XML fragment, another DCT,etc) wrap in the correct tags and call that script with an inline call.

annu1

Thanks for reply.

Is there any other way because right now we have implemented the same we dont want to writte the ipl file and not explicitly wrap in the dcr field.

Thanks
Anu

vpatel

Create other "sub-dcrs" and just use browse button to reference those "sub-dcrs"???? Am I missing something?

nipper

Create other "sub-dcrs" and just use browse button to reference those "sub-dcrs"???? Am I missing something?

He said DCT not DCR. He wants (I think) to have a generic block included in other DCTs. Quite easy to do, if one could read.

Rob76

Yeah, use the inline discussed above. You can then create the XML on the fly using Perl. You'll be able to reuse these "components/objects" across many different DCTs.

Adam Stoller

Thanks for reply.

Is there any other way because right now we have implemented the same we dont want to writte the ipl file and not explicitly wrap in the dcr field.

Thanks
Anu

You asked how to do it - Nipper told you how to do it - though he left off the part about: if the included DCT code has an inline directive within it - you'll have to do your own inline processing because FormsPublisher does not handle nested inlines.

You now say you don't want to write a perl script - well, I suppose you could write the inline in some other language (Java, shell, vbscript, etc.) - but frankly I think Perl is far easier than any of those for what you want to accomplish.

So, you may not want to write a Perl script for this - but if you want the functionality perhaps you'll have to do something you don't want - that's life.

annu1

Could you please elaborate more how i can handle the tested inline,it would be a great help.

I have tried with nested and its works but i want the inline.

Thanks
Anu

annu1

Thanks, I got the answer.

jack846

Hi Annu,

Please tell how to call another DCT from DCT. without using perl script.

Test.zip

sheikh1

Hi Annu,

Please tell how to call another DCT from DCT. without using perl script.

It is already mentioned clearly by Nipper and Ghoti - It is as simple by calling inline tag. If you are looking for a nested form with in a form as popup or something else then it's not supported by form api.

[php]
Robot Tag

[/php]

Migrateduser

Ideally, we should avoid having inlines within included DCT chunks. It entails an overhead on the developers to handle that logic by themselves. The included chunk should ideally be simple datacapture tags.

ISCBorisB

Ideally, we should avoid having inlines within included DCT chunks. It entails an overhead on the developers to handle that logic by themselves. The included chunk should ideally be simple datacapture tags.

Removed useless pontification - looks like I misunderstood post's premise to avoid nested inlines, not the root one

Adam Stoller

Boris - I think, perhaps, you misunderstood - that the intention was, I believe, to avoid having inline directives within inlined-code -- not to avoid using inlines (1st-level) -- and that, primarily because OOTB it won't work.

sheikh1

I would strongly disagree. Inline is a good mechanism to create shared "chunks" (as you called them)
of Projects' DCTs thus seriously reducing coding/maintenance efforts. Inlines provide just about the only supported
mechanism to make DCTs somewhat dynamic. Inlines allow you to limit Content Contributors access to templates
and so on, ad infinitum. Within limitation that you've proposed inlines would be all but useless, you might as well
use these "simple datacapture Tags" instead.

I guess there is some confusion here, I tried to update the post but Ghoti has already mentioned it.

ISCBorisB

Boris - I think, perhaps, you misunderstood...

Probably - thanks

nipper

Ideally, we should avoid having inlines within included DCT chunks. It entails an overhead on the developers to handle that logic by themselves. The included chunk should ideally be simple datacapture tags.

What you do it create perl modules that can be shared. I do this all the time, a single inline, and a bunch of modules that are common throught the company/project/etc