Custom visuals - pdf export

Hi analyst85​,

One workaround that keeps everything internal: rebuild the visuals on top of a visual that is already certified and acts as a rendering engine, such as Deneb (Vega / Vega-Lite). Your design lives in the JSON spec inside your report, so nothing has to be published to AppSource, and because the host visual is certified it can render in PDF / PowerPoint export.

A minimal Deneb (Vega-Lite) spec to show the idea:

{
  "data": { "name": "dataset" },
  "mark": { "type": "bar", "tooltip": true },
  "encoding": {
    "y": { "field": "Region", "type": "nominal", "sort": "-x" },
    "x": { "field": "Sales", "type": "quantitative" },
    "color": {
      "condition": { "test": "datum['Sales'] < 0", "value": "#D62728" },
      "value": "#1F77B4"
    }
  }
}

Trade-offs to weigh: your team needs to be comfortable with Vega-Lite, very interactive SDK features may not translate one-to-one, and you should check export output for each visual since complex specs and large datasets can still behave differently in export. Also confirm your tenant allows Deneb (admins sometimes restrict AppSource visuals).

If a visual cannot be rebuilt that way, the other option is a "print" page that swaps it for core visuals (table, matrix, bar) only for the exported version, with bookmarks or a separate page used by the subscription / export.

So my overall approach would be:

List which org visuals must appear in PDF
-> Rebuild those in Deneb (certified host, spec stays in the report)
-> Test export of each page
-> Anything that cannot be rebuilt: export-only page with core visuals

AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.