Transcript:
0:01 Welcome. Today I'm showing you how to
0:04 turbocharge your Dynamics 365 and Power
0:06 Platform deployments by automating
0:09 version control with North52.
0:12 In any complex project, business rules
0:15 change constantly. But relying on manual
0:18 tracking like spreadsheets or emails
0:20 creates accountability gaps. It's risky.
0:24 Our goal today is simple. Complete
0:26 traceability from business requirement
0:28 to deployment.
0:30 Here is the workflow we will use to
0:32 solve this. It starts with a request in
0:34 DevOps. You build the logic in N52.
0:38 Automation then commits it to source
0:40 control and deploys it to your later
0:42 environments.
0:44 Compare this to the old manual way of
0:46 exports and zip files. The modern way
0:50 gives you an automated audit trail,
0:52 one-click pipelines, and proof of every
0:54 single change.
0:56 Technically, this creates a clean
0:58 pipeline. Developers implement changes
1:01 in the development environment. Once
1:03 validated, the solution is exported to
1:06 Azure DevOps or source of truth. And
1:08 finally, build pipelines automatically
1:10 push the manage solution to test and
1:13 production.
1:15 Let's see this in action. We have under
1:19 our work items, work item 16, platinum
1:22 card eligibility, change the minimum
1:24 total assets acquired for customers that
1:27 are credit rating between 760 and 770.
1:30 We are to increase the total assets of
1:32 applicant from 200,000 to 300,000.
1:38 A functional consultant opens the North52
1:41 decision suite and updates the logic
1:43 directly. No complex coding, just a
1:46 simple configuration change. Behind the
1:48 scenes, this rule is saved as a web
1:50 resource inside the business rules
1:52 credit card solution. This is the
1:54 critical artifact that gets stored and
1:56 tracked in our DevOps repository.
1:59 We don't email zip files. We simply
2:02 trigger the pipeline
2:04 and tag it with work item 16. This tag
2:08 is the key. It links the business
2:10 request to the technical solution.
2:13 For our commit message, we give a
2:16 meaningful title. In this case, we're
2:18 going to use updated platinum card
2:21 eligibility min total assets 300,000.
2:29 The automation takes over. It exports
2:31 the solution, unpacks the files, and
2:34 commits them to source control. It is
2:36 creating a permanent source of truth for
2:38 your project.
2:41 This is the result. Complete audit
2:44 trail.
2:46 We can see exactly what changed. The
2:49 system highlights that the value moved
2:50 from 200,000 to 300,000. It is proof
2:54 that the system matches the requirement.
2:57 Here in the commit itself, we can see
3:01 not just the change made to the formula
3:03 PGK, we can also see the managed and
3:06 unmanaged solutions that were exported.
3:09 And if we click on details,
3:11 we can see who exported it, we can see
3:15 the work item linked below number 16.
3:18 And when we click on it, we can see that
3:20 the commit has been added to the
3:22 development section. This ensures
3:24 traceability for each and every change.
3:28 Deploying to test or production is just
3:30 as easy. We use the exact same manage
3:33 solution we just verified, ensuring
3:35 consistency across all environments with
3:37 zero manual steps.
3:45 To recap, we linked the business
3:47 requirement to the technical
3:48 deliverable. We eliminated manual errors
3:51 and we significantly increased
3:53 deployment speed. This is automated
3:56 application life cycle management for a
3:58 power platform. Safe, audit ready and
4:01 fast. Visit North52.com to download the
4:04 decision suite and try it for yourself.