Learn
Practical, no-fluff answers to the Salesforce development problems we kept hitting ourselves - each one true whether or not you ever use OrgTide.
Fixing "fullName invalid at this location" in package.xmlWhy a <fullName> element breaks Metadata API deploys, what it actually does inside package.xml, and the manifest shape that always works.Read →The 75% Apex code coverage rule, explainedWhy Salesforce blocks production deploys under 75% test coverage, how coverage is actually calculated, and how to raise it with tests that are worth having.Read →Flow versions: how they work, and why you never overwrite the active oneHow Salesforce flow versioning actually behaves - activation, the 50-version limit, running interviews - and the deployment habit that keeps automation safe.Read →Custom metadata types vs. custom settings: which one, whenThe one fact that decides most cases - custom metadata records deploy with your code, custom settings values don't - plus the real exceptions where settings still win.Read →Why your roll-up summary field isn't available (and what to do about it)Roll-up summaries only work on the master side of a master-detail relationship. Why Salesforce enforces it, and the three real workarounds when all you have is a lookup.Read →Sandbox vs. Developer Edition org: which one do you actually need?They sound interchangeable and aren't - one is a copy of your production org, the other is a free blank org you own. How to pick, and why a 'Developer sandbox' is neither.Read →