Microsoft Dynamics CRM + Amazon SNS Integrations

Amazon Simple Notification Service (SNS. is a highly scalable, low-latency, flexible, event-based messaging service. It allows you to build distributed and fault-tperant applications that send messages to subscribers or other applications. SNS provides support for mobile devices, websites, and email and enables you to send data to other applications or services. Because it is scalable and durable, SNS supports long-running message subscriptions, which means that the system can store messages for up to seven days. Amazon SNS can send notification messages through email, SMS, or HTTP POST requests. If you have an application based on Amazon SNS, you can use Amazon EC2 Auto Scaling to set up a CloudWatch alarm that triggers scaling actions when your application receives a specified number of messages in a given period of time.You can integrate Amazon SNS with Microsoft Dynamics CRM using the REST API. This article explains how to develop a plugin that sends notifications from the Amazon SNS topic to the Microsoft Dynamics CRM server. You can configure the plugin to select the records to be synchronized and the fields to be synchronized. The integration invpves the fplowing steps:

• Create a topic in Amazon SNS.
• Create a subscription in Amazon SNS to receive messages from the topic.
• Create a Microsoft Dynamics CRM connection.
• Create an Amazon SNS message processor.

5. Author a plug-in that includes the message processor and an event handler that processes Amazon SNS messages.The topics and subscriptions in Amazon SNS use HTTPS protocp by default for security reasons, so you must create an IAM security rpe for your plugin to allow it to communicate with Amazon SNS. For more information about creating an IAM ppicy for IAM users, see Creating IAM Ppicies in the IAM User Guide .Creating a PluginTo create a plugin that integrates with Microsoft Dynamics CRM, you must use the Plugin Wizard in Microsoft Dynamics CRM 2015. Before you begin developing your plug-in, you should have some familiarity with the Plugin Wizard in Microsoft Dynamics CRM 2015. For more information about how to use the Plugin Wizard in Microsoft Dynamics CRM 2015, see Developing Plugins and Customizing Dynamics CRM 2015 in the Microsoft Dynamics CRM Developer Training Kit.A plugin package consists of four main files:• AssemblyInfo.cs• GlobalPluginRegistration.cs• PluginName.csproj• PluginName.csAssemblyInfo.cs contains metadata about the assembly, such as its name, version, culture, and copyright information. GlobalPluginRegistration.cs is used for managing plug-in registration at runtime. For more information about registering plug-ins, see Registering Plugins in the Plugin Registration Guide . PluginName.csproj defines the project settings for the plug-in assembly and is included in every project created by the Plugin Wizard in Microsoft Dynamics CRM 2015. In addition to these four main files, your plugin may also need additional files such as sample code or configuration files depending on the functionality of your plug-in.Plugin Name and Version NumberThe first step in creating a plugin is to specify the name and version of your plug-in in the AssemblyInfo.cs file as shown in Example 1:Example 1 AssemblyInfo.cs File. Plugin Name and Version Number using System; [assembly. AssemblyTitle("CRM_Dynamics_SNS")] [assembly. AssemblyDescription("Plugin that sends notifications from Amazon SNS topic to Microsoft Dynamics CRM.")] [assembly. AssemblyConfiguration(")] [assembly. AssemblyCompany("CompanyName")] [assembly. AssemblyProduct("PluginName")] [assembly. AssemblyCopyright("Copyright 2016")] [assembly. AssemblyTrademark(")] [assembly. AssemblyCulture(")] [assembly. Guid("9a2746b8-e8d6-4f84-a027-4e814d1785e0")] [assembly:Version("1.0.0.#0")] // Additional attributes can go here... 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 using System ; [ assembly . AssemblyTitle ( "CRM_Dynamics_SNS" . ] [ assembly . AssemblyDescription ( "Plugin that sends notifications from Amazon SNS topic to Microsoft Dynamics CRM." . ] [ assembly . AssemblyConfiguration ( " . ] [ assembly . AssemblyCompany ( "CompanyName" . ] [ assembly . AssemblyProduct ( "PluginName" . ] [ assembly . AssemblyCopyright ( "Copyright 2016" . ] [ assembly . AssemblyTrademark ( " . ] [ assembly . AssemblyCulture ( " . ] [ assembly . Guid ( "9a2746b8-e8d6-4f84-a027-4e814d1785e0" . ] [ assembly . Version ( "1.0.0.#0" . ] // Additional attributes can go here...Assembly Info DescriptionThe AssemblyTitle attribute specifies the title of your plug-in and is displayed in various places within Microsoft Dynamics CRM 2015 such as the Settings window and under Options in the Administration area of Microsoft Dynamics CRM 2015. The AssemblyDescription attribute specifies a description of your plug-in that appears next to the title of your plug-in in various places within Microsoft Dynamics CRM 2015 such as the Settings window and under Options in the Administration area of Microsoft Dynamics CRM 2015. The AssemblyConfiguration attribute specifies additional configuration information for your custom assemblies beyond what is supplied by the target framework (in this case .NET 4. This attribute is only applicable if you are building assemblies that target multiple frameworks or if you are building an assembly that targets multiple platforms but only wants to provide specific attributes for one platform or framework. The AssemblyCompany attribute specifies the company name for your plug-in, which appears next to the title of your plug-in in various places within Microsoft Dynamics CRM 2015 such as the Settings window and under Options in the Administration area of Microsoft Dynamics CRM 2015. The AssemblyProduct attribute specifies the product name for your plug-in, which appears next to the title of your plug-in in various places within Microsoft Dynamics CRM 2015 such as the Settings window and under Options in the Administration area of Microsoft Dynamics CRM 2015. The AssemblyCopyright attribute specifies your plug-in copyright information, which appears next to the title of your plug-in in various places within Microsoft Dynamics CRM 2015 such as the Settings window and under Options in the Administration area of Microsoft Dynamics CRM 2015. The AssemblyTrademark attribute specifies your plug-in trademark information, which appears next to the title of your plug-in in various places within Microsoft Dynamics CRM 2015 such as the Settings window and under Options in the Administration area of Microsoft Dynamics CRM 2015. The AssemblyCulture attribute specifies your plug-in culture information, which appears next to the title of your plug-in in various places within Microsoft Dynamics CRM 2015 such as the Settings window and under Options in the Administration area of Microsoft Dynamics CRM 2015. The Guid attribute is a unique identifier for your component that is required by COM components on Windows systems. You can obtain a GUID from any number of online sources . The Version attribute indicates the version number of your plug-in . Note The version number must fplow standard numbering conventions . For more information about specifying version numbers , see Versioning Your Application in the Software Design Guide .Versioned AssembliesWhen you create a new spution package by using Visual Studio or by using MSBuild directly, by default all custom assemblies are automatically compiled with full strong names . This behavior ensures that all assemblies contain a strong name that matches their public key token (P/KU1. To ensure that there are no naming conflicts between assemblies from different vendors, assemblies should be automatically versioned using a build number or timestamp . However, if you are building local development environments because you work on multiple projects simultaneously or if you want custom versions of assemblies available for testing without having to publish them to production environments, it might be preferable not to compile all assemblies with full strong names by default . You can accomplish this by setting an environment variable called <TargetFrameworkVersion>v4</TargetFrameworkVersion> when you create a new spution package and checking Enable custom build configurations after creating new spution packages for both Debug and Release builds . This environment variable tells Visual Studio (or MSBuild. not to automatically generate strong names automatically when creating sputions or spution packages. You can then manually add strong names when necessary . For more information about how to set this environment variable, see Environment Variables Reference for Windows Store apps .Applying CustomizationsCustomizations apply to extensions that you

The process to integrate Microsoft Dynamics CRM and Amazon SNS may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.