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

DCT with multiple containers loads slow

ratna

hi,

I have a requirement in DCT which includes lot of containers with items which will dynamically populate depending on the user selection.
There are like 40 Item handlers in this form and on forminit(), I am checking in each of the child replicants, which is selected and depending on the value it returns, I am making that container visible and remaining containers as visible false.

When the DCR is initiated, it takes 6-8 mins to load all the items properly making the unselected ones as hidden.
Can the performance of loading the DCR for the saved DCRs be improved?

Please suggest a solution.

Find more posts tagged with

Comments

Adam Stoller

hi,

I have a requirement in DCT which includes lot of containers with items which will dynamically populate depending on the user selection.
There are like 40 Item handlers in this form and on forminit(), I am checking in each of the child replicants, which is selected and depending on the value it returns, I am making that container visible and remaining containers as visible false.

When the DCR is initiated, it takes 6-8 mins to load all the items properly making the unselected ones as hidden.
Can the performance of loading the DCR for the saved DCRs be improved?

Please suggest a solution.

Without seeing all the code - it's kind of difficult how to improve it. Generally - the bigger the DCT, the longer it will take to render. The more inline scripts you have, the longer it will take to render. etc.

So - Can the performance be improved - possibly.
Can we help you to improve it - possibly, but only if you post all the code - and then we're doing your work for you - something you get paid for, and we're doing it free of charge.

I suggest you create an alternate DCT - starting with the bare-bones of the existing one - without any FormAPI or inline calls - and then start adding that functionality back in slowly to figure out where you are running into performance issues. Then see if you can create a simple DCT that uses that functionality and still demonstrates the performance problems.

If at that point you still cannot figure out how to make that simplified DCT load in a reasonable time-frame - post that code.

Firenze

A big performance booster is to collapse all your replicants in your templating.cfg setting. The default is to only collapse if you have 3 or more replicant children but for a big DCR instances with lots of replicants causes performance delay.

This point is documented in the Forms Publisher guide as a performance improvement.

To identify your replicants by name instead of number use the "isTitle" attribute of your DCT items.

Dynamic Bar With Groping - New.rptdesign

ratna

hi ghoti,

Thanks for ur reply.
Regarding the performance, I asked a question whether is there any way to improve if any of the members have come across this situation and I didn't mean to get the work done by some others by posting here.I am looking for a friendly suggestion or possibly a better solution to what I am doing.

Evansw

Firenze - I found your help very useful. We have forms that are sometimes quite large with child and subchild replicants. This option has improved performance for us with two simple changes.

Many thanks.