Uniqueness of a field

sergeiz1 over 8 years ago

Hello!

What is the best way to keep some CDT field unique? It will be a constraint in the database, but the database error message is not user friendly.

I can set it up as a query rule or expression and validate manually in the interface. In this case the designer should remember what fields have to be validated.

May be there is an easier and straightforward way to achieve it?

Discussion posts and replies are publicly visible

Parents

0 PhilB
A Score Level 1
over 8 years ago

That's correct, it is quite common. However, you usually generate the unique items; in the case of IDs for primary keys, for example, you don't ask the user to enter the unique ID.

I'm guessing you have a requirement for a name to be unique - but my question would be why does it need to be? I'm just curious what the requirement is :)

Appian is quite cabale of implementing locking - optimistic or otherwise - but it does take a bit of work. This might be interesting reading if you've not already seen it: docs.appian.com/.../Database_Schema_Best_Practices.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 PhilB
A Score Level 1
over 8 years ago

That's correct, it is quite common. However, you usually generate the unique items; in the case of IDs for primary keys, for example, you don't ask the user to enter the unique ID.

I'm guessing you have a requirement for a name to be unique - but my question would be why does it need to be? I'm just curious what the requirement is :)

Appian is quite cabale of implementing locking - optimistic or otherwise - but it does take a bit of work. This might be interesting reading if you've not already seen it: docs.appian.com/.../Database_Schema_Best_Practices.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data