Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

"Duplicate not allowed" option on dynamic attributes not working

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on April 23 2020 at 09:34 UTC

Hi Experts,


I have created a Dynamic attribute under the Global Configurations--> Register User.


and selected the options, "Editable on update" and "Duplicate not allowed".


Ideally when tried to enter a new value(which is duplicate) in this field, SSM should check for the Duplicates, and a pop should show saying "Duplicate not allowed for the field- fieldname".


This behavior is working in version 5.4.1 whereas in the new version 5.5.0 its not working.


Is the issue is with the new version of instance or have i missed anything in the configuration.


Please anybody let me know, if this is an issue with configuration or SSM version.


Thanks in advance,

Naveen

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.
3 REPLIES 3

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 5 2020 at 10:21 UTC

This should work the way you described during Create or Update User. Please open a support ticket if it doesn't.


Regards,

Aditya

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on May 7 2020 at 14:06 UTC

HI Aditya,


Brought this issue to Saviynt support, this seems to be a bug.


Thanks for the information.

Naveen

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.

Community_User
Saviynt Employee
Saviynt Employee
Originally posted on June 16 2020 at 12:53 UTC

Its a bug.


Patching to SP1.8 for 5.5 fixes the issue

This message was previously posted on Saviynt's legacy forum by a community user and has been moved over to this forum for continued exposure.