Integration using Azure service topics with D365F&O, using Azure functions: a strategy, Part-2



For creating a service bus namespace, topic, subscription and automatic data filtration, please follow my previous blog: https://subsd365.blogspot.com/2023/07/integration-using-azure-service-topics.html

Ok, all set? Let us now explore how to consume the message received from Service bus to D365FO, using Azure Functions. 

Step 1: Creating the Azure function

In your Visual Studio (alternately you can also use Visual Studio Code) -- create new project --> in the template search for  Azure function, the following screen appears:

Select Function = Service Bus Topic Trigger.
Here Topic name is = is the name of my topic which I created in my service bus, subscription name is the name of my subscription which I created.

  
In the Connection String property, just write: sbConStr for now. Will explain what's this in the next point.
Click create to continue.

Step 2: Getting the connection string
To get the connection string, go to Azure Functions --> Shared Access Policies:





 Click on the same. The following screen opens:



Copy the 'Connection string' value by clicking on the highlighted icon. Come back to VS --> Go to LocalSettings.JSON --> Create a new entry called 'sbConStr' as below:


Consequently your code now looks like this:


You can refer to videos for parsing incoming JSON payloads to feed into D365FO from the following video links:
The first session link -https://lnkd.in/dknijQmG
The Second Session link - https://lnkd.in/dphaMR8H

Consequently when I am sending the following message in my Service bus explorer, 
with the label = SalesPool:


It lands successfully in D365FO as:

The console of your VS registers the message you have posted as:


So much for today. See you soon with a new idea. Keep daxing, keep Azuring !!!

 

Comments

Post a Comment

Popular posts from this blog

Make your menu items visible on main menu, conditionally,, using this cool feature of D365FO

Image
  Wassup guys? I am sure you must have encountered this situation where you needed to display your menuItems, on main menu, based on some condition, haven't you? This was only possible by using config keys and flights. Things get a bit tricky,  when suppose you have a requirement like this: you need to make it dynamic, by introducing a toggle switch on a field on a paremeter form.  Suppose on Accounts Receivables Parameters >> You have a field called ' Show US customer '. You have a requirement that says when you turn on this toggle, then only the menuItem ' Input SSN details ', under AR module. This is now highly acheivable by leveraging subscription to 'SysMenuNavigationObjectFactory' class, simply by saying a. Create a new class USMenuItemsVisibilityManager b. Copy the following method, with proper documentation (don't change signature/anything else) [SubscribesTo(classstr(SysMenuNavigationObjectFactory), staticdelegatestr(SysMenuNavigationObjec...
Read more

X++ : mistakes which developers commit the most

Image
   The most important thing is to remember where and when to write the code. a. Developers have an inherent habit of writing erratic select statements: select * from custTable where custTable.AccountNum == <SomeValue> Where in essence we need to make use of optimized choice of fields in the select statement. b. Making use of 'continue' keywords: While select custTrans where <someConditions> { if (cusTTrans.CustGroup != mappingTable.CustGroup) { continue; } } 'Continue' statements are precisely a very unhygienic way of designing your code. The above statement could have been easily ornamented by using exists/not exists joins. Using Continue statements would eventually result in a high performance impact. Also select statements should be made punctuated with a 'firstonly' clause -- just not from best practise standpoint, but also from performance considerations. c. Writing nested loops: This is a common mistake that perha...
Read more

Are you still using macros? Be sure you read this.

Image
  You still use a lot of macros in your code, don't you? Of course you should: Macros, as per Microsoft,  are p recompiler directives are processed before the code is compiled. The directives declare and handle macros and their values. The directives are removed by the precompiler so that the X++ compiler never encounters them. The X++ compiler only sees the sequence of characters written into the X++ code by the directives. However macros, are not quite recomended by Microsoft. They are slow, they can be subsequently deorectaed at any later time.  The Macros are  actually  a type of classes, only that they are not instantiated and not need be defined as classes. Hence runtime garbage collection could be a huge issue, consquently (a class when gets out of scope, gets garbage-collected owing to the destructor classes of DOT net instrumentation classes). Summing up, macrros are a bit old way of writing code. Use static classes instead. public static class MyIdenti...
Read more