Azure Funda

In this blog, I am going to cover some of the most frequent issues/requirements people face when developing Azure Functions via Visual Studio. These topics are based on my learnings while developing Azure Functions and I wanted to share the same with community out there. Here are the topics that I will cover in this blog post - Local Debugging of Service Bus Triggered Azure Functions Solving CORS Issue - Local Debugging and after deployment to Azure Run Azure Functions Locally on a different Port Debug Timer Triggered Azure Functions So let's get started. Local Debugging of Service Bus Triggered Azure Functions When you try to debug your Service Bus triggered Azure Function locally, you would need to ensure that there are no other listeners active for your Service Bus Topic and Subscription. Listeners here refer to other people trying to debug on same Service Bus, Topic and Subscription, other Azure Functions or any WebJobs deployed on Azure and running c...

If you want to retrieve 5000+ records in Dynamics 365 CE, you need to make use of Paging concept of CRM. By default 5000 records are retrieved in a single OData call in CRM. To get more, you need to make subsequent calls to OData Endpoint by passing a paging cookie in the request. I will be using a simple C# Console Application to retrieve 5000+ records from Dynamics 365 CE, by making use of OData API Endpoint provided by CRM and passing Fetch XML in OData Call . Concept: CRM OData Endpoints allows us to use Fetch XML to retrieve data from Microsoft Dynamics 365 CE.  If your resultset has more than 5000 records, you will be returned with first 5000 records ONLY in one OData call. To know if the resultset has more than 5000 records, we make use of the response from OData call. The response is added with a cookie value contained in a key - "@Microsoft.Dynamics.CRM.fetchxmlpagingcookie" If you wish to fetch the next set of resultset data, you will have to pass this c...

What is SWAGGER UI? Swagger UI is an HTML/CSS/JS framework that provides interactive documentation of your RESTful APIs and generates a navigable UI of the documentation. Swagger UI provides automatically generated HTML assets that give you automatic documentation and even an online test tool. It is extremely easy to set up, and comes with a lot of configurable options like XML Documentation, various kinds of Authentications (Basic, OAUTH2, API key), etc. which can be configured depending on the security schemes set up in your APIs. This can reduce the time and efforts you spend on creating your Client Application to consume and test your RESTful APIs. With minimum amount of code, you will get an easy to use test client for your APIs. Benefits of using SWAGGER UI? A Sandbox! Create test client for your APIs in seconds! It's comprehensible for developers and non-developers. It's easily adjustable. It’s like a sitemap for your API. How to set Up the Swagger...