Using Python to fetch data from D365 Finance & operations

 


This short article can help you fetch data from D365FinOps, which
a. You can subsequently analyse
b. You can perfrom further predictive modelling based on this data 
c. Understanding and forcasting the direction in which business is going and so on.

And it's quite straight forward.
Step 1. Define your Azure app registrations (AKA Microsoft Entra-ID).
Step 2. Enasure that the Azure App is registered in D365FO end by enabling the same through System Admin \\Setup\\Microsoft Entra ID Applications 

Step 3. We are going to use Jupyter Notebook here, for our code. This could be easily launched, if you have installed Anaconda as your IDE and then simply going to Windows \\ Jupyter. This will prompt you with an intermittent DOS prompt like this:


And will eventually open the Jupyter browser which looks lot like this:


Step 4: We are going to use the following modules for our code:

import requests

import json 

The former handles the requests and responses from API calls while the latter contains Newtonsoft based various intefcaes and class for decoding. 

Step 5: Define your app registration details under various variables:

CLIENT_SECRET = ' ##Your client secret here##'

TENANT_ID = '##Your tenant here##'

tokenendpoint = 'https://login.microsoftonline.com/<Give your tenant Id>/oauth2/token'

CLIENT_ID = '##Your client ID##'

GRANT_TYPE = 'Client_credentials'

RESOURCE =  '<D365fO base URL>/.default'

BaseURL = '<D365fO base URL>/.'

Step 6:
These variables now need to be passed on as a Dictionary element and posetd for Token generation:
tokenpost = {
    'client_id':CLIENT_ID,
    'scope':RESOURCE,
    'client_secret':CLIENT_SECRET,
    'grant_type': GRANT_TYPE
}
For more clarity on dictionary elements, please follow:
https://www.blogger.com/blog/post/edit/2520883737187850604/2026928301557204228

Step 7:

Get the token and store it in a variable:

tokenres = requests.get(tokenendpoint, data=tokenpost)

Step 8:
Here we are going to call D365FO data entities. For our demo purpose we are going to call SalesOrderPool data entity:
try:
    accesstoken = tokenres.json()['access_token']
except(KeyError):
    print('Could not get bearer access token')

api_call_headers = {
        'Authorization': 'Bearer ' + accesstoken,
        'Content-Type': 'application/json'
    }


test_api_url = f"{basUrl}/data/SalesOrderPoolsOrderPools"
api_call_response = str(requests.get(test_api_url, headers=api_call_headers))

try:
    if not api_call_response:
        data = json.loads(api_call_response)
        print(data)
    else:
        print ('No response');
except json.JSONDecodeError as e:
    print("Invalid JSON syntax:", e)

This will give entire SalesOrderPool JSON records.
If you want any speific details for any specific reord, you can use expaded JSOn query in the above code:
PoolVal = 'SalesOrder00001'
test_api_url = f"{basUrl}/data/SalesOrderPoolsOrderPools?$filter=PoolId eq {PoolVal}" 

In our previous discussion (https://subsd365.blogspot.com/2024/03/an-example-of-predictive-modelling.html) we saw how can we create a sampling based predicitve modeling strucure, where we can train our machine learning model with data and can find how easily it can predict any answer to a question. In the example we used, we were training the data with viewers, their genders, age and their fascination for movie-genres. So we asked the program what could be a man of age 40 would prefer to watch. And our code very smartly replied: Family drama. 

Likewise, we can use the data from D365FO to train our models to predict various outcomes and statistical manipulations.


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