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

container hide

getnaren

[html]

I have nested containers
grps -container
grp- subcontainer
search_items - container
linked_item - subcontainer
auth -container

I need to to hide the auth container and I tried like this...but not working...can anyone see this and let me know what is wrong

function initDCR()
{
//Make auth container hidden
var AuthContainer = IWDatacapture.getItem("/doc/grps/grp/search_items/linked_item/auth");
if (AuthContainer){
AuthContainer.setVisible(false);
}

}

[/html]

Find more posts tagged with

Comments

nipper

When are you running initDCR ? OnFormInit ?

getnaren

When are you running initDCR ? OnFormInit ?

yes.. like this

IWEventRegistry.addFormHandler("onFormInit", initiDCR);

Adam Stoller

I have nested containers

 grps -container
   grp- subcontainer
  search_items - container 
  linked_item - subcontainer
   auth -container

I need to to hide the auth container and I tried like this...but not working...can anyone see this and let me know what is wrong

function initDCR()
 {
//Make auth container hidden  
 var AuthContainer = IWDatacapture.getItem("/doc/grps/grp/search_items/linked_item/auth");
 if (AuthContainer){
  AuthContainer.setVisible(false);
 } 

 }

The highlighted line is likely the problem.
Are these "containers" or "replicant containers" - if they're replicants you must iterate through the various children at each level to get to the specific container in each "tree" that you want to hide.

Alternatively - if you set an eventHandler for it - (in which case you can use the path you have specified there) the handler function will be passed the specific item that triggered it, making it trivial to act on it.

getnaren

The highlighted line is likely the problem.
Are these "containers" or "replicant containers" - if they're replicants you must iterate through the various children at each level to get to the specific container in each "tree" that you want to hide.

Alternatively - if you set an eventHandler for it - (in which case you can use the path you have specified there) the handler function will be passed the specific item that triggered it, making it trivial to act on it.

Ghoti,

they are replicant containers...
and I tried this (see the attachement)

but its not working

nipper

Liberally use alerts and verify you have exactly what you need in the JS. You may want to simplify the DCT and hardcode some JS to see if it works in any case.

There is a defect in 6.7.1 where setVisible is not working correctly in certain circumstances, though I am unclear on what those are. You may want to talk to support if you are certain that the JS is correct.

nipper

FYI I think there is a patch to 6.7.1 for this, bug 69581.

moonkhanna

Sorry for my ignorance but I am confused. If you want to hide the container on formInit .. why dont you just specify it as hidden in your DCT xml itself. You can then try and make it visible when required.

getnaren

Sorry for my ignorance but I am confused. If you want to hide the container on formInit .. why dont you just specify it as hidden in your DCT xml itself. You can then try and make it visible when required.

you mean in datacapture.cfg? how

Adam Stoller

you mean in datacapture.cfg? how

Please read the FormsPublisher Developer's Guide for details on 'hidden'

As for the code you posted - I second nipper's comment - add alerts to make sure you're getting what you think you're getting - you may find that one part of your multiple-nested loop is not working correctly and once fixed, resolves your issues.

screenshot.bmp