Dropdown lists not behaving correct in TS 6.7.1

I have a DCT on which visibility and loading of dropdowns is manipulated based on the user interaction using Form API. These templates are working fine in TS 6.1. We are in the process of upgrading to TS 6.7.1 and our templates which have such manipulation of drop lists, are not showing the controls correctly. Following example will elaborate the scenario I am trying to explain.

Scenario desired
----------------
Let’s assume, on a Data capture, we have radio button control with two options yes and no.

STEP 1

On the OnChange event of this control I would like to show few drop lists (more than 1) by setting their visibility to true.

STEP 2
These drop lists are the top level options of a hierarchical classification and the onChange event of these newly displayed drop lists may show some new drop lists with additional classification options. To accomplish this, a callserver call is made and the options of the new drop list are fetched and the control is made visible.

Observation On TS 6.7.1
------------------------
1.
Execution of STEP 1 does not display all the drop lists. It only displays the first droplets. The template is spread across 2 pages and if the user goes to the second page and then comes back to the first page, all the controls are visible just fine.
2.
Execution of STEP 2 makes the call server call and the called application calls a method in the js file associated with the DCT and passes the values to be populated but the control is not visible. Again when the user moves to page 2 and comes back, the control is visible with the options populated just fine.
3.
If the controls are not hidden, they get populated just fine.

This code has been working fine in TS 6.1.

If anyone has observed a similar problem and has any insight into it, it would be highly appreciated.

Find more posts tagged with

Comments

nipper

The only issue I had with the upgrade that sounds *similar* to what you are seeing was due to access controls placed on DCRs. I had fields accessible only to Admin or Master and the Formapi was behaving badly. Are any of these fields using the access controls for roles ?

SBH

No they are not dependant on any role

Adam Stoller

Have you tried (temporarily) putting everything on one page to see if everything works in that configuration (i.e. verify whether the problem is with regard to using multiple page DCTs or not).

If it works with a single page DCT - open a ticket with Support, because it is likely a bug that was not tested for during their QA process (I think multiple page DCTs are fairly rare for a variety of reasons, and thus may not be getting fully tested for all possible scenarios)

If possible (just prior to opening the case) try to create a small, simple, repeatable DCT/FormAPI piece - the easier it is for them to reproduce the problem, the more quickly it is likely to get attention.

rsubbarao

We are also in the process of migrating to 6.7.1 from 6.0 and having similar issues. One point to note, most of the templates in our projects are multi-paged.

SBH

The problem happens even if the dct is on a single page. A ticket has already been opened with IW.