Save Record

1. Log in to the Kuika platform and open the project you are working on.
2. Go to the UI Design module and open the Properties panel on the right panel.

3. From the + ADD ACTION menu, add the Managed DB > Save Record action according to the trigger event you want (Initial Actions, OnClick, OnBlur, etc.).

Save Record Action Modes

There are three different modes for the Save Record action:

1. Smart Mode:
   
   • If the Id sent with the action matches an Id in the table, the UPDATE operation is executed; otherwise, the INSERT operation is executed.
   • Example: If there is an Id belonging to the user record in the database, the data is updated. Otherwise, a new user record is added.
2. Insert Mode:
   
   • If there is no record matching the given Id in the table, a new record is created. However, if there is a record matching the given Id, an error is returned.
   • Example: If there is a record with the same Id in the system, the new record is not added and an error message is displayed.
3. Update Mode:
   
   • If there is a record that matches the Id given in the table, the record is updated. If there is no matching record, no action is taken.
   • Example: The record in the database is updated with the specified Id. If there is no record with the Id, no action is taken.

Table Selection and Conditions in the Save Record Action

1. Table Selection:
   
   • “Select Table” field, select the table to be used for the record operation.
   • “Select Table” field, select the table to be used for the record operation. When the table is selected, a Multi Select field titled “Select Columns” is displayed. This field lists the columns belonging to the selected table. The columns are defined as action parameters and determine the functionality of the action.
2. Adding Conditions:
   
   • If the “Update” mode is selected for the action, a field representing the table entries to be updated appears below the action.
   • Conditions can be linked together using the AND structure. Alternatively, an OR condition group can be created so that the action is executed when any condition is met.
   • Example: If the username and email conditions are met, the record in the database is updated.

1. User Form: The user fills out a form containing their username, email, and phone number.
2. Save Record Action: When the user submits the form, the Save Record action is triggered and the form data is saved to the database.
   
   • If the form data belongs to an existing user, the system updates the data in Update mode.
   • If the user is new, the system adds a new record in Insert mode.

1. Dynamic Data: By making the Id parameter dynamic, the record can be updated with the ID taken from the form data.
2. Table-Linked Parameters: Action parameters can be dynamically matched with table-linked columns, allowing data to be added to different tables with the same action.
3. Delete and Update Options: Users can perform both delete and update operations at the same time. This allows for more efficient management of operations.

Technical Risks

• Incorrect ID Selection: Make sure that the Id parameter is obtained correctly. An incorrect ID can result in data loss or incorrect operations.
• Data Conflicts: Conflicts may occur during Update operations. The same record should not be updated by two different operations.

Save Record action allows users to quickly save data to the database via forms or data entry screens. This action provides seamless integration with MSSQL and Oracle databases and simplifies data management for users. It optimizes database operations by providing effective data management in both web and mobile applications.