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

setting hidden replicant value

garima

I am using Teamsite 6.5 on windows 2000 sever.

I have a replicant item which is hidden.
I want to set the values of replicant item through Formapi.
But getting error whenevr using setValue function.
Any idea where am I wrong.

Find more posts tagged with

Comments

Migrateduser

I think you'll need to post more of your FormAPI for anyone to diagnose the problem.

Adam Stoller

I am using Teamsite 6.5 on windows 2000 sever.

I have a replicant item which is hidden.
I want to set the values of replicant item through Formapi.
But getting error whenevr using setValue function.
Any idea where am I wrong.

I'm not sure, but you may have to not declare the item hidden in the DCT, but instead set the values and then hide the item all within the FormAPI code.

Also note - you'll get an error if the first item declared in the DCT is hidden - something about not being able to set focus on a hidden element.

garima

The same code is working if I make it visible.
And again gives an error if it is made hidden

Migrateduser

Then what if you were to set it visible (i.e. not set it as hidden) in the DCT and instead change it to invisible in FormAPI with item.setVisible('false') after you set its value ?

ISCBorisB

The same code is working if I make it visible.
And again gives an error if it is made hidden

Please refer to "datacapture6.0.dtd". You will see that "hidden" tag may have only "allowed" / "callout" nested tags. You are trying to nest the
whole replicants/items there, it is very doubtfull you'll get anything that way. So, as proposed before remove hidden tag from DCT and do
what you need in FormAPI

DbDemo.rptdesign

garima

I am using Dct of IWov format.

ISCBorisB

I am using Dct of IWov format.

No you are not. You may be using XML/IWOV format for your DCRs, as indicated in your "templating.cfg".
I'm talking your DCT's (datacapture.cfg) DOCTYPE, look at the top few lines of DCT Code

ISCBorisB

Also note - you'll get an error if the first item declared in the DCT is hidden - something about not being able to set focus on a hidden element.

I beleive it has been fixed in 6, certainly in 6.5

Adam Stoller

I beleive it has been fixed in 6, certainly in 6.5

Nope - I just ran into it yesterday on 6.5 SP2 on Windows - I changed the hidden field to a readonly field and that "fixed" the problem (I could also have moved the item within the structure, but ...)

ISCBorisB

Nope - I just ran into it yesterday on 6.5 SP2 on Windows - I changed the hidden field to a readonly field and that "fixed" the problem (I could also have moved the item within the structure, but ...)

The following works perfectly well for me. Perhaps the reason is required="f", absence of "allowed" block or something else, not sure.[html]

Manage content for our services compare Page

...
[/html]

garima

Hi,
I am using datacapture5.0.dtd for my DCT

ISCBorisB

Hi,
I am using datacapture5.0.dtd for my DCT

So? Either way, hidden tag is subelement of item tag and may contain only allowed and callout subelements.

TeamSite® FormsPublisher Developer’s Guide Release 6.5
<hidden> Specifies that the data will not be shown in the data capture form. A <hidden> field may receive data from a callout program.
Note: You cannot currently specify a default value.
Attributes:
.. required: See <browser>.
Subelements:
.. <allowed>: See <browser>.
.. <callout>: See <browser>.

garima

Thanks Dava.It worked ,If set to hidden thr Formapi.

jkm

TeamSite® FormsPublisher Developer’s Guide Release 6.5
<hidden> Specifies that the data will not be shown in the data capture form. A <hidden> field may receive data from a callout program.
Note: You cannot currently specify a default value.
Attributes:
.. required: See <browser>.
Subelements:
.. <allowed>: See <browser>.
.. <callout>: See <browser>.

I am just going to bang my head now ...
Cant we specify default values to hidden field?
In my dct if I use hidden field, i get null value in my formAPI and if I make them visible then it works fine ..

A small snippet of my DCT field
[html]

Image Size
456*0

[/html]

I tried making this item "required", radio button etc but still no luck.. I want to pass these default value to my CallServer API to match the imageSize,
I know I can use formAPI to make it invisible but thts hard way to achieve this when it is documented in the templating guide to use hidden tag
any pointers on this?

JonathonG

There is no way to use with . This has always seemed to me to be an obvious limitation to templating, but AFAIK, it has never been fixed.

Adam Stoller

There is no way to use <default> with <hidden>. This has always seemed to me to be an obvious limitation to templating, but AFAIK, it has never been fixed.

True, but the work-around is to set the default value, and then use FormAPI to set the field to hidden rather than declaring the field as hidden in the DCT.

jkm

hmm...I dont understand the use of hidden field without default value..except to hide the field for user profiles ....This is an important feature which should be working as I can see..
At the moment either we need to populate the field using formAPI/cgi callout etc or loop through all the child replicants to make this field invisible.. this is annoying Smiley Sad

But I like the Interwoven approach to generate work for IWOV consultants Smiley Wink

JonathonG

True, but the work-around is to set the default value, and then use FormAPI to set the field to hidden rather than declaring the field as hidden in the DCT.

<soapbox mode="on">
True, but the workaround sucks (to use a technical term). FormAPI doesn't run when just viewing a DCR, so whatever you were trying to use as a hidden is suddenly visible to the user. The frequency of posts on DevNet with the subject of "Hidden fields no longer hidden when viewing DCR" or some such point to the problem.
</soapbox>

Adam Stoller

<soapbox mode="on">
True, but the workaround sucks (to use a technical term). FormAPI doesn't run when just viewing a DCR, so whatever you were trying to use as a hidden is suddenly visible to the user. The frequency of posts on DevNet with the subject of "Hidden fields no longer hidden when viewing DCR" or some such point to the problem.
</soapbox>

Touche! That issue had slipped my mind at the point at which I was responding.