Kuika's Unmap Entity Attribute action is used to remove the connection between attributes (properties) that were previously associated with an entity (entity). With this action, unwanted or unused fields (attributes) can be easily separated from an entity without being deleted.

This action is currently available in beta version and is still under development. It is recommended to test it carefully before using it in a production environment.

This action does not delete attribute data, it only breaks the relationship with the entity. The attribute can continue to be used in other entities.

Technical Features

Remove Attribute Link (EAV Panel): Unmap Entity Attribute action works with the following required parameters:
- EntityId (Guid - Required): The ID of the entity from which the attribute relationship will be removed. It can be obtained statically or dynamically via the Symbol Picker.
- AttributeId (Guid/List - Required): The attribute or list of attributes to be separated from the entity. It can be a single or multiple value.
Data Source Compatibility: All parameters can be obtained from the following sources via the Symbol Picker:
- Form Component
- Action Result
- Select Box / Multi Select
- Fixed (static value)
Web & Mobile Support: The Unmap Entity Attributes action works in both web and mobile applications.

Unmap Entity Attribute Action Application Steps

1. Listing Existing Attributes on the UI

The attributes associated with the entity are listed with the Get Entity Attributes action.
The user selects the attributes they want to remove.

2. Action Definition

The following action is added to the ‘Remove Field’ or ‘Delete Link’ button:
- + ADD ACTION > OnClick > EAV > Entity Attributes > Unmap Entity Attribute

The parameters are set as follows:

EntityId: Symbol Picker > Form Component / Select Box
AttributeId: Symbol Picker > Multi Select / Action Result

3. Using the Action Result

After the link is removed:
- A notification message is displayed to the user (Show Toast)
- The current attribute list is reloaded (Get Entity Attributes)
- The dynamic form is recreated or updated

Usage Scenario: Removing a Field from a Customer Card

In a CRM application, a user wants to remove the ‘Occupation’ field from a customer card that is no longer in use:

The user selects the entity of the customer type.
The linked attribute list is displayed.
When the ‘Occupation’ field is selected and the “Delete” button is clicked, the Unmap Entity Attributes action is executed.
The ‘Occupation’ attribute is only separated from that entity; it is not deleted from the system.

Unmap Entity Attribute Action Advanced Customisations

Bulk Removal with Multiple Selection: The user can remove multiple attributes at the same time.
Conditional Removal: Only certain roles or permissions can delete attribute links.
UI Automation: After the attribute is removed, it can be automatically re-rendered in the Dynamic Form or Table element.
Undo Feature: Optionally, removed attributes can be temporarily stored in memory to be re-linked.

Technical Risks

Invalid EntityId or AttributeId: The operation will fail if the parameters are incorrect or missing.
Unrelated Attribute: The system will not perform the operation if the selected attribute is not already associated with the entity.
Data Loss Perception: This operation does not delete data; however, the user may mistakenly believe that data has been lost. An informational message should be added.

The Unmap Entity Attribute action is a critical tool for simplifying the dynamic data model, removing unnecessary fields, and keeping form structures up to date in the Kuika platform. It can be used efficiently in applications that require user-specific form and field management.

‍