Transcript:
0:02 Sometimes the standard forms and
0:04 dialogues in Dynamics 365 only get you
0:07 so far.
0:08 You can do some customization, but when
0:11 your business process needs something
0:12 more tailored, more fields, conditional
0:14 logic, or a completely different
0:16 workflow, you need another approach.
0:19 Today, we're looking at how North52 lets
0:22 you build fully custom dialog forms for
0:24 virtually any scenario. I'm joined by
0:26 our Norfick 2 expert, Bruce, to walk us
0:28 through this. So, what are we looking at
0:31 today?
0:36 We're using the close opportunity
0:37 process as our example, but this pattern
0:39 applies to lots of scenarios, approvals,
0:42 data capture workflows, bulk operations,
0:45 really anywhere you need a custom
0:47 dialogue with close opportunity.
0:49 Specifically, Dynamics 365 does allow
0:52 some customizations of the form. But
0:54 let's say your business needs more.
0:56 Maybe you want conditional logic where
0:57 selecting lost immediately shows a lost
1:00 reason field and locks the revenue to
1:02 zero. Or you want to enforce specific
1:04 validation rules. That's where custom
1:06 dialogues come in.
1:08 >> So this isn't just about opportunity.
1:11 It's a pattern that can be reused.
1:13 >> Exactly. Once you understand how to
1:15 build a custom dialogue with North52,
1:17 you can apply it anywhere. We're just
1:20 using close opportunity as a practical
1:22 example to demonstrate this technique.
1:24 >> Okay, great. Let's take a look.
1:30 Here's what we've built. When a user
1:32 selects an opportunity and clicks our
1:34 custom ribbon button, this dialogue
1:36 opens. They choose one or loss. If they
1:39 pick one, they enter the actual revenue
1:40 and close date. If they pick lost, the
1:43 revenue field lops to zero and a loss
1:45 reason field appears. So the form is
1:48 reacting in real playing base value user
1:50 input.
1:51 >> Exactly. And that's all handled by an
1:53 052 client side formula. No JavaScript
1:56 required. And when they click close
1:58 opportunity, which is a North52 quick
2:00 button, another formula creates the
2:02 opportunity close record and closes the
2:04 dial.
2:09 Let's peek under the hood. What's making
2:11 this work? There are a few components.
2:14 First, we have a custom dynamics form.
2:16 just a standard main form but we've
2:18 added some N52 JavaScript events to
2:20 make it behave like a dialogue. It hides
2:23 the chrome disables autosave things like
2:26 that.
2:28 Then we have two formulas. The first one
2:30 controls a UI what fields are required
2:33 what's visible default values. It uses a
2:36 decision table which is like a
2:38 spreadsheet where you define conditions
2:39 and actions.
2:42 So here if the user selects lost we show
2:44 the loss reason field make it required
2:47 and disable the revenue field all
2:50 defined vigilant no code. The second
2:53 formula handles the button click. It
2:55 reads the form values and calls either
2:58 the win opportunity or lose opportunity
3:00 North52 functions to create the close
3:02 record. Then it closes the dialogue
3:05 >> and the ribbon button that opens all
3:07 this
3:08 >> that's using North52 quick ribbon
3:10 functionality. You configure it right in
3:12 the app design. Point it at your custom
3:14 form, pass in the record ID, and done.
3:22 >> Now, I know there's a related example
3:24 that takes it even further using bulk
3:27 update. Yes, same concept, but instead
3:31 of closing one opportunity, you're
3:32 updating multiple records at once. In
3:35 this example, a user selects several
3:37 opportunities from the grid, clicks a
3:39 button, and gets a dialogue where they
3:41 can update the rating, reset the sales
3:43 team, or assign new team members using a
3:46 subre.
3:47 When they click update, a formula loops
3:49 through each selected record, makes the
3:52 changes, and then displays a summary
3:54 right from the dial. Which records were
3:56 updated, which users were added. So, you
3:59 get that feedback without leaving the
4:00 screen.
4:01 >> Exactly. It's a pattern you could adapt
4:03 for any bulk operation.
4:05 >> All right, let's recap. If you need to
4:08 customize dialogues in Dynamics 365 or
4:11 data versse model driven apps, whether
4:13 it's replacing lockdown screens like
4:15 close opportunity or building bulk
4:17 update tools, North52 gives you a way to
4:21 do it with standard forms and visual
4:23 formulas. And because it's all
4:25 configuration, not code, it's easier to
4:27 maintain and update as your business
4:28 changes. If you want to see how this
4:31 could work for your specific
4:32 requirements, reach out to North52 for a
4:35 demo. They can walk you through the
4:36 setup and help you figure out the best
4:38 approach for your scenario. Thanks for
4:41 watching. See you in the next one.