You can save any entity record as another type of record. This enables you to track companies and individuals that have multiple relationships with your company. For example, a vendor might also be a customer or a partner. This capability is available on customer, partner, vendor, and other name records. To save a record as… Continue reading Records as Multiple Types
Tag: Entity Records
Entity name not fully fetched using lookupFields
The “entityid” field of a customer record displays customer id and name. When fetching the “entityid” field value from a record using search.lookupFields, only the customer id is returned without the customer’s name. search.lookupFields is optimized for quick lookup of field values and generally returns a simplified version of the data. “entityid” concatenates multiple pieces… Continue reading Entity name not fully fetched using lookupFields
Assign Class Department Location fields to Customer and Other Entity Records
Currently there are no Class, Department, and Location to Entity Records. A possible alternate solution is to assign a Custom Segment to the Entity and source to new transactions. Solution 1. Navigate to Lists > Relationships > Customers 2. Customer line: Click Edit 3. Hover over Customize 4. Click New Field 4. Label: Enter Label 5. Type: Select List/Record 6. List/Record: Select Department (or Class/Location) 7. Store Value:Enter Checkmark 8. Click Applies To 9. Enter Checkmark for Entity records where the… Continue reading Assign Class Department Location fields to Customer and Other Entity Records
Allocating Subsidiaries and Currencies
Jira Code: TRS:575 We can allocate all the subsidiaries and currencies to a customer or vendor after get created. This will ensure that all the active subsidiaries (children) and currency will allocate to all of the customers and vendors.This is achieved using a User Event script which will trigger after the record creation. Basically the… Continue reading Allocating Subsidiaries and Currencies