Skip to main content

DupliCat Enhanced Overrides

Last updated: February 23, 2026 (America/Los_Angeles)

Applies to version/build: DupliCat v0.1.6 (released February 16, 2026)

Enhanced overrides are advanced template controls that adjust cloned property values in predictable ways.

They are configured per object-type template and applied during clone execution.

Included controls

ControlWhat it doesObject coverage
Date shiftShifts selected date fields by N days (+ forward, - backward).Deals, contacts, companies, tickets
Owner ruleSets owner behavior to keep, clear, or specific owner ID.Deals, contacts, companies, tickets
Pipeline mapRemaps source pipeline values to target pipeline values.Deals and tickets
Stage mapRemaps source stage values to target stage values.Deals and tickets

Configuration notes

  • Date fields are configured as property internal names (for example closedate).
  • Owner rules use a configurable owner property (default is hubspot_owner_id).
  • Pipeline/stage maps are key/value mappings (from -> to).
  • For object types without pipeline support (contacts/companies), pipeline/stage maps are ignored.

Precedence with templates and runtime inputs

Clone behavior is resolved in this order:

  1. System defaults
  2. Portal defaults
  3. Selected template config (including enhanced overrides)
  4. Per-run inputs (card selections or workflow inputs)
  5. Direct field-value overrides

Direct property overrides are applied after enhanced overrides. If both target the same property, direct overrides win.

Practical examples

  • Shift close dates forward by 14 days in renewal-deal templates.
  • Clear owner on clone to route reassignment through existing queue rules.
  • Map legacy pipeline/stage IDs to new pipeline/stage IDs during phased migrations.

Boundaries

  • Enhanced overrides modify clone property payloads only.
  • They do not add support for attachments, and they do not change which card/workflow surfaces are currently published for quotes, activity objects, or custom objects.
  • Pipeline/stage mapping is intentionally limited to deals and tickets in this release.

Troubleshooting

  • Date shift warning: verify field type and property internal name spelling.
  • Owner rule specific with no owner ID: clone keeps source owner and returns a warning.
  • Pipeline/stage mapping not applied: verify object type is deals/tickets and mapping keys match source values exactly.
  • Unexpected value outcome: verify template selection/default resolution and any per-run direct overrides.

Support intake checklist

If an override behaves unexpectedly, contact support with:

  • Portal ID
  • Object type + source record URL
  • Template name
  • The specific override rule (date shift / owner / pipeline map / stage map)
  • Expected outcome vs actual outcome
  • Timestamp with timezone