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

Does the Datacapture DTD delimiter attribute work?

Bill Klish

TeamSite 6.5 SP3
Solaris 9

We have a select item in a datacapture.cfg file and would like the multiple selections to not be separate XML value elements, but rather a comma separated list (val1,val2,val3).

The 6.5 TST manual states:

delimiter: Specifies the delimiting character used when data from all
check boxes is concatenated by the data capture subsystem when saving
an XML data record. The default delimiter is a comma (,)

I found the delimiter attribute for checkboxes and select boxes which according to the DTD works when multiple="t", which we have:
[html]

Target Page Type

[/html]

Is this not going to do what I expect? Not a big deal to do in a PT, but wanted to make sure I wasn't missing something.

Find more posts tagged with

Comments

Adam Stoller

TeamSite 6.5 SP3
Solaris 9

We have a select item in a datacapture.cfg file and would like the multiple selections to not be separate XML value elements, but rather a comma separated list (val1,val2,val3).

The 6.5 TST manual states:

delimiter: Specifies the delimiting character used when data from all
check boxes is concatenated by the data capture subsystem when saving
an XML data record. The default delimiter is a comma (,)

I found the delimiter attribute for checkboxes and select boxes which according to the DTD works when multiple="t", which we have:
[html]

Target Page Type

[/html]

Is this not going to do what I expect? Not a big deal to do in a PT, but wanted to make sure I wasn't missing something.

I'd suggest opening a case with Support - it's quite possible the behavior changed (broke?) in 6.x - I don't have a system to try it out though - so I can neither verify nor refute your experience.

syal123

The delimeter would work when you call the FormAPI method called getValue(). The method returns comma separated value if delimeter is set to comma.

I dont think you can really change the way the DCR XML is created and saved.

What are you trying to do? May be you can create a hidden item and set the value on save so you will have a comma separated value.

Hope that helps.

Frederik

TeamSite 6.5 SP3 Solaris 9
We have a select item in a datacapture.cfg file and would like the multiple selections to not be separate XML value elements, but rather a comma separated list (val1,val2,val3).

I've seen TS 6.5 sp2 + Patch 1767 on Solaris 9 do exactly what you describe, creating val1,val2,val3 in the DCR file as seen on disk. That was for a datatype set to XML type in templating.cfg.

I think the tst.650a.dg.pdf manual hints at the fact that this is only for XML type DCRs, so not for the IWOV type ones.

nipper

I have to agree with Fredo, I only use XML style DCRs and all my select lists are comma separated.

syal123

I've seen TS 6.5 sp2 + Patch 1767 on Solaris 9 do exactly what you describe, creating val1,val2,val3 in the DCR file as seen on disk. That was for a datatype set to XML type in templating.cfg.

I think the tst.650a.dg.pdf manual hints at the fact that this is only for XML type DCRs, so not for the IWOV type ones.

What do you mean by "datatype set to XML type in templating.cfg"?
Can you please give an example?

nipper

Find the manual and read about dcr-type='xml'

ISCBorisB

I've seen TS 6.5 sp2 + Patch 1767 on Solaris 9 do exactly what you describe, creating val1,val2,val3 in the DCR file as seen on disk. That was for a datatype set to XML type in templating.cfg.

I think the tst.650a.dg.pdf manual hints at the fact that this is only for XML type DCRs, so not for the IWOV type ones.

Please note that although internal XML representation differs between XML and IWOV Types both FormAPI IWItem.getValue
and iwperl TeamSite: Smiley Very Happy

CRnode::value return delimited String (not that it matters much to bk99nd, he can either use XML
or do it in PT as mentioned)

syal123

Find the manual and read about dcr-type='xml'

Thanks for telling me to look at the Manual. Nothing personal, but If I could find everything in the Manual, I would probably not even be coming to the devnet forum. Smiley Happy

In my 3+ years of experience, I did not need to play with templating.cfg much and mostly I use dcr-type="iwov" so I was curious what we are talking about here as I never used it.

ISCBorisB

...mostly I use dcr-type="iwov"...

Have you ever wondered why 'dcr-type' attribute exists in the first place?

syal123

Have you ever wondered why 'dcr-type' attribute exists in the first place?

Nope. not in a while

Adam Stoller

Thanks for telling me to look at the Manual. Nothing personal, but If I could find everything in the Manual, I would probably not even be coming to the devnet forum.

In my 3+ years of experience, I did not need to play with templating.cfg much and mostly I use dcr-type="iwov" so I was curious what we are talking about here as I never used it.

If you don't like being referred to the manual for questions that are reasonably basic and actually covered in the manuals - then you're wasting everyone's time - including yours.

dcr-type of either "iwov" or "xml" has been around since at least 5.5.2 - so if you're been doing templating for 3+ years you should have picked up this information somewhere along the way.

Since you didn't - Andy provided you the text to search for in the manuals so that you could find it.

So - rather than "biting the hand that feeds you" - why not accept the information in the manner in which it was intended [smiley not withstanding]

syal123

If you don't like being referred to the manual for questions that are reasonably basic and actually covered in the manuals - then you're wasting everyone's time - including yours.

dcr-type of either "iwov" or "xml" has been around since at least 5.5.2 - so if you're been doing templating for 3+ years you should have picked up this information somewhere along the way.

Since you didn't - Andy provided you the text to search for in the manuals so that you could find it.

So - rather than "biting the hand that feeds you" - why not accept the information in the manner in which it was intended [smiley not withstanding]

Thanks for the information. I am just trying to say that it is not always easy to find information in the manuals. All I was expecting was a 1 liner on that not a whole explanation and I am sure there will be so many people who would not even know about it.

nipper

Thanks for the information. I am just trying to say that it is not always easy to find information in the manuals. All I was expecting was a 1 liner on that not a whole explanation and I am sure there will be so many people who would not even know about it.

That is exactly why I responded the way I did. All you needed to do was search the TST dev manual for dcr-type and it will explain the usage and why

syal123

That is exactly why I responded the way I did. All you needed to do was search the TST dev manual for dcr-type and it will explain the usage and why

Thanks nipper. Smiley Happy

I guess I should try to search the manuals before I put any replies (that ask a question) on the forum. Lesson learnt.

But still I would say I did not find the answer of the bk99nd's question in the manual. The manual does not mention what happens saving items with multiple selections unless I implement the xml type to test. If the answer was there, bk99nd probably would not have asked his question either (maybe). So when I saw the reply, I got curious to know how setting the dcr-type would effect the way the multiple selection values get saved. and as they say...... "Curiosity kills the Cat"

Adam Stoller

Thanks nipper. I guess I should try to search the manuals before I put any replies (that ask a question) on the forum. Lesson learnt.

But still I would say I did not find the answer of the bk99nd's question in the manual. The manual does not mention what happens saving items with multiple selections unless I implement the xml type to test. If the answer was there, bk99nd probably would not have asked his question either (maybe). So when I saw the reply, I got curious to know how setting the dcr-type would effect the way the multiple selection values get saved. and as they say...... "Curiosity kills the Cat"

I thought the original problem might have been related to Bill's use of "iwov" style DCRs and did look at the manuals and did not see anything that seemed to link the data-type style to the DCR-output for multi-select lists (and thus didn't bother to post that as a suggestion).

If, in fact, this is the source of the issue - a bug report should be filed with IWOV to either (a) modify the docs or (b) [preferable - IMO] fix the code to work for both style of data-types.

However - those are details of the specific issue that was originally raised and completely different than your initial post that sparked this side-thread:

What do you mean by "datatype set to XML type in templating.cfg"?
Can you please give an example?

to which the answer you received was appropriate and hence our lack of comprehension for why you should not appreciate the answer.