Relations define data connections between concepts. Through this structure, records are linked to each other, related records are displayed in forms, and reporting can be done.

Relations design in Robosme;

• Data model,
• User experience,
• Performance
  is a critical step.

One-to-Many (1:N)

One-to-Many relations are defined through Lookup fields.

Features:

• Multiple child records can be defined for one parent record.
• A child record is linked to only one parent record.
• The relation is established through the lookup field on the child concept.
  
  

Usage examples:

• Company → Contacts
• Company → Sales
• Sale → Activity Records
  
  

Form and list behaviors:

• In the parent record's form, related records can be displayed as related record list.
• In related lists:
• List selection can be made
• Columns can be customized
• Filtering can be applied
  
  

Many-to-Many (N:N)

Many-to-Many relations enable two concepts to be linked mutually and multiply to each other.

In this relationship type:

• Both concepts can be linked to each other with multiple records
• The relation is managed through an intermediate relation table created by the system
• In this intermediate table, only the Id fields of the two concepts are stored
• Additional fields cannot be defined on the relation table
  
  

Meaning:

• Additional information such as role, date, description cannot be defined
• Only "which record is related to which record" information is stored

Purpose of use:

• Scenarios requiring pure relations
• Structural and systemic connections

Example usage scenarios:

• User – Roles
  Which user has which roles?
  Which role has which users?
• Team – Users
  Which team has which users?
  Which teams does a user belong to?

In such scenarios:

• Performance is priority
• Data structure is clear
• No additional information is needed