Azure
Developing Scheduler for Dynamics 365 CE using Azure Function Part 2
Category: Azure,Azure integration,Azure Timer Function,CRM Dvelopment Series,Developing Scheduler for Dynamics 365 CE,Dynamics 365 Author: HIMBAP Date: 3 weeks ago Comments: 0

Introduction This is our second article about developing scheduler for Dynamics 365 CE using Azure Timer Function. In earlier article we developed a simple sample Azure Timer Function, now we are going to discuss how to deploy and configure scheduling for the Azure Timer Function. Solution Let’s first discuss how to schedule Timer to run it on specified times. Based… Read more »
Source: Mahendra Pal


Developing Scheduler for Dynamics 365 CE using Azure Function Part 1
Category: Azure,Azure integration,Azure Timer Function,CRM Dvelopment Series,Developing Scheduler for Dynamics 365 CE,Dynamics 365,Dynamics 365 CE with Azure Author: HIMBAP Date: 3 weeks ago Comments: 0

Introduction Sometimes we require to develop scheduler job for Dynamics 365 CE online. Currently we have different options to implement scheduler for Dynamics 365 CE online for example using workflow, Power Automate, Azure etc. In this article we are going to discuss how we can use Azure time trigger to develop scheduler for Dynamics 365 CE. Let’s say we have… Read more »
Source: Mahendra Pal


Dynamics 365 Integration with Azure Cosmos DB – Part I
Category: #cosmosdb #dynamics365,Azure,Dynamics 365 Author: Jeevarajan Kumar Date: 5 months ago Comments: 0

Introduction This is going to be a several part series where we will see how we can harness the power of Cosmos DB with Microsoft Dynamics 365. We will take a sample scenario of a multinational transportation network company offering services that include peer-to-peer ridesharing, food delivery, etc. like Uber, let’s name it ‘Troopers’ (well, […]

Source: Jeeva


Battle Between Microsoft Flow And Logic Apps ?
Category: Azure,Flow,Logic Apps,Microsoft Flow Author: Vignesh R Date: 7 months ago Comments: 0

What is Flow?

Microsoft Flow is an online workflow service that automates actions across the most common apps and services. For example, you can instantly receive an email or a push notification on your phone whenever a sales lead is added to Dynamics 365 

Microsoft Flow is a Software as a Service (SaaS).

Read for more info: https://docs.microsoft.com/en-us/learn/paths/automate-process-using-flow/

What is Logic Apps

Azure Logic Apps simplifies how you build automated scalable workflows that integrate apps and data across cloud services and on-premises systems. Learn how to create, design, and deploy logic apps that automate business processes with our quickstarts, tutorials, templates, and APIs.

Logic Apps is a Platform as a Service(PaaS) and Infrastructure as a Service(Iaas). Which exists within the Azure cloud.

Read for more info: https://docs.microsoft.com/en-us/learn/paths/automate-process-using-flow/

Is this both same or different?

Both are integration tools that have configurable workflow actions which makes it easy to build your workflow processes to integrate with all of your enterprise applications.

Microsoft flow is built on top of logic apps. Whatever logic apps can do can be done by flow but there are slight differences. Which we will discuss briefly…

Who is the Target Audience? who can use this?

Microsoft Flow Concentrates targeting on Citizen developer, Business Users, IT people, A guy with a deep understanding of coding (developers) – Sorry dev guys you are not the only rockstar for this show. We have got more company.

Logic apps are used to create a bit complex workflows on a B2B level which requires a developer or IT professional who can handle advanced integrations and developments.

  • Flow
  • Development is done using browser side(UI)
  • Built-in Analytics. Flows are created and grouped within the environment.
  • Administration is handled by flow, requires a basic office 365 subscription.
  • Features which are missing in Logic Apps – Buttons, Environments, Mobile App, Run as User, Resource is allowed to own flows.
  • Logic Apps
  • Development can be done using the browser(UI) or Visual Studio and deployed to Azure logic Apps.
  • Need to use Azure analytics services and has no concept of environment.
  • Administration is handled by Azure portal. So has additional built-in Azure security capabilities.

Conclusion

As a beginner, it would be great to start with Microsoft flow as it is easy to use and automate workflows. When it Comes to complex integration and B2B or B2C make sure you choose Logic Apps…

Source: Vignesh Ravi


The request channel timed out while waiting for a reply after 00:01:59.9687488
Category: "The request channel timed out while waiting for a reply after 00:01:59.9687488.",Azure,Azure Function,Azure function trigger,Dynamics 365,OrganizationWebProxyClient timeout error Author: HIMBAP Date: 9 months ago Comments: 0

Introduction
This post is about
“The request channel timed out while waiting for a reply after 00:01:59.9687488. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.” error, we got this error in our Azure function where we are updating Dynamics 365 CE records. We are going to discussed how we fixed it.

Details
We used following code in our Azure function to connect to Dynamics 365 CE.

 private static OrganizationWebProxyClient GetCRMService(TraceWriter log) {

  var aadInstance = "https://login.microsoftonline.com/";
  var organizationUrl = "https://himbap.crm8.dynamics.com";

  var tenantId = "8....";

  var clientId = "5...";

  var clientkey = "qZXgfddd.....";

  var clientcred = new ClientCredential(clientId, clientkey);

  var authenticationContext = new AuthenticationContext(aadInstance + tenantId);

  var authenticationResult = authenticationContext.AcquireTokenAsync(organizationUrl, clientcred);

  var requestedToken = authenticationResult.Result.AccessToken;

  var sdkService = new OrganizationWebProxyClient(GetServiceUrl(organizationUrl), false);
  sdkService.HeaderToken = requestedToken;
  return sdkService;
}

Please see our earlier post to know, how to connect to Dynamics 365 CE from Azure function.

Recently our Azure function started failing and when we checked logs it was timeout error. It was throwing timout error after two minute as default timeout limit for OrganizationWebProxy is 2 minute. But we can override this setting. We can get OrganizationWebProxyClient by passing following parameters.

public OrganizationWebProxyClient(
    Uri uri,
    TimeSpan timeout,
    Assembly strongTypeAssembly
)

Reference: Dynamics 365 CE SDK

To fix this issue we used following code

var sdkService = new OrganizationWebProxyClient(GetServiceUrl(organizationUrl),new TimeSpan(0, 10, 0), false);

We used 10 minute here, but you can change it based on your requirement.

Summary
We learned how to fixed OrganizationWebProxyClient timeout issue by passing TimeSpan parameter. Hope it will help someone. Stay tuned for more Dynamics 365 CE Contents !!

Source: Mahendra Pal