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

Creating DCT elements that are not visible on open, without FormAPI?

talemyn

I have a replicant in a DCT that contains a handfull of fields in it. For one of the fields, if it contains a specific value a specific value, one of its "sibling fields" needs to be visible, but, for all other values (which is a majority of the time), the sibling field needs to be hidden.

That in itself it easy enough to accomplish, but there are usually many of these replicants (and they are in a multi-level, "or" replicant structure, so the fields are not always in the same place in each replicant) and having to use FormAPI to unt down and hide 99% of those sibling fields really slows down the load of the DCR.

Does anyone know of any way to have all of those sibling fields start out as inherently hidden (or, I guess "invisible" is really what I want) so that I can just make the 1% visible, when needed?

Find more posts tagged with

Comments

talemyn

Hmmmm . . . I should probably have posted this under the "TeamSite FormsPublisher (Templating)" topic.

Please move if it makes sense to do so.

kaalraa

Use the init function through FormAPI and make all sibling fields hidden on initialization of the form. Again on change of field value you can make that particular sibling visible.

RTFM FormAPI for more on setting fields visible or hidden.

I have a replicant in a DCT that contains a handfull of fields in it. For one of the fields, if it contains a specific value a specific value, one of its "sibling fields" needs to be visible, but, for all other values (which is a majority of the time), the sibling field needs to be hidden.

That in itself it easy enough to accomplish, but there are usually many of these replicants (and they are in a multi-level, "or" replicant structure, so the fields are not always in the same place in each replicant) and having to use FormAPI to unt down and hide 99% of those sibling fields really slows down the load of the DCR.

Does anyone know of any way to have all of those sibling fields start out as inherently hidden (or, I guess "invisible" is really what I want) so that I can just make the 1% visible, when needed?

ravio

I have a replicant in a DCT that contains a handfull of fields in it. For one of the fields, if it contains a specific value a specific value, one of its "sibling fields" needs to be visible, but, for all other values (which is a majority of the time), the sibling field needs to be hidden.

That in itself it easy enough to accomplish, but there are usually many of these replicants (and they are in a multi-level, "or" replicant structure, so the fields are not always in the same place in each replicant) and having to use FormAPI to unt down and hide 99% of those sibling fields really slows down the load of the DCR.

Does anyone know of any way to have all of those sibling fields start out as inherently hidden (or, I guess "invisible" is really what I want) so that I can just make the 1% visible, when needed?

If the time taken for DCR initialization is the only concern to be addressed

You could start with all the items in question set to hidden onFormInit and set the replicant collapsed, This should make the form load faster
When the user expands the replicant container you could run your actual FormAPI function
In the function itself, use logic for unhiding/displaying items conditionally

talemyn

Thanks for the suggestions guys . . . all of the stuff that you suggested was what I was doing already. What I was really hoping for was a way to have the DCT fields come up invisible at the start without using any FormAPI. "Hidden" would do it, but then I wouldn't be able to make any ones visible later on if they needed to be, and that's not an option.

However, after doing some further testing, it doesn't look like the FormAPI is causing the delay that we are seeing. A few well placed alerts are showing that the actual loading of the data from the DCR is the bulk of the delay (which isn't really a surprise, given the amount and complexity of the data involved in them).

I'd still be curious to hear any ideas to my initial question, though, if anyone has any . . . it seems like there should be a way to have an element come up defaulting to invisible whithout having to run through it with FormAPI.