Testing a Cayan Genius Device

First things first. You’re going to need  to download Cayan’s Genius POS Emulator. Ensure that you are on the client’s site and part of their domain.

  1. Extract the downloaded file and open the application.
  2. Open the application Settings and enter information as shown below. merchant-settings.png
  3. Enter the IP Address of the Cayan Genius device. Leave the port number, target path, and format as shown.


    The IP address can be found on the device. Depending on your network settings, this may be a static IP address, or if DCHP is enabled, the device will choose it’s own IP Address.

  4. Gift card settings giftcard-settings1.png
  5. Sale settings sale-settings.png
  6. For Version Settings, set Initiate to v2. Version-Settings

Now you should be able to make a “sale.” To begin, click the Start Order button. They Cayan Genius device will be triggered and the screen will change. Add items to the order, and the Genius begins to act as an item line display. To take payment, click Sale and swipe/insert/tap a credit card. emulator-e1492639114372.png

MPOS Declare Start Amount Error

Earlier today my colleagues and I were seeing a very non-descriptive error (as the MPOS is becoming infamous for). The error read: “We cannot process your request at this time. Please try again later.”

Thanks, MPOS! I will! I will try again later!

After additional investigation of event logs, I noticed that there was a problem with TENDERTYPE on the RetailTransactionPaymentTrans table.

Cannot insert the value NULL into column ‘TENDERTYPE’, table ‘RetailSunsetStore.ax.RETAILTRANSACTIONPAYMENTTRANS’; column does not allow nulls.

INSERT fails.

Bummer. OK so what this means from a functional point-of-view is that the tender types of the retail store’s payment method is incorrectly setup.

The fix:

First we set up a new Payment Method on the store of type Tender Remove/Float


Next, on the Retail Store, under Miscellaneous, Payment Method must be set to Tender Remove/Float.


Then run the 1070 data distribution job to push the changes to the store database.

AX 2012 Retail SDK Eating Your Hard Drive Space?

After I installed the Retail SDK for Dynamics AX 2012 CU10 on a virtual machine for testing purposes, I was amazed at how fast my hard drive space started disappearing. It was obviously very frustrating. Here is what the problem ended up being:

There is a retail service that can grow several gigs in a matter of minutes. It’s honestly pretty amazing…in a bad way.

Open up Services and search for Microsoft Dynamics AX for Retail Offline Sync Service. Disable this service. Possibly because I don’t have everything configured yet, but what was happening was every time the service attempted to sync, it failed. When it failed a log file grew.

Here is the log file that you can delete to free up some space:


Massive 56gb file!

By deleting “C:\Program Files (x86)\ Microsoft Dynamics AX\ 60\Retail POS\RetailOffline\RetailOfflineSyncTrace I freed 56 gigs of storage!

I hope this helps some of you out! Obviously some of you are going to need this file for your own purposes. Personally I didn’t need any of these error messages taking up my hard drive space. So as always, delete at your own risk.

AX 2012 Retail SDK Missing Component References

After installing the AX 2012 R3 CU10 Retail SDK, I opened the Blank Operations VS C# project. After building the solution, I received 2049 errors! It’s gonna be long day, I thought. Here is If you run into this error, here is what you need to do:

Go to each individual project that is missing references in the DevExpress* and SystemSettings DLLs. You will see yellow warning symbols next to the broken references. The screenshot below was taken after I fixed the issue, so you will have to imagine the warnings.

Right click on the project, in this case BlankOperations, and select Properties.

Solution Explorer Properties

Solution Explorer Properties

Now select Reference Paths and add the following location:

C:\Program Files (x86)\Microsoft Dynamics AX\60\Retail POS\

Click Add Folder.

Reference Paths

Properties > Reference Paths

Those missing references should now appear visible to the project.