Update Entities v Save Entities?

Unknown

Update Entities v Save Entities?

Unknown

Can someone please explain the use of Update Entities and Save Entities as flow steps.

Unknown

Update should allow you to update an existing record with whatever new property value you declare, where the Save step allows you to pass in the entire object for the structure you want to create / save.

Your use case will determine which one of these steps will be necessary for your flow

Unknown

Adding on this, what can be are the different use cases for Save Entities versus Batch Insert Entities? I am taking in data from an Excel upload then saving the data in its database structure (Entity).

Unknown

Hello,

[color=rgb(29, 28, 29)][font=Slack-Lato, Slack-Fractions, appleLogo, sans-serif]A Save Entity step creates an object in the table, and if an object already exists, it is updated.[/font][/color]
[color=rgb(29, 28, 29)][font=Slack-Lato, Slack-Fractions, appleLogo, sans-serif]Batch Insert Step involves importing a list of objects and creating/saving them in the Decisions table. It does not update any existing objects.
[/font][/color][color=rgb(29, 28, 29)][font=Slack-Lato, Slack-Fractions, appleLogo, sans-serif]In your use-case, I think by using the CSV to Object mapping step followed by the Batch Insert step, you can populate the table with data from the excel file.
[/font][/color]
Regards
Osman Zama

Unknown

thanks osman for the context.