TechTalk

This post is now hosted at this  link .

Just a short but nevertheless important post. I discovered this document AX7 Retail Handbook while browsing my LCS deployed AX 7 RTW VM Retail SDK folder. Overall the document is made up of two parts. The first covers the Retail Sdk, build, configurations that can be done to be more productive. Additionally, typical branching strategy is discussed in order to work effectively in teams. The second part contains details about the main extensibilities that are possible with the Retail Sdk. Anyone getting started with writing code against the Sdk can use it as a reference in order to get started. Some sample extensions are also provided in the same folder path. Kudos to the team at Microsoft for going the extra mile to provide this document and sample extensions. PS: If you have access to the LCS Deployed VM please access these materials there, I would not be in a position to share these as copyrights apply.   Update -   These documents have been discussed...

Recently i needed to move my configuration from one environment to another. I expected it to be easy thanks to the Data Entities available in AX 7. However being the first time to do this it was a bit of a pain. First off it took me a while to locate the Data Entity I wanted to use. As its a long list I tend to apply a filter "Retail" to my the list of Data Entities.However turns out that they have a I should have used the filter "POS".  In order to move the screen layouts few important entities are the POS Button Grid, POS button grid buttons, and the  POS screen layout button grid zones  . These hold the definitions of the grids displayed in your POS screen layout, buttons (which trigger functionality in the POS) within them and the  grid zones  assigned to those screen layouts.  Another issue is assigning the images associated with the buttons. If the images on your environments have different indexes , you need to again associa...

Just a short post w.r.t Distribution Jobs that sync data from AX HQ to your Retail Channels, if you notice that the Distribution Jobs are not running for quite some time, you may want to check if the following service is running on the AX machine.  Since the distribution jobs executes as a batch job on the AX server, this service is responsible for executing these jobs. 

Hi All, I aim to achieve three things with this post, i.e. to demonstrate 1. How we can execute a test job in AX7 which most of us already know in the good old AX 2012 as an AOT Node.  2. Use of like operator in AX uses asterik '*' instead of '%' which we use in SQL 3. Changing Layouts of Retail Screens need not be tedious and time consuming by changing properties of each button manually. Article updated and moved here -Hitesh Manglani

Hi All, I recently had to add a Blank Operation to Modern POS (MPOS) to open a url from MPOS. Blank Operation as you may already be aware enable you to extend Microsoft Dynamics Retail for POS by adding custom logic that can be triggered from the Retail POS Register buttons. The way to implement Blank Operations in MPOS  is different from Enterprise POS as MPOS is a modern app as compared to EPOS which is a windows forms based app. So lets explore a very simple customization i.e. we want to open a URL on triggering a button from MPOS. 1. We would need to start with AX to add a button to the layout of MPOS. If you do not want to disturb the standard layouts its better to copy one of the existing layouts and then modify it using the designer. Please note the designer only opens in Internet Explorer so it will save you time by not trying to open it in other browsers e.g Chrome 2. Next we need to add this layout to the Store where we intend to use it...