Limitations and restrictions of Experience Edge for XM

Abstract

The limitations for working with Experience Edge for XM.

Experience Edge for Experience Manager (XM) has the following limitations and restrictions:

  • The Experience Edge connector supports only one search provider: Solr.

  • The Experience Edge for XM Connector publishes a static snapshot of the Layout Service output for an item at the time of publishing. This means that:

    • Experience Edge for XM does not execute or support Sitecore personalization rules or content testing.

    • Experience Edge for XM does not support contextual/dynamic output from the Layout Service based on user, query strings, and so on.

    • If you make a change to a rendering configuration or Layout Service extension that affects the output of the Layout Service, you must republish the affected items.

  • Sitecore tracking/analytics do not reflect Experience Edge API calls.

  • Experience Edge for XM does not enforce security constraints on Sitecore content. You must apply publishing restrictions to avoid publishing content that you do not want to be publicly accessible.

  • Sitecore language fallback rules are applied at publish time and can only be enabled/disabled on an instance and not on individual sites. If you make a change to language fallback configuration, you must republish the affected items.

  • The value an item inherits through clones and standard values is resolved at publish time. A change to a clone source or standard value requires republishing of dependent items.

  • Experience Edge for XM only utilizes a single content scope for the whole tenant. Security tokens, query cache clearing, and webhooks cannot be limited by site.

  • The maximum size for Media items is 50MB.

  • The Experience Edge Connector is not compatible with Azure Search or the Sitecore Publishing Service.

  • The mirrored schema might return inconsistent results when filtering or sorting by item text fields, due to differing tokenization.

  • The Experience Edge Media CDN supports the following parameters for media URLs:

    Query parameter

    Description

    w

    The width of the image.

    h

    The height of the image.

    mw

    The maximum width of the image.

    mh

    The maximum height of the image.

  • Due to a known issue in the Experience Edge GraphQL schema, you must not mix literal and variable notation in your query input. If you use any variables in your GraphQL query, you must replace all literals with variables.

    Correct

    Incorrect

    query MyQuery($hasLayout: String!, $parent: String!) {
      search(
        where: {
          AND: [
            { name: "_hasLayout", value: $hasLayout }
            { name: "_parent", value: $parent }
          ]
        }
      ) {
        total
      }
    }
    query MyQuery($parent: String!) {
      search(
        where: {
          AND: [
            { name: "_hasLayout", value: "true" }
            { name: "_parent", value: $parent }
          ]
        }
      ) {
        total
      }
    }