Table browser in Dynamics 365

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:

Extensions

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:

Table_browser

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. 🙂

Advertisements

Why my product images doesn’t show up on my eCommerce site

So here’s the scenario. We’ve got the POS running and the eCommerce site too; but somethings wrong with the product images. They’re not showing up on the eCommerce site. No matter how many times we restart the IIS and change the images on the media server. The thing is that the eCommerce site doesn’t pull the images from the media server. At least not for the products, that is.

So looking at these sunglasses we get the image of the sunglasses as expected:1 POS product image.png

Looking at the media server path here’s the image:

2 Image file on media server.png

Now we add a new image to the media server like this:

3 New image on media server.png

It’s ok to go “aaaawwww”…

Looking at the POS it picks up the change pretty fast and shows us two images:

4 New image on POS.png

If we go the the eCom site not much happens:

5 Image not shown on eCom.png

You can restart the IIS all that you want, it won’t change.

Here’s the explanation:

6_Folder_difference.png

The eCom site looks for the files in another folder than the POS. This opens up for having different levels of image resolution and so on, but that is another story.

So if we copy the image files to the Retail Storefront folder we might be out of the woods … but not quite.We still only see the old image on the site, thanks to caching.

Clear your browsers image cache and bingo: another moment of aaaawwwwww:

8 New image shown on eCom.png

This all might be documented somewhere … I just didn’t find it.

Retail operations and user rights

In this post I will do a quick explanation of the user rights setup of the retail POS operations.

Operations is referring to the different actions available in the POS. They are listed in Retail and commerce/Channel setup/POS setup/POS/Operations. Each operation has the following information:

Operation id and Operation name identifies the operation.

Permission ID 1 and Permission ID 2: These permissions can be a required level of rights needed for the operation.

Check user access: If not set the operation does not require the user to have the required access.

User operation: If not set you cannot create a button on the POS for that operation. Notice that the form by default has a filter on that field requiring the field to be set true.

Confused? Let’s have a look at an example.

We are going to focus on the void product operation using worker 000120 (Andrew Lan) and 000110 (Dan Park). Dan is allowed to void transactions:

danp-pos-permissions

Andrew is not:

andrewl-pos-permissions

Scenario 1:

Check user rights = true

Permission IDs = 0

Andrew tries to do a void:

void-transaction-not-allowed

Since Andrew has limited rights he cannot void the transaction.

 

Scenario 2:

Check user rights = false

Permission IDs = 0

In this case the POS doesn’t care what about permissions when voiding transactions so it allows Andrew to void:

void-transaction-prompt

 

Scenario 3

Check user rights = false

Permission IDs = 1001 (Allow transaction voiding)

Like in scenario 2 the POS still doesn’t care about user rights so it allows Andrew to void the transaction:

void-transaction-prompt

Scenario 4

Check user rights = true

Permission IDs = 1001 (Allow transaction voiding)

The user rights are validated again and since Andrew isn’t allowed voiding he can’t do the void. But now we have added the feature that Andrew can call in his manager or anyone else with enough rights to allow transaction voiding:

cannot-void

In this case he gets Dan to type in his id and password and this opens up for voiding the transaction:

void-transaction-prompt

 

Peripheral Simulator in new release of Dynamics 365 Operations

With one of the latest releases of Dynamics 365 Operations we have the option of simulating hardware peripherals like printers, cash drawers and so on.

The idea is to allow the user to simulate the flow of the retail processes including printers, drawers, scales, payments and so on but without having to occupy your co-workers desk piling up all of your retail hardware.

Here is what you need to do. Start by going to the hardware profiles. In the demo data a new profile has been added called Virtual. It has been set up with a profile that will work pretty much out of the box.

Besides the data a new button has been added allowing the download of the simulator:

hardware-profile-and-download-button

The simulator download hasn’t received the prettiest name, but that aside it is working great.

peripheralsimulator

The installer is very much a next-next-next installer and does not require any action taken unless you have specific wishes regarding installation folder.

Once installed you get this new application:

retail-peripheral-simulator

Already at this point we get an idea of what to expect. But before getting everything up and running you need to do a couple of more things.

First, we need to tell the store that the hardware station should use the new hardware profile:

hardware-profile-o

Run your 1070 and 1090 jobs (depending on which setup changes you made).

Now, starting up the POS you might end up with a series of hardware station errors that could look something like this:

hardware-station-error-3hardware-station-error-2comm-error-cash-drawer

To get passed this we should shortly touch upon how this works. According to the hardware profile we are using all communication is OPOS based so we need to get that onboard our POS machine as well. I used this one that previously was recommended during the installation of the POS software: Link to OPOS software

With that done you should be ready to start up your POS. You might have to manually go in and enable the use of the hardware station.

So first test could be a safe drop. In this case I pull out 10 USD:

make-safe-drop

That leaves a safe drop receipt in the printer:

safe-drop-receipt

And the drawer needs to be closed again:

cash-drawer-open

Click the Close drawer button to close it:

cash-drawer-closed

Let’s sell something. In this case a shirt:

transaction

I would like to pay this with a credit card so I switch to my simulator and select the MSR.

no-card-created

Click the + button to create new card:

create-master-card

The number is found on this page: credit card generator

Next step is to click the Pay card button in the POS followed by the Swipe card button in the Simulator. This adds the card info to the tender information in the POS:

card-details-in-pos

Completing the transaction you get a receipt in the printer:

receipt-from-transaction

This will definitely change the way we make demos of the POS with Dynamics 365 Operations.