Why can't the Formula field that can now be declared as unique be used as a key in a relationship? In one of my apps I need to create a real field as a composite of two other fields so i can set up a relationship with another table. This is duplicating data of course, but there's no choice as a formula cannot be related.. So the 'completion' of the task in CB9.8 only went part way. A true composite key can be in a relationship methinks...

This would be a fantastic feature, as it is required so often.

The implementation of the idea started of the feature started? Still not able to mark a formula field as unique... or how can be this done?

The feature will be available in early Q3 this year. Thanks

When is this going to be available in the bridge? Thank you

wow... not even an answer to a critical feature like this planned for over 2 years .... nice

I agree with this suggestion....and for me it was a must, so I just created one in a formula field at the table level.

I have a Vendor Initials field, a time stamp field (text field with a timestamp input from the form) and an Autonumber field (in the table)... I then wrote a formula that becomes a concatenation of the vendor initials, the substring function to pull the year from the timestamp and the autonumber field at the end the string (separated by '.' so the formula won't add the year and the autonumber)

An example of the results looks like this: UL2017.1

This is what my formula looks like:
[@field:VenInit]+Substring([@field:TimeStamp],7,4)+'.'+Right([@field:AutoNumber],4)

The Substring function, and the Right and Left functions can really help you create a very strong composite key (I use mine for purchase order numbering).

The company I'm working for would like the the autonumber to start over each month, so I have to manually do that each month (unfortunately.....I wish that could be on a schedule)... so this isn't without limitations, but it works really well for me to create a unique identifier at least.

Looks like open since June 2015 !

Any Updates ?

I really need this

This is a huge need! Please bring it to the system!

Is there any update on this feature? Seems to be a pretty fundamental database concept not to have on the Caspio platform. This would be fantastically helpful in maintaining data integrity for more complex applications. Thanks.

Calculated fields in RDBMS are called DERIVED ATTRIBUTES. Just a tip it could help guiding caspio's developers get right to the issue.

I am having problems keeping truck of student records on my app were many duplicates have to be deleted over and over again due to human data-entry error. This feature is called COMPOSITE KEY in RDBMS. An alternative would be adding calculated data field on Caspio tables, one that would allow building the query right at the table structure rather than on the data page and have it unique

This would be perfect for many situations I have to create workarounds for.

Hi!
I have also been looking for this feature, as I have table that links tw other tables through many-to many-relations. Therefore, I tried to prevent registration of two records with the same combination of IDs from the two tables in the third table (linktable).

This is absolutely necessary in some situations. They could really do well to add this.

I couldn't agree more.

To further cement Caspio as MS Access in the cloud, the ability to extract unique records using multiple keys is critical. The tool works great for getting data in, but we need more mechanisms like this for reporting.