/// <summary>
        /// This function can create any record type using Json Entity Objects
        /// </summary>
        /// <param name="entityName"></param>
        /// <param name="entityObject"></param>
        /// <returns></returns>
        public async Task CreateEntityRecords(string entityName, JObject entityObject)
        {
            using (httpClient = CreateDynHttpClient(AccessToken, entityName))
            {
                HttpRequestMessage createHttpRequest = new HttpRequestMessage(HttpMethod.Post, BaseOrganizationApiUrl + "/api/data/v8.1/" + entityName);
                createHttpRequest.Content = new StringContent(entityObject.ToString(), Encoding.UTF8, "application/json");
                var response = await httpClient.SendAsync(createHttpRequest);
                response.EnsureSuccessStatusCode();
                if (response.StatusCode == HttpStatusCode.NoContent)
                {
                    // Do something with response. Example get content:
                    Console.WriteLine("The record was created successfully.");
                    Console.ReadKey();
                }
            }
        }

• FetchXML using Advanced Find in CRM
• Customizing D365 Portals

• Go to Advanced Find
• Select the entity as "Categories"
• See FetchXML Sample

• Go to D365 Online Instance - CRM
• Go to Portals > Web Templates > Knowledge Base Home
• Open the record
• You will see the below code:

• Add the liqiuid objects in following format:

• The Authorization Server is the v2.0 endpoint. It is responsible for ensuring the user's identity, granting and revoking access to resources, and issuing tokens. It is also known as the identity provider - it securely handles anything to do with the user's information, their access, and the trust relationships between parties in an flow.
• The Resource Owner is typically the end-user. It is the party that owns the data, and has the power to allow third parties to access that data, or resource.
• The OAuth Client is your app, identified by its Application Id. It is usually the party that the end-user interacts with, and it requests tokens from the authorization server. The client must be granted permission to access the resource by the resource owner.
• The Resource Server is where the resource or data resides. It trusts the Authorization Server to securely authenticate and authorize the OAuth Client, and uses Bearer access_tokens to ensure that access to a resource can be granted.

• Client ID : 32-Digit Guid registered in Azure
• Resource Url: Fully Qualified Dynamics 365 Url (ex: orgname.crm.dyamics.com)
• Oauth Endpoint: Fully Qualified Azure Oauth endpoint url (should be retrieved dynamically). See this post: Sample: https://login.windows.net/<tenantId>/oauth2/authorize?

Program app = new Program();
 Task.WaitAll(Task.Run(async () => await app.CreateMyReordsAsync())); 

Function definition

 async Task CreateMyReordsAsync()
        {
            WebApiOperationHelper apihelper = new WebApiOperationHelper();
            apihelper.BaseOrganizationApiUrl = "https://org.api.crm.dynamics.com";
            apihelper.ObtainOAuthToken(); //Let's say this step failed.

            if (!(string.IsNullOrEmpty(apihelper.AccessToken)))
            { //Success go }

public async Task SearchExistingRecord(string entityName, string filter)
        {
            httpClient = CreateDynHttpClient(AccessToken, entityName);
            string completedFilterCondition = BaseOrganizationApiUrl + "/api/data/v8.1/" + entityName + filter;
            var response = await httpClient.GetAsync(completedFilterCondition);
            response.EnsureSuccessStatusCode();
            if (response.StatusCode == HttpStatusCode.OK)
            {
                var content = await response.Content.ReadAsStringAsync();
                var objParsedContent = JsonConvert.DeserializeObject(content);

                // Do something with response. Example get content:
                Console.WriteLine(objParsedContent);
                Console.WriteLine("Records Found");
                Console.ReadKey();
                //Dispose the Object :: Best Practice
                httpClient.Dispose();
            }
        }

1. Using Azure Management Console
2. Json Serialize using Newtonsoft
3. Basic understanding of HttpClient and WebAPI in general
4. ADAL (Azure Active Directory Authentication Library)

1. Sign-up for Azure Trial/Office 365/Dynamics 365 (Formerly called as CRM Online) in a single tenant.
2. Launch your Azure Management Console and Navigate to Active Directory.
3. 
4. Register your application in Azure AD
5. 
6. Choose Native Client Application. You can read more about this in Azure Documentation.
7. Once you've provided the information including Redirect Url. You should see the app dashboard as below
8. 
9. You've completed configuration! :)

• Searching an existing account, if found it will show an alert with a count of accounts found
  • If not found, then it will ask you if you want to create one.

• Walkthrough: Single Sign-on from a Custom Web Page
• CRM 2011 and ASP.NET Single Sign-on: Use WAUTH for Integrated Web Apps (Thanks to Austin jones for this explanation)

It's really important for you to understand on how WAUTH is used. The blog article above really helps you to understand this from the expert level point of view. To go more in depth about the SAML Based Authentication Context, you can see the below table at: Supported SAML Authentication Context Classes and Strengths

Authentication Method	Authentication Context Class URI
User Name and Password	urn:oasis:names:tc:SAML:2.0:ac:classes:Password
Password Protected Transport	urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport
Transport Layer Security (TLS) Client	urn:oasis:names:tc:SAML:2.0:ac:classes:TLSClient
X.509 Certificate	urn:oasis:names:tc:SAML:2.0:ac:classes:X509
Integrated Windows Authentication	urn:federation:authentication:windows
Kerberos	urn:oasis:names:tc:SAML:2.0:ac:classes:Kerberos

Now, I'll go ahead and walk you through the steps required to build your application:

• Create a new Project "ASP.NET" Web Application in Visual Studio
• You can choose to write the below sample to display the post login information as below:

• Now go ahead and Publish your website in IIS / or Host your site.
• While the hosting is done and mapped to your local path. I'd choose a custom header for my website to look like below

• I chose https://custom.domain.com:82/Welcome.aspx. Be sure to select your "Wild Card certificate". I'm using the same as I have for ADFS STS (With onebox setup)
• Go ahead and download the WIF SDK
• Go to Programs, and Select "Windows Identity Federation Utility Wizard" (FedUtil.exe) - Please ensure to open this with "Run as Administrator" option.
• While you keep running this tool with Next option, you'll be providing below information
   - Custom Web Url: https://custom.domain.com:82/Welcome.aspx

                 - STS Url: https://sts.domain.com/FederationMetadata/2007-06/FederationMetadata.xml

• I've added few screen shots below

• Now open Global.asax to use the code from https://blogs.msdn.com/b/crminthefield/archive/2013/10/30/crm-2011-and-asp-net-single-sign-on-use-wauth-for-integrated-web-apps.aspx. This will help you choose if you need IFD Redirected page or Claims Page. For demo I've just used this below:

• These steps will be helpful for you to create your application.

Happy CRM Integration :)

Cheers,
Apurv

Today I'm going to talk about an exciting new feature of CRM 2013/2015 environment "Business Process Flows". You can read more about the features here

While you can do this job from UI, but the idea is to automate the creation of next steps automatically. This article talks about the a plugin code using CRM SDK to achieve this.

Some Prerequisites before you start:

1. Hands on CRM 2013 - Business process flow
2. Hands on CRM SDK 2013
3. Plugin Registration for CRM 2013
4. .NET Framework 4.0 / Visual Studio 2012 or higher

Consider the scenario below:

• Opportunity Entity
• Custom Entity new_customflow

Please make sure you've enabled "Business Process Flows" in the entity customization for "new_customflow" entity, see below image:

• Now go ahead and create a business flow with a custom entity

This will look like as shown below:

You're all set with designing the business Flows via CRM customizations.

• Now when you create opportunity, it should automatically create a record for Custom Flows and link it to existing opportunity.

You'll need to write the code as below

• This code will be registered as Plugin

For Plugins (Config):
a. Message: Create
b. Entity: Opportunity
c. Operation: Post
d. Execution mode: Sync

Note: The workflow Id and Stage Id has to be correctly mentioned. In this sample, I've used hardcoded values which can be replaced by just doing a simple retrieve using SDK. Or you can use Early bound classes to use "WorkflowSet".

You're now all set for automating your business process flows. As you hit "next" you can see the opportunity is now listed as connected flow. In the below screenshot, notice "108".

Stages preview:

I'd like to thank Kaustubh Giri who helped me with all the testing and innovating the business processes.



Happy customizing! :)

Thanks,
Apurv

You'll need a working knowledge on the following

1. ADAL (Active Directory Authentication Library) - Available on Nuget
2. ADFS 3.0
3. Window Store Apps
4. A bit of Fiddler (Optional)

I'm trying to walk you through the entire steps which includes the configuration of ADFS, then we'll go ahead and build the sample.

Register your application with ADFS Environment for development / Token issue

1. Create a GUID using Guid Generator using Visual Studio
2. Make a note of it for registration
3. At this point, I've not provided Redirect Url

Adfs script:

Add-AdfsClient -ClientId C8E3F34A-E1A6-455C-A6DB-A1B82E6A6BE0 -Name WindowsAppsStore -Description "OAuth for CRM connecting Clients from Windows Store"

Windows Store Application demo

Note: This app is using Mobile SDK Please read the instructions to compile and generate the Assembly for app reference

1. Create a new project using Visual Studio 2013
2. Choose, Project for Store (Blank should be okay)
3. Add Reference to "Microsoft.Crm.Sdk.Mobile"
4. Add CrmHelper.cs file form the Mobile SDK Download to reuse the code.
5. I have written and attached below

Few Global Variables

ADAL Based Sample:

It's important that you run the code for the first time with all the correct parameters/variables set and obtain the redirect URL from below code:
public static string redirectUri = WebAuthenticationBroker.GetCurrentApplicationCallbackUri().ToString();

Once you've see the value, it will look something like this
ms-app://s-1-15-2-23142
Now go back to ADFS and use the below command:

Set-AdfsClient -ClientId C8E3F34A-E1A6-455C-A6DB-A1B82E6A6BE0 -Name WindowsAppsStore -Description "OAuth for CRM connecting Clients from Windows Store" -RedirectUri ms-app://s-1-15-2-23142

Once you execute and deploy your application. You can see the token value in fiddler as below:

        HTTP/1.1 200 OK
        Cache-Control: no-store
        Pragma: no-cache
        Content-Length: 1115
        Content-Type: application/json;charset=UTF-8
        Server: Microsoft-HTTPAPI/2.0
        client-request-id: 43224044-4a95-41cc-9716-fe9387529c49
        Date: Tue, 06 Jan 2015 18:52:44 GMT
        {"access_token":"token value encrypted>":491520}

My special credits to Kenichiro Nakamura for inspiring and providing technical insights to use Mobile SDK for CRM.

Cheers,
Apurv

MainPage.xaml.zip

https://github.com/apurvgh/Dynamics365Samples/blob/master/Crm_Sdk_Samples/OldSchoolCrmConnection.cs