2026-02-26

by Noémie Lagarde

If you’d told me a year ago that I’d have such a complicated relationship with a Salesforce feature, I’d have laughed. But after nearly 12 months of working with Omnistudio Document Generation (DocGen), “complicated” is the perfect word.

This post is for technical admins who are considering DocGen for their Salesforce org. I’ll share the highs, the lows, and the lessons that will save you time (and sanity).

Why DocGen Looks Like a Dream

Let’s start with the positives, because there are plenty.

Omnistudio DocGen is a native powerhouse.

The promise is compelling: a Salesforce-native solution for complex document generation and conversion at scale. No third-party apps, no messy integrations.

Highlights:

• Batch processing that respects Salesforce limits: Hit your hourly document generation cap? DocGen queues the rest automatically and processes them later, with clear success/failure notifications.
• Template flexibility: Supports Word and PowerPoint templates, merges data from multiple sources, and integrates with Omnistudio Data Mappers.
• Low-code options: Recent updates allow mass creation of document processes with minimal coding.
• For large-scale operations, this is a game-changer, at least on paper.

Where the Frustration Begins

Here’s the reality: DocGen is powerful, but it’s not frictionless.

• Hidden objects: Need to query Document Generation Process records? There’s no standard tab, and you’ll be living in Developer Console.
• Odd dependencies: Uploading a Vlocity logo in Salesforce Classic just to avoid errors in Omnistudio? Yes, that’s a thing.
• Features that tease: “Merge PDF” sounds great…until you hit a cryptic error with zero documentation.
• You’ll often wonder: Is this broken, or am I missing a secret permission?

The Workaround Wilderness

What feels simple elsewhere in Salesforce often requires creative hacks in DocGen.

For example

• Batch component UI: You can’t edit its record page or add custom buttons. Our workaround? Build a custom batch object as a front-end. It works, but reinventing the wheel for basic UI flexibility is frustrating.
• Triggering batch automatically: We wanted to start a batch from Flow or Apex to save users a click. After hours of searching, the answer was simple: update the batch record’s status to “In Progress.” Obvious once you know, but undocumented.

Trust Issues

The most unnerving moment? Seeing a Document Generation Process marked “Success,” only to download an empty document. Merge fields? Gone. Lesson learned: Don’t trust the status field. Always verify the output manually.

So… Is It Worth It?

Yes—with a giant asterisk.

If you need to generate thousands of personalised documents and want to stay native, DocGen is a strong contender. But:

• Expect a steep learning curve.
• Prepare for sparse documentation.
• Be ready to build workarounds for basic functionality.

My Top 5 Tips for Surviving DocGen

1. Pack your patience.
2. Turn on debug mode early.
3. Document your workarounds.
4. Verify outputs manually and verify “Success” messages.
5. Lean on the community. Forums and blogs often have answers Salesforce docs don’t.

Final Thoughts

DocGen will test your problem-solving skills, but it can deliver immense value once you learn its quirks. If you’re considering it, go in with eyes open and a willingness to get creative.

Thinking about implementing DocGen?

Before you dive in, weigh the trade-offs. It’s powerful, but patience and persistence are part of the package.

If you’re evaluating DocGen for your Salesforce org and want practical insights or implementation strategies, let’s connect. I’d love to hear your journey.