The Case of the "Sticky" Legal Entity: Why Your D365FO Name Change Isn't Showing Up

Have you ever updated a Legal Entity name in Dynamics 365 Finance and Operations, hit save, refreshed your browser, and… nothing? The old name is still staring back at you from the dashboard or that little "pill" in the top-right corner.

It feels like the system is gaslighting you! In this blog, we’ll explore why a simple name change can turn into a deep-dive into the D365FO architecture, and we'll share the definitive steps to fix it.

The Problem: "I changed it, but I don't see it!"

The goal seems simple: Navigate to Legal Entities, change the "Name" field, and expect the UI to reflect that change globally. However, due to how D365FO handles caching and data relationships, the "Display Name" often gets stuck in the Application Object Server (AOS) memory or the Global Address Book (GAB).

Observations from the Field (The "Trial and Error" Phase)

Before we found the "Golden Fix," we observed several interesting behaviors while trying to force the system to update:

1. The Browser Isn't the Boss: A "Hard Refresh" (Ctrl + F5) or clearing browser cache rarely works for this. This isn't a website styling issue; it's a server-side data synchronization issue.

2. The "Pill" Control is Persistent: When using the modern Unified Header (the "bubble" that shows ID | Name), the name seems more stubborn than when using the Legacy Navigation bar. This is because that specific control is heavily dependent on the Metadata Cache.

3. Default Company Swapping: Even changing your user's default company, logging out, and logging back in doesn't always "nudge" the session to re-read the new name.

4. The GAB Duplicate Mystery: Searching the Global Address Book (GAB) often reveals multiple records for the same name. If the Legal Entity is linked to the "wrong" Party ID, or if the Party Record didn't update along with the Legal Entity form, the UI stays stuck in the past.

---

The Master Checklist: How to Actually Fix It

If you are facing this, follow these steps in order. 

1. The Global Address Book (GAB) Audit

D365FO pulls names from the Party Record, not just the Legal Entity table.

• Identify the Source of Truth: Go to the Legal Entity form, right-click the name, and select Form Information > Administration. Note the Party ID.

• Update the GAB: Search for that specific Party ID in the Global Address Book. If the name there is the old one, edit it manually.

• The Merge: If you find duplicate Party IDs for your company, use the GAB Merge tool to consolidate them into the "Master" ID linked to your Legal Entity.

• Learn more: Microsoft Learn: Global Address Book Scopes

2. The Server-Side Flush (The "Magic" URL)

If the data is correct in the GAB but the UI is still wrong, you need to flush the AOS cache. Append this to your environment URL:

https://[yoururl].com/?mi=SysClassRunner&cls=SysFlushData

6. The Final Option: Service Restart (Tier-2)

In Tier-2 Sandbox environments, the Azure Redis Cache might be holding onto the old name. If all else fails, go to Lifecycle Services (LCS) and perform an AOS Service Restart. This clears the memory entirely and forces a fresh pull from the database.

• Reference: LCS Environment Management
  
  

---

Conclusion: Data Integrity is Key

The takeaway? A Legal Entity in D365FO isn't just a row in a table; it’s a Party in a global ecosystem. When names get "stuck," it's almost always a sign that the link between the CompanyInfo table and the DirPartyTable needs a little manual love (or a big server-side reset).

We hope this guide helps you keep your environments clean and your Legal Entities accurately named!

Happy New Year everyone and Happy D365'ing!!

Overview of Synapse Link for Dynamics 365 Finance and Operations

Azure Synapse Link enables seamless integration allows for continuous data export from Dynamics 365 to Azure Synapse Analytics and Azure Data Lake Storage Gen2, facilitating advanced analytics and insights.

Practical Applications (A Youtube video is always a good start to have the right understanding)

• Analytics and Reporting: By exporting data to Azure Synapse Analytics, organizations can leverage powerful analytics tools to gain insights and make data-driven decisions.

• Data Integration: Synapse Link facilitates the integration of Dynamics 365 data with other data sources, enabling comprehensive data analysis.

Here are some individual links providing additional information:

• Azure Synapse Link for Dataverse: This article explains how to use Azure Synapse Link to connect Microsoft Dataverse data to Azure Synapse Analytics. It covers prerequisites, how to connect Dataverse to a Synapse workspace, manage table data, and monitor the link. The guide also includes steps to unlink and relink the Synapse Link and view data in Azure Synapse Analytics.
  
  
• Export Data from D365 FO using Synapse Link: This blog post details the process of exporting data from Dynamics 365 Finance and Operations (D365 FO) using Azure Synapse Link. It highlights the benefits of continuous data export to Azure Synapse Analytics and Azure Data Lake Storage Gen2, and provides a step-by-step guide on setting up the export, managing data, and troubleshooting common issues. 
  
  
• Set Up Access Control for Azure Synapse Workspace: This article provides a comprehensive guide on setting up access control for an Azure Synapse workspace. It discusses various access control mechanisms, including Azure roles, Synapse roles, SQL permissions, and Git permissions. The guide also includes steps to secure a Synapse workspace by configuring security groups, preparing ADLS Gen2 storage accounts, and assigning roles.
  
  
• Azure Synapse Link with Managed Identities: This document explains how to use managed identities for Azure with Azure Synapse Link. It covers the prerequisites, steps to enable enterprise policy for Azure subscriptions, and how to grant reader access to the enterprise policy. The guide also provides instructions on creating and configuring managed identities to secure access to Azure Data Lake Storage accounts.
  
  
• Azure Synapse RBAC Roles: This article describes the built-in role-based access control (RBAC) roles in Azure Synapse Analytics. It details the permissions granted by each role, the scopes at which they can be used, and how to review and assign Synapse RBAC roles. The guide also includes a table summarizing the roles and their associated permissions.
  
  
• Grant Permissions to Managed Identity in Synapse Workspace: This guide teaches how to grant permissions to the managed identity in an Azure Synapse workspace. It explains the steps to assign the Storage Blob Data Contributor role to the managed identity for accessing ADLS Gen2 storage accounts. The article also covers the process of granting permissions during and after workspace creation.
  
  
• Synapse Link Lake Database Permissions: This blog post discusses the permissions required for using Synapse Link with lake databases in Azure Synapse Analytics. It highlights the security model for lake databases, including Azure role-based access control (RBAC) and Microsoft Entra ID (formerly Azure AD) permissions. The post also provides tips on managing permissions for lake databases and troubleshooting common issues.
  
  
• Common Azure Synapse Link for SQL Storage Permission Issues: This blog post addresses common permission issues encountered when using Azure Synapse Link for SQL storage. It provides solutions for resolving access problems to Azure Data Lake Storage Gen2 accounts, including steps to refresh access tokens and assign the correct permissions. The post also offers troubleshooting tips for both new and existing Synapse Link setups.

Integration Key Patterns and Best Practices from MSFT sessions

Microsoft Dynamics 365 FastTrack TechTalks are a must-attend series for those who look to deepen their knowledge on Dynamics. These TechTalks are designed to provide in-depth knowledge and practical guidance directly from Microsoft experts, helping you to maximize the potential of your Dynamics 365 solutions. One such series is related to Integration patterns and related best practices. 

1. Dynamics 365 Integration General Guidance | October 2, 2023:
   https://community.dynamics.com/blogs/post/?postid=13b3efef-ee69-ee11-9ae7-000d3a574bff 
   This video provides an overview of general integration strategies and best practices for Dynamics 365. It covers various integration scenarios, tools, and techniques to ensure seamless data flow and system interoperability. Key topics include the use of APIs, data connectors, and middleware solutions to integrate Dynamics 365 with other applications and services.
   
   
2. Integration Patterns for Dynamics 365 Finance and Operations Applications | October 30, 2023:
   https://community.dynamics.com/blogs/post/?postid=27adb1ef-d19d-ee11-be37-000d3a4e511f
   This session focuses on specific integration patterns for Dynamics 365 Finance and Operations applications. It discusses synchronous and asynchronous integration methods, the use of web application programming interfaces (APIs), and data integration scenarios. The video aims to help developers and solution architects understand the best practices for integrating finance and operations apps with other systems.
   
   
3. Integration Patterns for Dataverse | November 6, 2023:
   https://community.dynamics.com/blogs/post/?postid=388a6e70-738d-ee11-8179-00224827e5da
   This video explores various integration patterns for Microsoft Dataverse. It covers inbound and outbound integration methods, including the use of APIs, Power Automate, Logic Apps, and Azure Data Factory. The session also highlights best practices for handling large data volumes, real-time data integration, and ensuring data security and scalability.

There is also a fourth video "Session 4 - Complex integration scenarios - aimed to be delivered on December th 4th 2023. However, I couldn't find the link to that video. So, if you were able to find it, please do post it in here. Thanks.