0
Answered
IdB 4.1 uses GUIDs in UI Errors
IdB provides meaningless GUIDs instead of name when reporting errors in UI. Need to provide name of connector or adapter.
Example:
Adapter import all entities for adapter e14dde8a-73ff-4723-acbd-b34f5cb38ac0 failed with reason EMAIL_ADDR is not a valid LDAP attribute name Parameter name: attributeName. Duration: 00:00:01.1860000
Customer support service by UserEcho
I have added the adapter name to this and a few other messages.