Skip to content
Build a Doc
Home Documentation Support
This documentation is currently in preview, therefore subject to change.

Merge PowerPoint Presentation

Merges a source PowerPoint presentation into a destination presentation and returns the resulting file.

Parameters

NameTypeRequiredDescription
Source DocumentFile contentYesPowerPoint file to insert (e.g. from a Get file content action in SharePoint or OneDrive).
Destination DocumentFile contentYesPowerPoint file to insert into.
Merge MethodStringYesDetermines how slides are merged. Options: Append, Slide Position.
Merge LocationIntegerNoRequired only if Merge Method is Slide Position. Specifies the position at which to insert.

Returns

NameTypeDescription
File contentString (base64‑encoded)The merged file’s binary content, base64 encoded. Ready for downstream actions (e.g., file creation or storage).

Troubleshooting

Click to expand common errors and fixes

Missing, Truncated or Invalid Input Document

Cause:
Source or destination payload is empty, truncated, or not a valid PowerPoint binary.

Fix:

  • Provide the full, valid .ppt / .pptx binary for both inputs.
  • Verify each file opens locally to confirm it is not corrupted.

Unsupported or Misspelt Merge Method

Cause:
Merge Method value is invalid or mistyped.

Fix:

  • Use exactly Append or Slide Position (case sensitive).
  • Correct typos and retry.

Slide Master / Theme Inconsistency After Merge

Cause:
Source and destination use different masters or conflicting theme elements - slides retain source styling or lose destination styling.

Fix:

  • Decide whether to preserve source formatting or adopt the destination master.
  • If destination styling is required, reapply the destination master or layout after merging, or normalise masters before the merge.

Duplicate Slide IDs, Custom Layouts or Name Collisions

Cause:
Internal IDs, custom layouts, or named resources collide between files, causing layout or content anomalies.

Fix:

  • Normalise custom layout names or remap conflicting resources prior to merging.
  • If possible, merge via append and reconcile layouts in a post-merge step.

Animations, Transitions or Embedded Media Broken or Lost

Cause:
Complex animations, transitions, or embedded media (audio, video, OLE) may not survive the merge intact.

Fix:

  • Test merging with slides that contain media or animations to confirm behaviour.
  • For critical media, re-embed or re-link media after the merge and verify playback.

Fonts or Rendering Differences on Target Systems

Cause:
Presentation uses fonts not available in the environment that renders the merged file.

Fix:

  • Embed or standardise fonts, or use common system fonts.
  • Test the merged file on intended viewers.

Cause:
Slide indices or internal link targets change when slides are inserted, invalidating links.

Fix:

  • Update internal hyperlinks or action targets to the new slide indices after the merge.
  • Use named anchors where possible.

Output Corrupted or Fails to Open

Cause:
Returned payload is truncated, has an encoding error, or the merge failed mid-write.

Fix:

  • Ensure returned base64 is complete and decodes successfully.
  • Reproduce with minimal presentations to determine whether truncation is consistent.

Performance, Timeouts or Resource Limits with Very Large Decks

Cause:
Extremely large presentations or many high-resolution assets cause processing limits or timeouts.

Fix:

  • Break merges into smaller batches.
  • Reduce image sizes or merge only required slides.
  • Test with representative samples to determine safe limits.

Conflicting Slide Numbering or Indexing After Append

Cause:
Appending changes slide numbering expectations downstream.

Fix:

  • Recalculate slide numbers after the merge.
  • Update any external references or automation that relies on fixed indices.

Generic Runtime or Transient Failure

Cause:
Malformed inputs, intermittent engine error, or unexpected internal state.

Fix:

  • Reproduce with minimal source and destination files and a single merge operation.
  • Validate inputs and retry to rule out transient issues.

Quick Checklist

  • Source Document and Destination Document are full valid PowerPoint binaries (not paths or URLs).
  • Merge Method is Append or Slide Position and spelt exactly.
  • Decide master or theme behaviour - expect source formatting to come with inserted slides unless you reapply the destination master.
  • Verify handling of animations, media, speaker notes and comments with a small test merge.
  • Check fonts and embedded resources on intended viewer platforms.
  • For large decks, merge in batches and reduce asset sizes if you hit timeouts.
  • If output is corrupted, reproduce with minimal (redacted) sample files and the exact merge parameters - those inputs are required to isolate the issue.