Facing issue with catalogue variable name

[Puneet Hegde1]

Dear All,
I'm our instance whenever variable is created it's value has been showing like formatter, formatter1, etc because of it we are not able to write on any catalogue client script which is effecting significantly and it is happening only for variable and if we wanna write some script on variable set everything is fine does anyone know how to resolve it?
I have attached screenshot for reference.

Thank you,
Puneet

 

[ShubhamGarg]

Hello @Puneet ,

What I can understand, this is UI Policy action not Catalog client script. Is that correct?

To write a catalog client script, you can copy variable name to write your logic.

Hope it helps.

Regards,

Shubham

[Puneet Hegde1 · Accepted solution]

Dear All,
thank you for your kind replay, I have found the solution in my instance, the previous developer replace default variable name with other name and deactivated it from the table because of it all the new variable is visible as formatter.
Steps I have taken:
1) checked the variable names of the question tables

2) check the client script which will normally auto populate the name field based on question field.
3) verify the table using the backend value from the script.
4) activated the field from the table level and added in variables layout.

the above steps resolved issue.

Key takeaway: our instance was highly customized and some of the job variable. has been replaced by previous vendor.

Thank you,
Puneet