and more in a single search tool across platforms. Read the announcement here. |
01/29/2024 02:23 PM - edited 01/29/2024 03:50 PM
Hi All,
We have two dynamic attributes: DA1, DA2.
DA2 can have value either '1' or '0'. We want that if the value in DA2 is '1' then HIDE DA1 else show DA1.
I have configured it as below:
- Type of DA2 is ENUM with possible values 0,1
- Made DA2 as the parent attribute of DA1. For DA1(child attribute) set the action to perform when parent attribute changes as 'Mapping'
- Set the default value in DA2 as '1'.
- Used the Action String in DA2: SHOW###DA1###0___HIDE###DA1###1___HIDE###DA1###NONE
So, ideally when ARS page loads since the value in DA2 will by default be populated as '1', the DA1 should remain hidden. But this is not happening. If I remove the value in DA2 by clicking on cross (or) If I select the value as '0' and then again manually select the value as '1' in DA2, only then it is getting hidden.
I want that by default when the ARS page loads, this field DA1 should be hidden. Is it possible to achieve?.
When ARS Page loads the field 'Please enter GitHub username'(DA1) is not hidden even though value in 'dummy'(DA2) is correctly populated as '1'.
But, when I manually select value as '1', by removing then selecting, it works fine and 'Please enter your GitHub username' field(DA1) is hidden.
Thanks,
Atul Singh
01/29/2024 03:55 PM
Use SQL ENUM
select 1 as id union 0 as id
01/29/2024 04:11 PM
I tried 'SQL ENUM' as well. It is causing the same issue. On ARS Page load, it is not hidden even if the value in DA2 is '1'.
01/29/2024 04:14 PM
Use boolean
01/29/2024 04:18 PM
@rushikeshvartak I cannot use boolean in this case. The value in DA1 is dynamically fetched using a SQL Query:
select (CASE WHEN COUNT(u.username)=1 THEN '1' ELSE '0' END) AS ID from users u inner join accounts a on u.secondaryemail = a.customproperty2 where u.userkey = ${requestee} and a.endpointkey=84
01/29/2024 04:22 PM
When form is loaded what value of da1 is populated in logs ?
01/29/2024 05:00 PM
01/29/2024 07:20 PM - edited 01/29/2024 07:21 PM
Use Gen2 UI it works
On load
After changing
01/30/2024 03:38 AM
01/30/2024 03:42 AM
Global configurations>Preferences>Enable Request Modern Experience Gen 2 (Beta)
01/30/2024 12:03 AM
@AS5278 I have checked and perfectly working for me.
Action String in DA2(Parent attribute): SHOW###DA1###0___HIDE###DA1###1
DA1 is hidden when DA2(Parent DA) default value is 1
DA1 is showing when DA2(Parent DA) value is 0
01/30/2024 05:40 AM
@SumathiSomala @rushikeshvartak
The SHOW/HIDE functionality is working fine now. I didn't make any change I used the same configuration as earlier. It's strange, the changes made in the Dynamic Attribute Configuration sometimes reflects instantly..but sometimes takes too long to reflect. I think this is the issue I was facing. I even ran the 'Endpoint sync trigger' and 'Endpoint delta sync trigger' but it was not reflecting. Now, its working fine.
Also, since 'DA2', is the dummy attribute based on whose value we have implemented the SHOW/HIDE functionality for DA1. Is there any way to keep this dummy attribute 'DA2' always hidden from the user in ARS page?.
Thanks.
01/30/2024 06:39 AM
You can always trigger microservices from postman which always run properly.
you can’t keep da2 hidden