Why We Used a Console App to Update 1.3 Million Records (And When You Should Too)
When your update count hits seven digits, the question stops being “can we do this?” and becomes “what’s the safest way to do this once?” This article explains why a console app using the Dataverse SDK is often the most controlled option for high-volume updates—especially when you need deterministic mapping logic, safe reruns, batching/throttling control, and the ability to update inactive records—plus a practical “test small first” pattern and validation steps to prove it worked.