Here, you’ll find practical tips, deep technical dives, and real-world solutions for Microsoft Dynamics 365 F&O development. From X++ best practices and debugging tricks to data entities, integrations, and performance optimization, this blog is all about making your F&O journey smoother and more efficient. Whether you’re a seasoned developer or just starting out, there’s something here for you. Stay tuned for hands-on tutorials, expert insights, and the latest F&O innovations! 💡🔥
Friday, September 1, 2023
ORGANIZE PROJECT BY ELEMENT TYPE IN VISUAL STUDIO FOR D365 F&O
Wednesday, July 26, 2023
Dynamics 365 Finance & Operations The path is already mapped in workspace
Purpose:
The purpose of this blog is to explain how can we resolve the version control workspace issue while working with Azure DevOps version control, previously known as VSTS or TFS.
Error:
The path % is already mapped in workspace %
Resolution:
First make sure that no other workspace is mapped to this path
(including remote workspaces).
Sometimes the trick could be to clear the TFS cache on client machines
1. Close all instances of Visual Studio on the client machine
2. Manually delete the corresponding TFS client cache folder
3. Start Visual Studio
The path to TFS client cache folder varies depending on the TFS
version. Delete contents of the cache folder to resolve the issue:
Tfs 2019: “%localappdata%\Microsoft\Team Foundation\8.0\Cache\”
Tfs 2017: “%localappdata%\Microsoft\Team Foundation\7.0\Cache\”
Tfs 2015: “%localappdata%\Microsoft\Team Foundation\6.0\Cache\”
Tfs 2013: “%localappdata%\Microsoft\Team Foundation\5.0\Cache\”
Tfs 2012: “%localappdata%\Microsoft\Team Foundation\4.0\Cache\”

