Skip to main content

27 posts tagged with "Entity-Data"

View All Tags

Entity-Data – Changed

The partial-properties endpoint is now unconditionally available to all callers. Request/response schema is unchanged.

Affected Endpoints​

  • POST /entitydataquery/api/v2/entity/drafts/partial-properties

Entity-Data – Added

New endpoint returning a page of draft entity/journey membership ({ EntityId, EntityDraftId }) per matching draft, for callers that need journey draft membership without the full draft payload. Same authorization/filtering rules as the existing search endpoint. Request gains an optional page options object (page size, pagination token, sort order); response is now a page of items plus a pagination token instead of a bare array. Omitting page options defaults to a page size of 100; page size accepts 1-500.

Affected Endpoints​

  • POST /entitydataquery/api/v2/drafts-in-scope/search-entity-drafts-light

Entity-Data – Changed

The maximum number of EntityIds accepted per request is raised from 10 to 100. Requests above the new limit are still rejected with a validation error. Response shape is unchanged.

Affected Endpoints​

  • POST /entitydataquery/api/v2/entity/drafts/names

Entity-Data – Added

New endpoint that returns a named subset of an entity draft's properties for up to 10 drafts in a single request. Each result carries the draft's id, type, and only the top-level property keys named in the request. Requested keys that don't exist on a draft are omitted, and drafts that don't exist or that the caller cannot access are omitted from the response.

Affected Endpoints​

  • POST /entitydataquery/api/v2/entity/drafts/partial-properties

Entity-Data – Fixed

GraphQL responses — including auth-denied ones — from both EntityData subgraph hosts now include the Platform security headers Strict-Transport-Security and Content-Security-Policy.

Affected Endpoints​

  • POST /graphql

Entity-Data – Fixed

Entity draft/entity update validation now honours Policy ExternalDataGroupProvider rules for data group fields when creating external adapter validation requests. Request/response schema is unchanged; affected command endpoints now correctly reject invalid data group rows returned by the external provider.

Affected Endpoints​

  • All entity draft/entity update command endpoints that trigger external data group validation (validation behaviour only — no schema change).

Entity-Data – Changed

Entity draft/entity update validation now sends data group fields to external adapter providers as grouped requests (one request per collection row per provider) instead of individual single-field requests. Request/response schema is unchanged; validation error messages returned to callers are unaffected.

Affected Endpoints​

  • All entity draft/entity update command endpoints that trigger external data group validation (validation behaviour only — no schema change).

Entity-Data – Added

New endpoint that returns the entity id, draft id (when applicable), type, display name, and aggregate version for each requested entity within a journey context. Uses the journey's draft when present, falling back to the verified entity record otherwise. Only accessible records are returned; inaccessible and forbidden records are silently omitted.

Affected Endpoints​

  • POST /entitydataquery/api/v2/entity/drafts/names

Entity-Data – Changed

The conflicts-exist check now persists a conflict-free result once a comparison finds no data conflicts, clearing the phantom conflict badge with no client-visible API change.

Affected Endpoints​

  • GET /entitydataquery/api/v1/entity/{entityId}/draft/{draftId}/conflicts-exist (internal behaviour change only)

Entity-Data – Added

Journey Level Data (JLD) property values are now surfaced in Advanced Reporting: entity draft properties (scalars, Data Groups, and custom properties) are projected into the reporting data store alongside regular entity draft data.

Affected Endpoints​

  • No endpoint change — internal reporting data enrichment only.