Microsoft expects all Dynamics 365 / X++ development to be done in a preconfigured virtual machine (sometimes called a “onebox”) that has local installs of Visual Studio, Dynamics, and SQL Server; these are integrated in a way to ease development. They would prefer that you rented these VMs from them, which has some integration advantages; but it is possible to set up your own, which is probably less expensive in the long run, and might be more convenient. These instructions will help you set up that development environment on a personal machine; although there are a few wiki pages on it, there does not seem to be any complete information gathered in one place.
As with all my blog posts, if you have comments or additional information, I will endeavor to update what I have written here. I have noticed that this is by far my most…
In my recent Dynamics 365 for Operations implementation on 7.1, we encountered an issue with MPOS switching to offline randomly . MPOS as we know switches to offline either when triggered manually or when the switch is seamless (automatically) when there is any issue in the communication between MPOS and D365 Retail Server, an example is a network interruption (for more information on the overall Retail Topology do refer this link MPOS Technical Architecture)
In a usual scenario, when an interruption occurs in between a transaction, cashier would get an error message the Cart State has changed. The cashier would need to void the transaction and then start all over again and end with creating an offline transaction (Not the kind of experience you want when you have a queue of customers at the billing). Another issue that coupled with this was that the MPOS logo would not switch from offline to online when the MPOS mode switched.
Make sure you uptake following binary hotfixes as soon as you can if you have enabled MPOS in offline mode
KB 4049328 – MPOS offline logo issue
KB 4058723- Set of reliability fixes for POS Offline
Also include the following X++ hotfix which complements the above binary fix
KB4058724 – Set of reliability fixes for POS Offline
This post is meant for anyone starting to explore Dynamics 365 for Operations Retail. I have included some of the resources that I have found very useful. In this video I will take a quick look at the following resources
1. The first link is the landing page on Retail on the Microsoft documentation portal docs.microsoft.com
This article is the outcome of a shared session with credit to my friend Vishal Kohli .
While creating a new store in the store master in Dyn365FO, you may face the following error.
“Cannot create a record in Global address book (DirPartyTable). The record already exists.”
The issue is that the operating number keyed is already existing in the system. Therefore you need to make sure you key in a number that does not already exist. The error message can be a little confusing in this regard, which is why I thought this warrants a post.
Note -You are most likely to face this issue when your operating unit number sequence is configured as Manual.
If you are on Dynamics 365 for Operations 7.1 and planning to uptake the latest set of binary hotfixes, expect to see the above error when trying to activate MPOS.
Sergey from Microsoft has described the change that is triggered by binary hotfix KB4051347 in below link in great detail. Just one note though if you are on 7.1 you will not find the event ID 40619 in the event viewer. Its only available 7.2 onwards.