Bring data to Microsoft Fabric Onelake from D365F&O (no Azure SQL needed)

 

Hi freinds, in one of recent blogs, I chalked out an integration stratgey pattern of setting up of D365F&O with Microsoft Fabric, by routing it through a DMF batch job to Azure SQL. This currrent blog talks about even a cool hack of direct integration between D365F&O and Microsoft Fabric, just harnessing Synapse Link itself -- no additional/intermeidary steps are required.

Here are the steps:

Step 1: Create a Datalake Storage account in Azure Portal, with the following settings:

 Don't forget to mark the following setting, from the advanced tab:

Click Review + create >> Create to complete the wizard to create the Storage account.

Step 2: Come to PowerApps page (https://make.powerapps.com/environments), and check if you are able to view the  Azure Synapse Link:
If not, then you have to click on More >> Discover all >> You should be able to see it as under the Data management:

Ensure that you are on the correct environment:


Step 3:
Once this is done click on Tables >> and choose Azure Fabric from the highlighted Link:

Allow it some time to spin up from the capacity planning and the following screen will load up:


Click Save connection.
Make sure that you choose the same region for your Azure Fabric as you have selected for Capacity planning for the Microsoft fabric.
 
Step 4: 
In the next step, you need to select the Workspace which you have created for the Microsoft Fabric:

Step-5: 
In the next step, it will create all the needful of setting up connects with Onelake and connects with Microsoft Fabric:

Step 5:
It will appear as a link as under Azure Synapse Link:

Just click on this link: it will also show up under the D365 Financed & Operations tab:
For our demo purpose, I am just selecting Item Group. Click Save and allow it some time for queuing and initial Synch.

Once completed, the data will automaticlally show under Onelake Datahub:


Whew -- that's it. Your data is now in Microsoft Fabric, without doing anything as an extra step 👲👲
What's next? Power up your BI reports, prepare Spark Jobs, route it Azure Data modelling pieplines, to analyse it further.

With that, I am taking your leave, and would come back with more ideas on Data engineering, Azure and AI/ML studios. Much love and namaste 💓💓💓

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

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

Modifying a DMF data entity query dynamically, from another query, for filteration in D365FO

Image
  Problem statement  Have you ever came across a situation where you needed to run your data entity through a batch, and in your batch you have a very complex composite query (where the query ranges could be anything -- the user can keep adding new ranges to the query) and you need pass on the query range values to your data entity query. I bet you must have faced this: say, your data contract is having an AOT query called PurchContractQry where you have PurchTable, Purchline, InventDim, PurchParmLine and a litter of related tables. You have an entity that does have a different query (as you know Data entities store queries as packed data in DMFDefinitionGroupEntity )-- how could you possibly make the ranges flow to your Entity, then? The following blog explains the same. As an example: we have created a Data entity called D365DataEntityPurchExport , which exports records based on the ranges supplied in a query coming from a contract Class, called PurchContractQry. We need to ...
Read more