The Logical Entity Data/Entity to Entity Service (E2E LEDS) lets you copy or update records across logical entities in one API request, using field mappings and optional transformation logic. It’s designed for bulk operations where you would otherwise have to export data from Zilliant, transform it in your own code or tools, and write it back record by record.
With E2E LEDS, you describe the operation (source, target, mappings, filters, transformations) and Zilliant applies it server-side.
What you can do with E2E LEDS
Use E2E LEDS to:
Copy data from one entity to another
Update existing records using mapped fields and computed values
Apply transformations during the data copy or update, for example, adjust price fields as you move them
Limit the scope of the operation with filters, without fetching data client-side
Common scenarios
You can use E2E LEDS for bulk operations such as:
Price adjustments, for example, to increase list prices by 10% for a product line
Mass reclassification, for example, to update segment/category fields based on rules
Entity-to-entity synchronization, for example, to copy approved values into a downstream entity
Copy-and-modify workflows, for example, to copy a baseline dataset and apply transformations in one step
When to use E2E LEDS vs LEDS
Both services can update data, but they solve different problems.
Use E2E LEDS when you want to:
Update many records using computed values, for example,
ListPrice * 1.10Copy data between different entities
Apply transformations during the data copy or update
Limit changes using a filter without fetching data client-side
Use LEDS PATCH when you:
Already know the final values per record
Want to update records one by one