Disable Replicant add on item change

I am not sure if this has been addressed before. I have a replicant container with 2 items. What I am trying to achieve is if a user selects "All" for both the items then do not allow anymore additions of the replicant. Is this possible with FormAPI? I am on TS 6.7.1 & solaris 10.

Thanks,
K

Find more posts tagged with

Comments

Lex

If I'm understanding you correctly, yes, this can be done with FormAPI, but perhaps not in the manner you're hoping to. What you'll need to do is add an event handler for the "OnReplicantBeforeAdd" event. In that handler you can check to see if the existing instance of the container has "All" selected for both items it contains and return false to cancel adding a new instance of the container.

Something else you'll likely need to consider is what to do in the situation where there are existing instances of the container and then "All" is selected for both items on a newly added or existing instance. You'd probably want to go back through and delete the other existing instances of the container. That's a SWAG, though, since I'm not sure I'm entirely clear on what you're attempting to accomplish.

logs.zip

kaalraa

I am not sure if this has been addressed before. I have a replicant container with 2 items. What I am trying to achieve is if a user selects "All" for both the items then do not allow anymore additions of the replicant. Is this possible with FormAPI? I am on TS 6.7.1 & solaris 10.

Thanks,
K

I second to Lex, as this is what we have implemented in one of our project.

cascading_datePicker.rptdesign

kajjubee

Thanks Lex, yes its exactly what you have mentioned. On second thoughts I feel the "SWAG" you mentioned is a big one and I am thinking of maybe trying to simplify this as follows:
Have a separate checkbox field to choose All and a separate replicant container for dropdown with the rest as before. If a user chooses "All" then hide the dropdown replicant container. If not, everything is great. Atleast I don't have to program the complications of having to deal with "All" in replicants. What say?

cheers,
K

ISCBorisB

I second to Lex, as this is what we have implemented in one of our project.

Just wondering, what were your criteria to add such an invaluable contribution?

Seriously, you had an excellent opportunity to second 30+ other posts/opinions.
Why have you chosen this one?

Lex

Thanks Lex, yes its exactly what you have mentioned. On second thoughts I feel the "SWAG" you mentioned is a big one and I am thinking of maybe trying to simplify this as follows:
Have a separate checkbox field to choose All and a separate replicant container for dropdown with the rest as before. If a user chooses "All" then hide the dropdown replicant container. If not, everything is great. Atleast I don't have to program the complications of having to deal with "All" in replicants. What say?

That does sound better and would probably end up being less confusing to the users. And, as you say, much easier to implement and maintain.

kajjubee

Again, appreciate your comments Lex. I was able to implement your original solution using "OnReplicantBeforeAdd". It wasn't as complicated as I expected it to be. I just didn't want to change the structure of the DCT by adding the new field I mentioned. Anyway, both ways would have worked but I chose your path Smiley Happy

Thanks,
K