Skip to main content

65 posts tagged with "Salesforce"

All SF articles

View All Tags

Salesforce Deployment Approvals: Separation of Duties for Your Release Process

· 5 min read
Kristina Zaretskaya
Salesforce Consultant

The fastest way to break production is to let everyone deploy to it. As a team grows, "anyone can push anything, anytime" stops being agility and starts being risk. What you want instead is separation of duties: people propose changes, and a smaller set of trusted reviewers sign them off.

mtdt.io's deployment approvals build that directly into the deploy flow — role-based, enforced at the moment of deploy, with extra protection for your most important orgs.

Salesforce Email Backup: Archive EmailMessages to Your Own Database & S3

· 4 min read
Aliaksandr Kliazovich
Salesforce Developer

Every email logged to a case, a contact, or a record lives in Salesforce as an EmailMessage. Those messages are some of the most compliance-sensitive data you hold — e-discovery, audits, disputes all turn on "what was actually sent." Yet they sit in Salesforce with finite storage and retention, and a standard backup doesn't single them out.

mtdt.io backs up your EmailMessages incrementally into your own database and S3 — a queryable email archive you control.

Salesforce File Backup and Archiving: Move Files to Your Own S3 and Free Salesforce Storage

· 11 min read
Kiryl Haradzenski
Salesforce Consultant

Salesforce Files — the attachments, uploaded documents, images, and signed PDFs stored as Content Versions — are often the largest and most expensive data in an org, and metadata or record backups don't copy them. mtdt.io copies them to an S3-compatible bucket you own, on demand or on a daily or weekly schedule. In archive mode it also deletes each file from Salesforce once the copy is verified, which frees Salesforce file storage, and can leave a record in Salesforce that points to the file in S3.

Pre-Deployment Checks: Catch What Breaks a Salesforce Deploy Before It Runs

· 6 min read
Kristina Zaretskaya
Salesforce Consultant

Most Salesforce deployment failures aren't mysterious. A flow references a field that isn't in the package. A profile change quietly removes access. There's no way to undo it if it goes wrong. These are predictable problems — and yet they usually surface the worst way: after you click Deploy, as a red error or a wave of "I can't see X" tickets.

What if you saw them before? That's what mtdt.io's pre-deployment checks do — run a set of analyzers against your target deployment and flag anything risky while you can still fix it cheaply.

Salesforce Static Code Analysis: Catch Apex Problems Before They Ship

· 5 min read
Aliaksandr Kliazovich
Salesforce Developer

Salesforce makes you hit 75% Apex test coverage to deploy to production. It's an easy target to game — and it proves only that your code runs, not that it's fast, safe, or maintainable. Coverage is not quality.

The issues that actually bite — a SOQL query inside a loop, an unhandled exception, a hardcoded ID, a sharing leak — sail straight through a coverage check and surface later as governor-limit errors, slow pages, or a security finding. Static analysis is how you catch them before they ship: mtdt.io runs the industry-standard analyzer PMD across your org's Apex, on demand or on a schedule, and reports every violation ranked by severity.

Outgrowing Salesforce DevOps Center: When (and How) to Move On

· 6 min read
Kiryl Haradzenski
Salesforce Consultant

Salesforce DevOps Center was a genuine leap forward. It dragged teams off change sets, put Git at the center of releases, and made source-driven development approachable for admins and devs alike — for free. If you're using it today, you made a good call.

But there's a pattern almost every growing team runs into: somewhere around the 6–12 month mark, DevOps Center starts to feel less like a platform and more like a ceiling. DevOps Center is a starting point, and outgrowing it is the normal arc for a maturing team.

One-Click Rollback: How to Undo a Bad Salesforce Deployment

· 4 min read
Kristina Zaretskaya
Salesforce Consultant

A deployment succeeds, everyone moves on — and an hour later a key flow is misfiring in production. Now what? With native Salesforce tooling, the honest answer is: you rebuild the previous state by hand, under pressure, while production misbehaves.

There's a better answer. Here's why Salesforce rollback is genuinely tricky, and how to turn it into a single click. mtdt.io does it by capturing a rollback point — a snapshot of the target org's metadata — right before a deployment runs; if the release goes wrong, you open the deployment and click Rollback to restore that pre-deployment state.

Salesforce DevOps in 2026: The Complete Stack

· 5 min read
Kiryl Haradzenski
Salesforce Consultant

A few years ago, "Salesforce DevOps" mostly meant "please stop using change sets." In 2026 it means a connected stack of version control, safe deployment, backup & recovery, quality, data, and governance — practices and tools that take a change from a developer's sandbox to production safely, repeatably, and with a way back if something breaks.

If you're assembling (or upgrading) that setup, this is the map: what each layer is for, and how they fit together.

A Salesforce Disaster Recovery Playbook: Backup, Rollback, and a Plan That Works

· 7 min read
Kiryl Haradzenski
Salesforce Consultant

Ask a Salesforce team what their disaster recovery plan is and you'll usually get one of two answers: "Salesforce handles that," or an uncomfortable silence. Both are a problem.

Salesforce is one of the most reliable platforms on earth — but "the platform is up" and "your data and configuration are recoverable" are two very different guarantees. This is a practical playbook for the second one: what to protect, how to think about it, and exactly what to do when something goes wrong.

Safe Field-Level Deployments: Ship Only What Changed

· 7 min read
Alina Hubaidullina
Salesforce Consultant

"Just deploy the one thing I changed" sounds simple. On Salesforce, it's one of the easiest ways to quietly break production.

The problem isn't deploying less — it's that Salesforce treats what you leave out as a decision. Here's why partial deployments are risky, when you actually need them, and how to do field-level deploys without the landmines.