LOAD ENTITY Action

[pauln]

So I have this Action to Load a ENTITY:Supplier which seems to work, but I cannot access or check the other Custom Data fields using {ENTITY DATA:x}

Rule:

So kendash said “the action is used to place an Entity into memory for further processing”? What can be done with Supplier after LOAD ENTITY as I would like to store some custom data with ACTION:Update Entity Data.

Is the problem because I am inside a Ticket?

[EDIT]
Ok - so CHANGE TICKET ENTITY is required and returns Custom Data - BUT it attaches to the Ticket. I guess I will need to unattached when I am done updating Custom Data Fields? Surely you must be able to access all Entity Fields outside of a Ticket…

[EDIT2]
Umm let me check this link out.

Loyality Card and Delivery ticket

Hmm. interesting. Basically you need to read a value from an entity and update another entity with that value. The problem you’re facing is entity related tags (for example {ENTITY DATA:X}) works with entities assigned to tickets but you need to read data from an entity that is not assigned to ticket. You can load an entity with Load Entity action and pass that entity to an automation command to read values but this is pretty complex. With V5 we’ll have {ENTITY CUSTOMDATA BY NAME:X} tag to read…

[EDIT 3]
Usage

@QMcKay

Instead, use the new V5 Tag called {ENTITY CUSTOMDATA BY NAME:<ET>.<EN>:<FN>}, for example:

{ENTITY CUSTOMDATA BY NAME:Employees.{ENTITY NAME}:Password}

Looks like if I am in Ticket then I MUST use “In Ticket Commands”.

Final Results if you are Interested

Load Entity Action

Change Ticket Entity Action

Change Ticket Entity Action using {ENTITY NAME:Supplier}

[Jesse]

Once you load an entity you do not need to specify entity type. When you load an entity these tags will work.

{ENTITY NAME} {ENTITY DATA:<Custom Field>} 

Once Entity is loaded you do not need to use {ENTITY NAME:X} or {ENTITY DATA:<Entity Type>:X}

The reason for specifying entity type is if your in a ticket working with multiple entities assigned.

Load Entity was designed to work outside of tickets which is the very reason we have the action.

[Jesse]

To update entity data you do not have to load an entity first all of the required parameters are inside the action.