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; } } }

Reading dcr values

explorer

Hi friends,

I want to fetch one dcr values and want to show in those values in other dct as drop-down box .

Please suggest how can I do it by using PERL or is there any other short cut way in teamsite ?

Find more posts tagged with

Comments

Rick Poulin

DCRs are basically just XML files. Therefore, use an inline cmd or a callserver in your other dct, and have it call a perl script which reads the appropriate DCR with one of the bundled XML modules (may I suggest XML::XPath, since you're only reading). Easy peasy, if you've ever done any perl (your question is fairly open-ended).

ISCBorisB

Hi friends,

I want to fetch one dcr values and want to show in those values in other dct as drop-down box .

Please suggest how can I do it by using PERL or is there any other short cut way in teamsite ?

In addition to callServer you can sometimes use FormAPI to get information from another DCR,
either directly or by calling "foreign" DCR's call-back functions. This thread contains some
discussion, it's a (little) hack though.

nipper

You have been given two different approaches. The inline approach will work on instantiation only, while the FormAPI/call server will work after the DCT has been loaded.

The inline is much easier to do, and if the data does not need to change once the DCT has been loaded, use the inline.

ISCBorisB

You have been given two different approaches. The inline approach will work on instantiation only, while the FormAPI/call server will work after the DCT has been loaded.

The inline is much easier to do, and if the data does not need to change once the DCT has been loaded, use the inline.

Agree. Both callServer and FormAPI approaches make sense only if you need additional user
input, DCR (rather than DCT) information or both. In any other case inline is preferable.