Records and Entries

The most fundamental building blocks of data in Clevero are Records and Entries.

1. Records

Records are the building blocks of data in Clevero that define how data is structured and stored.

Each record has its properties, including Fields, Auto ID Schema, and linked configurations like Layouts that determine how data is displayed to users in different contexts. Examples of Records would be an Invoice object or a Sales Opportunity object.

To create or modify a record, follow the steps in the video demo below.

You can also follow the written steps guide below.

1. Go to "Settings" > "System Settings".
2. Click on "Records".
3. Select "New Record".
4. Fill in all required fields. Here's a description of each:
   1. Name: It refers to a record's identifiable label or title. For example, an invoice record might have a name like "Invoices" or "Monthly Sales Report."
   2. Internal ID: A unique identifier assigned to each record within Clevero's system. It serves as a backend reference that helps identify and differentiate records programmatically.
   3. Icon: A visual representation or symbol associated with a record. Icons are often used to provide a quick visual reference and aid in recognizing and navigating records.
5. Set the "Record Type" to "Record".
6. Click on the "Submit" button to save the changes.

📘

Records vs. Subrecords

• Records store the main set of information (e.g., a customer profile, or project).
• Subrecords are linked to a record and help organise additional details in a structured way (e.g., notes, tasks, or supporting documents).

This makes Subrecords a useful way to streamline and structure related information within your records. For detailed instructions, please refer to the Sub-records guide.

2. Entries

Entries are rows of information that belong to a given Record. In other words, they represent specific instances or examples of the data stored within a Record. For example, if we consider the "invoices" Record, each entry would correspond to a unique and specific invoice stored in Clevero.

It's important to understand the distinction between the concept of the Record and its corresponding Entries.

• When we refer to "invoices" as a concept or object within the system, we are talking about the overarching Record that encompasses all the invoices.
• On the other hand, when we mention something like "Invoice #13342," we are referring to a specific Entry within the "invoices" Record, highlighting an individual invoice with a particular identification number.

📌 Need Help?

If you require assistance or encounter any issues, please don't hesitate to contact us for further support.

I need support