Top
Top
LibraryEASYProcess Reference ManualProcessesServicesEntityWorkshopUpdate

Update Overview

Update is used to update the property values of existing entity objects records. Update works similar to a sql update statement. The update service will update an entity object record and the corresponding sql table record.


Update Use Example
Workshop:EntityWorkshop
Service:Update
Inputs
EntityIdThis is where you enter the EntityId of the entity object record you would like to update. This acts as the update key.

EntityTypeThis is where you enter the entity type of the entity object record you would like to update. The recommended values will list all possible entity types. The Entity Types correspond to SQL table name.

PropertiesThis is the container node that contains all the property nodes. It does not access any input, but you can Right-Click to add new Properties (Property #0, Property #1, etc.). Each Property below this node is added to the created entity object.

PropertyThe property is a container node which accepts no input, but represents a single entity object you are adding.

NameThis is the name of a property that you would like to update. The name must correspond to an existing property of the entity (column in the table).

ValueThis is the value you would like to assign to the property.

CreateIfNotExistsIf this is set to true and there is no entity object record matching the EntityId and EntityType entered into the update, the service will create a record with the EntityId, EntityType, and properties entered.

AutoLoad

Outputs
Entity/EntityIdThis is the EntityId of the entity object record that was updated.
Entity/EntityIdsThis is the EntityId of the enityt object record that was updated.
Entity/EntityTypeThis is the Entity Type of the entity object record that was updated.
Entity/Properties/PropertyNameThese are the properties and their values of the entity object record that was updated. This will list all the properties that exist for the entity, not just the ones that you passed in a value for.

Update Use Example

In this example we are going to be looking at the Save Shopping Cart Webpart. This webpart allows a user to save their shopping cart so they can access it later at their leisure. Below you can see that this webpart consists of a textbox and a Save button. The save button process contains the update service that we are going to be analyzing.

In this process, we first retrieve the CartId of the cart that we are going to save. Once we have the CartId, we run the Update service and update the ShoppingCartHeader entity object record. The EntityId and EntityType act as a key here so we enter the CartId for the EntityId and we enter ShoppingCartHeader for the EntityType. The entity properties that we want to update are Nickname and UserId, so use the Nickname that was entered and the UserId of the current user to update those values.

     

Below is the log data for the save cart button process. Notice how all the entity properties are returned even though just one property was updated.

The Property Names correspond to columns that exist in the table tied to the entity. The property name must already exist as a column for the table/property for the entity. This is case sensitive. This means that if you make a database change to add a column, but do not sync the EASYProcess entity, the property will not exist yet and the action will be performed against the record, but it will occur as if the new column was not in the update statement ran.

     

Once the update service runs, the save cart webpart will close and the parent page will reload. The user can then navigate to the saved carts page and view that the cart was saved. If they log out or their session ends, they are able to reload the saved cart.


Powered by EASYProcess (© 2019 K-Rise Systems, Inc).