Scenario: Initially I had a user set up with username, as example, "AB1234&

Scenario: Initially I had a user set up with username, as example, "AB1234". Since it's case-sensitive we deactivated that user and changed it to "ab1234". Now when I log in as "ab1234", the following error appears in the log:

com.appiancorp.suiteapi.content.exceptions.InsufficientNameUniquenessException: Name is insufficiently unique

Any suggestion on how to resolve this since we cannot delete the original user? Having issues uploading a profile picture for the 2nd user and also when logged into Tempo I can see that there are tasks assigned to my user because of the "(2)" however nothing appears when I click on the "Tasks (2)" link....

OriginalPostID-78157

OriginalPostID-78157

  Discussion posts and replies are publicly visible

Parents
  • This will happen if your RDBMS is not case sensitive for text columns. When a user logs in to Appian as ab1234 it will try to add a new entry to the usr table in the primary data source, the username has to be unique, but given your RDBMS is not case sensitive it thinks that ab1234 = AB1234 which results in the error you're seeing.

    In order to fix the problem you have to change the collate of your usr table in the primary data source to a case sensitive one:

    ALTER TABLE usr
    ALTER COLUMN username
    COLLATE SQL_Latin1_General_CP1_CS_AS
Reply
  • This will happen if your RDBMS is not case sensitive for text columns. When a user logs in to Appian as ab1234 it will try to add a new entry to the usr table in the primary data source, the username has to be unique, but given your RDBMS is not case sensitive it thinks that ab1234 = AB1234 which results in the error you're seeing.

    In order to fix the problem you have to change the collate of your usr table in the primary data source to a case sensitive one:

    ALTER TABLE usr
    ALTER COLUMN username
    COLLATE SQL_Latin1_General_CP1_CS_AS
Children
No Data