← All entries

Copying tiles between journey locations (Customer Insights – Journeys)

Praxisis D365 Wiki · Public reference · Client-specific details redacted

Source: Claude.ai chat (original: copying-tiles-between-journey-locations__1e3339bc.md) Added: 2026-10-02

Summary

  • The real-time journey designer has no copy/paste, duplicate, or drag-to-reposition for individual tiles. Tiles only get created at a + node and the canvas auto-lays out.
  • To relocate a tile: rebuild it at the target + and delete the original.
  • Journey-level copy IS supported (via "Create a copy" on the journey record).

Key takeaways

  • Branch consolidation workaround: if the reason to copy a tile is the same send appearing on multiple branches, use the multi-branch attribute tile with a merge back to a common path.
  • Journey Creation Agent (preview, 1.1.65002.153+) can scaffold a restructured journey from a text description — faster than manual rebuilding for heavily-nested journeys.
  • The journey definition lives as JSON on the msdynmkt_journey record and is technically patchable — but Microsoft treats this shape as internal, it shifts between versions, and malformed definitions fail publish validation unpredictably. Not production-safe.

Learnings / how to apply

  • When scoping a CIJ migration, treat tile-level restructuring as a rebuild activity, not a copy — budget time accordingly.
  • Watch 2026 Wave 2 release plan: tile copy is a long-standing ideas-portal request; could land any wave.

Need this applied to your own tenant?

Praxisis Sustain Self-Serve builds a private AI Wiki trained on your documents and tickets, with free Tier-2 support when the AI cannot answer. Book a 30-min overview.