This article explains how to use the North52 Decision Suite together with Azure DevOps to automate version control, achieve full traceability from business requirement to production deployment, and eliminate manual errors in your Dynamics 365 and Power Platform projects.
The Problem: Manual Tracking Creates Risk
In any complex Dynamics 365 or Power Platform project, business rules change constantly. Teams that rely on manual tracking methods — spreadsheets, emails, and exported zip files — quickly encounter accountability gaps. Without a clear audit trail, it becomes difficult to determine what changed, who changed it, and why. This approach is error-prone, slow, and risky.
The Goal: Complete Traceability
The objective is to establish complete traceability from the original business requirement through to the deployed solution. Every configuration change should be linked back to a specific work item, with a permanent record of what was modified and when.
The Automated Workflow
The modern workflow with North52 follows these steps:
- A request is created in Azure DevOps — A work item captures the business requirement, such as a change to eligibility criteria or a threshold update.
- The logic is updated in North52 — A functional consultant opens the North52 Decision Suite and makes the configuration change directly. No complex coding is required.
- Automation commits the change to source control — Behind the scenes, the updated rule is saved as a web resource inside the relevant solution. A pipeline is triggered that exports the solution, unpacks the files, and commits them to the Azure DevOps repository.
- Build pipelines deploy to later environments — The verified managed solution is automatically pushed to test and production environments.
Manual vs. Modern Comparison
The old manual approach involved exporting solutions, handling zip files, and hoping nothing was missed. The modern automated approach delivers an automated audit trail, one-click pipelines, and verifiable proof of every single change.
Step-by-Step Example
1. Review the Work Item
In Azure DevOps, a work item (for example, Work Item 16: "Platinum Card Eligibility") describes the change required. In this example, the requirement is to increase the minimum total assets for customers with a credit rating between 760 and 770 from 200,000 to 300,000.
2. Update the Business Rule in North52
A functional consultant opens the North52 Decision Suite and updates the relevant rule. This is a straightforward configuration change — no custom code is needed. The updated rule is saved as a web resource inside the business rules solution (e.g., the Credit Card solution).
3. Trigger the Pipeline
Rather than emailing zip files, you simply trigger the DevOps pipeline and tag the run with the relevant work item number (e.g., Work Item 16). This tag is the key link between the business request and the technical solution. A meaningful commit message is provided, such as: "Updated Platinum Card Eligibility min total assets 300,000."
4. Automation Takes Over
The pipeline automation performs the following actions:
- Exports the solution from the development environment
- Unpacks the solution files
- Commits the files to source control
This creates a permanent source of truth for your project.
5. Review the Audit Trail
Once the commit is complete, you have a full audit trail. The repository diff shows exactly what changed — for example, that the total assets value moved from 200,000 to 300,000. This serves as proof that the deployed system matches the business requirement.
Within the commit details, you can see:
- The specific changes made to the formula (the .pgk file)
- The managed and unmanaged solutions that were exported
- Who performed the export
- The linked work item (Work Item 16)
When you open the work item, the commit appears in the development section, ensuring full traceability for each and every change.
6. Deploy to Test and Production
Deploying to test or production uses the exact same managed solution that was just verified. This ensures consistency across all environments with zero manual steps.
Summary of Benefits
- Business requirement linked to technical deliverable — Every change is traceable back to a specific work item.
- Manual errors eliminated — No more reliance on zip files, spreadsheets, or email-based tracking.
- Deployment speed increased — One-click pipelines replace multi-step manual processes.
- Audit-ready — A complete, verifiable record of every change is maintained in source control.
This is automated Application Lifecycle Management (ALM) for the Power Platform — safe, audit-ready, and fast.