When moving data from a sandbox environment to your dev-box you need sqlpackage to unpack the bacpac file to a database. This could give you an error message stating that the file contains corrupted data:
To get yourself passed this you can download the .net core edition of the SQLPackage from here:
This is something that I generally forget whenever I create a new dev-box. Visual Studio needs to be running as Administrator otherwise you’ll get messages such as “Access to the path ‘K:\AosService\PackagesLocalDirectory\Bin\InstalledVersion.json’ is denied”:
and “Visual Studio is not running as administrator. Finance and Operations (Dynamics 365) requires Visual Studio to be running as administrator. Please restart Visual Studio as administrator”:
You can always right-click on your VS-shortcut and select “Run as administrator”, but if you’re even remotely like me, you’ll forget that approx 82% of the times.
So what you need to do is to modify the shortcut you’re using. In my case I modify the shortcut in my Taskbar. Right click on the shortcut for Visual Studio and instead of clicking “Run as administrator” you click Properties:
In the properties window you click the Advanced button:
In the window that opens up tick the “Run as administrator”:
Click OK and OK and you’re done. Next time you use the shortcut it runs VS as administrator.
In the Dynamics 365 POS it’s possible to enable a developer mode that gives you some additional options like seeing the id of the strings, grid views, coloring aids and so on. To enable these features you need to rebuild the POS with the value config.isDebugMode to true in the pos.js file. That’s easy in the CPOS but requires some build/deploy in MPOS.
Our POS developer gave me a tip to shortcut that … a lot. It’s a few easy steps and they go like this:
Enable Developer mode in Windows. That’s done in settings on the box running the POS
Start the POS and hit F12 to enable the developer aid
In the bottom of the console type in Commerce.Config.isDebugMode=true and press Enter
Go to your POS settings to enable the Developer mode flag in here.
This will make some things way easier. Notice, that when done like this it is only for the current session. Doing it in the pos.js file-way is permanent.
While testing MPOS changes I had to do an uninstall on my laptop. But every time I tried to uninstall it told me that there was an error and it couldn’t complete the uninstall and that I should contact the administrator.
And then it reappeared in the list of installed apps.
Trying to run the Uninstall-RetailModernPOS.ps1 gave a hint of what’s wrong:
You’ll usually find the script around here:
C:\Program Files (x86)\Microsoft Dynamics 365\70\Retail Modern POS\Tools\
There might be some clever way of fixing this, but in order to move forward I did a quick’n’dirty and not recommended way of fixing it:
Remove the check …
Edit the script by commenting out this line:
This is not recommended and definitely not in a production environment and I do not take any responsibility for any undesired outcome of this. But it did the trick for getting me forward.
Please note, that this doesn’t take away the error. So when you uninstall the next time it’ll still throw the error at you until you once again remove the check.
Normally when I need the table browser in Dynamics 365 I use a Chrome extension called “Table Browser Caller for D365FO“. Often you end up working in Incognito mode when having to access environments with a different AAD account. That requires you to make it available in Incognito mode:
BUT … what the extension does isn’t magic. What it does however is offering a very easy approach to building an URL that I never can remember. And when working in a browser without that extension you can write the URL change yourselve. So I figured that if I wrote it here I might remember it better or at least help somebody else remember it.
Add this to the URL to get the table browser: &mi=SysTableBrowser&TableName=. This will give you something like this:
Notice, that the table browser is being changed in a couple of areas compared to AX 2012. This means that changing data through the table browser is not allowed in production environments for example. Nice in regards to data consistency, but missed when having to dirty-fix data. 🙂