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

Chasity Davis over 11 years ago

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....

Discussion posts and replies are publicly visible

0 Eduardo Fuentes
Appian Employee
over 11 years ago

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
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 11 years ago

I forgot to ask what RDBMS you are using:

1. If using MySQL use this statement to change the collation:

ALTER TABLE usr COLLATE latin1_general_cs;

2. If using SQL Server use these other three:

ALTER TABLE usr DROP CONSTRAINT usr_username_uc;
ALTER TABLE usr ALTER COLUMN username nvarchar(255) COLLATE Latin1_General_CS_AS NOT NULL ;
ALTER TABLE usr ADD CONSTRAINT usr_username_uc UNIQUE NONCLUSTERED (username);
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jordanp over 11 years ago

Hey Eduardo, I'm the system administrator in this scenario. Using the commands you suggested, the username column is now case sensitive, which is great. However, it was not case sensitive when the AB1234 and ab1234 users were created, so there is only one entry in the database for that user (since it saw the second one as a duplicate and did not store it). So how do I let the database know that there should be two users in there? One with uppercase and one with lowercase?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chasity Davis over 11 years ago

Thanks Eduardo for the initial response and thanks Jordan for keeping this item going while I'm busy with the other Appian folks onsite!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 11 years ago

Hello Jordan, just ask
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 11 years ago

...just ask this user to login to Tempo and the entry will be created automatically
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 11 years ago

Given it was not case sensitive it wasn't being created but now that it is, the row will be added.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Chasity Davis over 11 years ago

Eduardo - The user is actually myself. When DEV was set up my username was created with uppercase and then it was determined it should be lowercase. I have reactivated the "ABC1234" user and logged into Tempo. When I log in as the user that I really have been using "abc1234" I still am having issues uploading my profile picture, however I can how access my tasks from within Tempo. So one thing is working now. :-)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 jordanp over 11 years ago

Yeah, I can confirm that just as Eduardo said, the lowercase username was added to the database automatically after you logged in. However, we're still seeing the errors in the log files fairly regularly.

"ERROR com.appiancorp.ag.util.UserPhotos - Could not generate thumbnails for user 'abc1234'."

"com.appiancorp.suiteapi.content.exceptions.InsufficientNameUniquenessException: Name is insufficiently unique"
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 11 years ago

Whenever a user uploads a profile picture, it is stored under Default Community > System Knowledge Center > User Pictures and Default Community > System Knowledge Center > User Pictures > Thumbnails. This feature is designed to check that the file names are unique in the Thumbnails directory but is not case sensitive.

What is the user that you actually want to preserve?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel