APL Scheduler

Integrator Studio: connections and mappings

What you will learn

Exchange data with stable keys, relationships and change control.

Worked example

Test article input keyed by code. Repeat the same record and check idempotent update without duplicates before scheduling.

From data to result

  1. 1Connection
  2. 2Keys
  3. 3Mapping
  4. 4Execution

Integrator exchanges data through connections, operations and mappings. Integration-owned fields may become read-only elsewhere.

  1. 1
    Check licence and permissions, create a connection and follow the provider’s specification. Store credentials only in secure app fields, never public screenshots.
  2. 2
    Choose direction, entity and operation. Map external/APL fields, defaults and transformations. Check dates and time zones, including fractions and offsets.
  3. 3
    If the service uses `{keys}`, configure its required key fields. Do not invent quotes or duplicate the resource in the URL. DELETE is not supported in Integrator Studio.
  4. 4
    Test controlled data and inspect request, response, execution and errors. Confirm affected records before enabling schedules or production triggers.

Technical reference

Illustrative example: adapt values to the installed contract and use a secret store.

ERP · JSON→Integrator Studio→APL Scheduler
GET /articles
{ "items": [{ "code": "ART-DEMO", "name": "Demo" }] }

items[] → Material
code    → code
name    → name

PATCH /resource/({keys})
{keys}: company={company},id={order.number}

Before you finish

Check flat/grouped entity, response root, header/panel keys, fields, units, time zone, pagination and run log.

Common questions

An option is missing or I cannot edit

Check active company, licence, permissions and integration-managed fields. Do not use a direct URL to bypass restrictions.

I cannot find records

Clear filters and check page, dates and company. There may be no accessible data; do not create duplicates to test.

I saved but cannot see the expected effect

Reopen the record and verify. Saving data does not publish a required simulation. Check whether the first write succeeded before repeating it.

Related guides