Skip to main content

Posts

Fabric - See history of parquet files

One advantage with parquet files is that it keeps history. Run the below script and it will give you the history.  %% sql DESCRIBE HISTORY dirpartytable; Below is an example I have in my environment. Use "VERSION AS OF"  Now that you have the history, you can use the VERSION AS OF statement. This will give you the previous values for the record.  %% sql SELECT partynumber, primarycontactphone, primarycontactemail FROM dirpartytable WHERE partynumber = '000001702' ; SELECT partynumber, primarycontactphone, primarycontactemail FROM dirpartytable VERSION AS OF 2 WHERE partynumber = '000001702' ; The below example is when I deleted the primary contact phone number.
Recent posts

Fabric - Sample Notebook scripts for MSDyn365FO

This will be a fairly straightforward blog post covering different ways of copying data from a shortcut delta table into a delta table created automatically via a notebook. Select statement with a join %% sql SELECT     party.recid AS PartyId     ,party.name AS Name     ,COALESCE(party.namealias, '' ) AS ShortName     ,COALESCE(postal.countryregionid, '' ) AS Country     ,COALESCE(postal.state, '' ) AS State     ,COALESCE(postal.city, '' ) AS City     ,COALESCE(postal.street, '' ) AS Street     ,COALESCE(postal.zipcode, '' ) AS PostCode     ,COALESCE(phone.locator, '' ) AS PhoneNumber     ,COALESCE(email.locator, '' ) AS Email FROM dirpartytable party LEFT OUTER JOIN logisticspostaladdress postal ON postal. location = party.primaryaddresslocation AND postal.validto > current_date () -- filters only valid(effective) addresses LEFT OUTER JOIN logisticselectronicaddress phone ON phone.recid = party

Exploring Analytical Options with Dynamics 365 Finance and Operations: Link to Fabric

I’ve recently been exploring various analytical options within Dynamics 365 Finance and Operations, and one that I’ve delved deeply into is Link to Fabric. There is a walkthrough guide available on the Microsoft Fasttrack Github repo . See  Hands-on Lab: Link to Fabric from Dynamics 365 finance and operations apps This guide is an excellent starting point and should be one of the first things you try out. However, it’s important to understand that there are limitations to this approach that may not be suitable for all real-world scenarios. Lets discuss these items and what I have been exploring ... Background I want to join multiple tables to create my denormalised views that I can report on. My goal is to use  Direct Lake  mode in the semantic model. Specifically, I wanted to avoid the need to reimport data into Power BI for reporting.  Key Limitations The first limitation you’ll encounter is: By design, only tables in the semantic model derived from tables in a Lakehouse or Warehouse

Copy Company and Number Sequence Issue

When it comes to setting up multiple companies, stream lining the process can save you time and effort. One effective strategy is to establish a template company or select a source company to replicate from.  In this blog post, I won't go through how to use the copy company feature as there are many blogs out there and Microsoft has some good documentation. https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/copy-configuration What I will explain is an issue I faced when using it. I found that the copy number sequence isn't working as expected. It throws an error when used as part of the copy company. Number sequence feature: There are two check boxes for number sequence copy: Copy number sequence - this will add number sequence entities and when run, it will change company references in the staging table before processing to target. Reset to smallest value - this resets the number sequence if it is used back to its smallest value. In most cases b

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it.  From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines feature is

Asset Management Mobile App

  Microsoft recently released a preview mobile app for Asset Management . The App gives 2 personas that you can use it for: Maintenance worker - You need to be assigned to the security role "Maintenance worker"  https://learn.microsoft.com/en-us/dynamics365/supply-chain/asset-management/asset-management-mobile-app/work-orders . It will allow you to give feedback on a work order such updating actual hours, items, checklists and attachments. Maintenance requester - You just need a teams license and can assign "Maintenance requester" security role  https://learn.microsoft.com/en-us/dynamics365/supply-chain/asset-management/asset-management-mobile-app/maintenance-requests . This will allow you to create a request. Installation To install, go to AppSource to find the app  Dynamics 365 Asset Management Mobile Application Read the Onboarding doc page  as there are prerequisites. Such as installing the  Finance and Operations Virtual Entity solution. The install is prett

My Experience moving FinOps/X++ code to GitHub

I recently saw a question on LinkedIn, asking if we can share our experience with moving to Git version control. https://www.linkedin.com/posts/tommyskaue_developer-git-xppdevs-activity-7017198598765342721-0i8c Here is a response to it. I will share my experience of moving to GitHub version control. We have chosen to move our X++ code to Git and in particular GitHub about 6 months ago. Reasons for the move Below are some of the reasons we have chosen to move from TFVC on Azure DevOps to Git on GitHub: Every single source code/project we have is on Git except for our X++ code. I have been asked way too many times as to why we are on TFVC. I have explained many times but I can't help shake the feeling that others think X++ is some old language. In other words, better alignment. There has been considerable effort to move to GitHub as our approved version control from many other version control systems. This is to make our code more accessible to all teams, have policies in place, leve