-
Notifications
You must be signed in to change notification settings - Fork 15
Tutorial 7
PhuocLe edited this page Aug 26, 2018
·
7 revisions
- Qualify lead don't create Opportunity, create Account and move to Account page after success qualified
- Finish Tutorial 1: Plugin
- Finish Tutorial 2: Unit Test Plugin
- Finish Tutorial 3: WebResource
- Finish Tutorial 4: Unit Test WebResource
- Finish Tutorial 5: Custom Workflow
- Finish Tutorial 6: WebApiClient
- Goto Dynamics 365, create a
Custom Action
thenActivated
with these information bellow
-
Process Name
:Ajax
-
Unique Name
:paz_Ajaz
-
Entity
:None (global)
-
Arguments
-
Name
:function
,Type
:String
,Required
:Required
,Direction
:Input
-
Name
:jsonInput
,Type
:String
,Required
:Optional
,Direction
:Input
-
Name
:jsonOutput
,Type
:String
,Required
:Required
,Direction
:Output
-
- Add
New Project
02. C# Custom Action Project
to solution.- A popup form
Add new Custom Action Project
opened - Click button
><
to create/select a Dynamics 365 connection - Keep the text box
Project Name
empty - Select
9.0.2.4
in theCrm Version
PL.DynamicsCrm.DevKit
get allMicrosoft.CrmSdk.CoreAssemblies
version fromNuGet
- Select
4.5.2
in the.Net version
- Click
OK
-
PL.DynamicsCrm.DevKit
created workflow project name:Paz.LuckeyMonkey.CustomAction
- A popup form
- Rebuild solution to restore
NuGet
packages - Add
New Item
04. C# Custom Action Class
toPaz.LuckeyMonkey.CustomAction
project- A popup form opened
- Click button
><
to create/select a Dynamics 365 connection - After connected
PL.DynamicsCrm.DevKit
loaded all entities and bind to dropdownMessage
- Select
paz_Ajax
- Click
OK
-
PL.DynamicsCrm.DevKit
created custom action class:PostNonepaz_AjaxSynchronous