Map Entity Attribute

1. Field Selection on the UI

• The user is presented with a field where they can select an entity.
• Then, the attributes defined in the system are listed.
• Even if multiple attributes are selected, the MapEntityAttribute action only works for a single attribute. Therefore, the action must be triggered separately for each selected attribute.

2. Action Definition

Add the following action to the ‘Add Attribute’ or ‘Match Fields’ button:

• + ADD ACTION > OnClick > EAV > Entity Attributes > MapEntityAttribute

The parameters are configured as follows:

• EntityId: Symbol Picker > Select Box / Dynamic Form
• AttributeId: Symbol Picker > Select Box
• SortOrder: Symbol Picker > Optional > Fixed / Numeric Input

3. Using the Action Result

• After the match is complete, a notification can be displayed to the user (Show Toast).
• The GetEntityAttributes action can be run for the relevant entity to display the new attributes.

In a CRM application, the user wants to add fields such as ‘Date of Birth’ and ‘Customer Notes’ to customer cards.

• The user selects the relevant customer entity.
• Selects one of the attributes defined in the system.
• When the ‘Add Field’ button is clicked, the MapEntityAttribute action is executed.
• The selected attribute is linked to the relevant entity.
• The Dynamic Form is recreated according to this new attribute.
• This process is repeated for each attribute.

‍

• Add Attribute One by One: The action works for only one attribute at a time. If multiple additions are desired, the MapEntityAttribute action must be triggered one by one with a loop after selection.
• Conditional SortOrder Assignment: The SortOrder value can be dynamically determined based on the attribute type.
• Preview: A form preview can be presented to the user before the attribute is added.

Technical Risks

• Invalid IDs: If EntityId or AttributeId is missing or incorrect, the mapping will fail.
• Duplicate Mappings: If the same attribute has already been mapped to the same entity, the system may throw a conflict or ignore the mapping.
• Order Conflict: If the same SortOrder is assigned to different attributes, unexpected sorting errors may occur in the UI.

The MapEntityAttribute action is one of the fundamental building blocks of Kuika's EAV-based architecture, enabling flexible field definitions for entities. It is ideal for creating customisable data models and developing user-specific forms.