Learn about Redwood and be one of the first to join the conversation

Visit Redwood Community
Data table key best practices — Cloud Customer Connect
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Data table key best practices

Received Response
22
Views
1
Comments
edited Jul 20, 2022 3:53PM in Configure Price Quote 1 comment

Summary:

Best practice for the number of Key'ed fields in a Data table

Content (required):

We have a Homologation table with 5 fields in the schema and have found duplicates and just cleaned it up by exporting to excel and reimporting the clean data. Was wondering if there is any downside to have all 5 fields in the table Key'ed as to not allow duplicates in the future

Version (include the version you are using, if applicable):


Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!