Radio buttons are not selected in table of embeded section
I have a big problem with radio buttons in a table (grid) of an embeded section:
In fact I have three sections one embeded in another, each contains a dynamic layout with a table in which a property contains another section, and one of the properties in the more embeded section contains radio buttons.
When I add lines in the first instance of the more embeded section (what I name 'instance' here is a line in the section that contains the more embeded section), if I select a value from the radio buttons for each rows, there is no problem.
But when I add lines in another (a second or a third) instance of the more embeded section, then if I select a value from the radio buttons, it is always the corresponding line in the first instance that is selected.
Here is an extract of my screen to explain what happens. For example when I hover the cursor upon the green radio button, it is the red radio button that is hightlighted. And if I clic on the green then the red will be selected.
This strange behavior doesn't occur with other types of component. Here in my screen the date time and the text input properties are properly entered.
And what is more strange, is that when I replace the radio buttons with dropdowns, there is no problem anymore, lines and values are correctly selected. But I want radio buttons:-)
I've found a post on the community that tells there was such a problem in Pega 7.3.0 that have been resolved in Pega 7.3.1: https://community.pega.com/support/support-articles/radiobuttons-dynami…
Although I'm working with Pega 7.3.1 I still have a similar problem, what do you think about it?
It seems the radio buttons are unreachable, but perhaps I have not well configured my screen...
Thank you very much for your help!
***Edited by Moderator Marissa to update platform capability tags***
If there are 2 radio button fields on the same screen which has the same property name, then it is bound to happen that the same id will be generated, since when we click on the radio, it looks for the radio button from the top of DOM and when it founds the id the checkbox gets checked. In your case are you using in property Type Montant on the same screen?
Finally all Type Montant fields are in the same screen, but Montant is embeded section in Avantage, and Avantage is embeded section in Regime, so by concatenation Type Montant fields don't have the same name:
The name of Type Montant 1 is $PpyWorkPage$pAssureTemp$pListeRegimes$l1$pListeAvantages$l1$pListeMontants$l1$pTypeMontant (Regime 1, Avantage 1, Montant 1)
And the name of Type Montant 3 is $PpyWorkPage$pAssureTemp$pListeRegimes$l1$pListeAvantages$l2$pListeMontants$l1$pTypeMontant (Regime 1, Avantage 2, Montant 1)
Without concatenation, if we considere only Type Montant name, yes it is the same name, because the same line number in each Avantage.
But one Type Montant is in Avantage 1, and the other is in Avantage 2, and both Avantages are in Regime 1.
What is strange is that when I change the field type, if I replace radio button with dropdown, the problem disappears. And there are no problem with the other fields of Montant data, such as Date Montant or Montant Brut, which are of Date Time and Text Input types.
Yes this explains why there is no problem with dropdown... But how to resolve it with radio buttons? Because the name, for example $PpyWorkPage$pAssureTemp$pListeRegimes$l1$pListeAvantages$l2$pListeMontants$l1$pTypeMontant, is automatically generated. And it seems to be correct, here it uniquely identifies one radio button, the first TypeMontant in the second Avantage of the first Regime. The name seems to be correct but not the ID, TypeMontant0_ri_1, instead of TypeMontant0_ri_3 in this case. I think (I hope:-) it is possible to resolve it, else it will mean that we can not use radio buttons in embeded sections... Perhaps I have not well configured something in my sections, so is there a way to generate the expected ID? Or perhaps is it a bug, and in this case is there a hotfix to resolve it?