• Back Office Steel City
• Retail Back Office Software
• Back Office Usborne

Is focused on meeting the challenges of a retail environment that is constantly evolving. Customers have more information at their fingertips than ever before. Whether browsing online, interacting through social networks or shopping in-store, customers demand a seamless and consistent experience.

The new Dynamics AX 7 arms employees with the tools they need to deliver superior customer service. Here are five key features of Dynamics AX 7: 1. Order management and payment processing POS-based order support tools allow on-the-spot creation of orders and quotes. Total visibility of business processes facilitates price and inventory checks, management of inventory reservations, and the acceptance, fulfilment and tracking of standard and special orders. Microsoft Dynamics AX 7 supports all credit and debit card features of Dynamics AX for Retail 2012 and has added new capabilities. It supports plug-and-play and semi-integrated cross-channel payment processing by using the payment SDK. Social integration Dynamics AX 7 facilitates an integrated, omni-channel customer experience.

With Azure machine learning capability, the new Dynamics AX 7 intelligent predictive technology allows you to take full advantage of customers’ social interactions. Enhanced social insights enable better targeting of promotions and discounts. Trends that impact your brand can be detected and piggybacked. Modern Point of Sales (MPOS) Dynamics AX 7 introduces a cloud-based POS that is optimised for mobile and tablet.

Instant access to customer intelligence allows sales assistants to make more informed recommendations and guide customers in their purchasing decisions. MPOS consolidates all customer data, including sales history, wish lists, purchase patterns and preferences. It manages transactions, gift and loyalty processing, as well as inventory receipt, reporting and stock counts. Retails workspaces The new Workspace feature centralises all the tasks, actions, data and people needed for specific roles. Dynamics AX 7 comes with built-in retail Workspaces, such as the Category and product management workspace. This has the functionality of assortment management, assortment life cycle and tracking.

Other Workspaces include the Prices and discounts workspace, the Channel deployment workspace, and the Channel operations workspace. Catalogue management Catalogue management in the new Dynamics AX 7 brings numerous new tools and enhancements. Specific catalogue pricing, related call scripts and linking to multiple targeted mailing lists are all centrally and easily managed. A catalogue manager can tie specific key codes or source codes to a catalogue which can be linked to the sale order in entry, providing insight into promotional response rates. The new productivity enhancing Workspace for catalogues brings together in one place all tasks and processes related to active catalogues and facilitates easy catalogue life cycle tracking. These are just a fraction of the rich tools and features offered in the new Dynamics AX 7. The latest generation of Microsoft’s flagship enterprise resource planning solution enables you to place all your retail processes on a single, unified platform.

Microsoft Dynamics AX 2012 R3 gives organizations an exceptional. Process waves: automatic, manual, batch time scheduled, filtering and. Import the edited forecast back into Microsoft Dynamics AX. Clienteling, real time inventory look up, as well as back office capabilities. Coming H2 C 2014 and H1 C 2015.

It provides a real-time view across your entire organisation. With Power BI now integrated as the native business intelligence, more than 30 back-office reports and 10 channel-side reports deliver clear, actionable information to the right people at the right time. The new role-tailored Workspaces drive productivity, and the browser-based client offers a familiar interface that is easy to learn and operate.

• Feb 13, 2015 - Watch this video to see how Microsoft Dynamics AX human resources. Effective, reliable, cost-conscious back-office solutions ensure their. Microsoft Dynamics SL 2015 Capabilities Guide Excerpt: For more than 25 years,.
• Jun 16, 2017 - Connector for Microsoft Dynamics AX consists of two separate installers. Dynamics 365 for Retail environment will be used as the back-end infrastructure for. For Microsoft SQL Server 2014, Service Pack 2 must be installed. It's critical that you review security guidelines for IIS and PCI requirements.

Install N-1 components for use with Microsoft Dynamics 365 for Retail. 15 minutes to read. Contributors.

In this article This topic explains how you can use self-service to configure Connector for Microsoft Dynamics AX (previously N-1) in Microsoft Dynamics 365 for Retail headquarters, download it, and install it on the domain computers of a Microsoft Dynamics AX 2012 R3 environment, so that it can be used by previously deployed and running stores. Connector for Microsoft Dynamics AX consists of two separate installers. One installer is for the Retail Async Server Connector service, and the other installer is for the Real-time service for AX 2012 R3. When the installation is completed, a Microsoft Dynamics 365 for Retail environment will be used as the back-end infrastructure for currently installed and working stores that contain Enterprise POS and Retail Modern POS from AX 2012 R3. This topic also explains how to uninstall and troubleshoot these installations. Before you begin. Important To help maintain a high level of security across the company, we strongly recommend that you create a new client ID and secret for this installation.

This step requires a new Web App. Generate a Microsoft Azure Web App to create a client ID and secret. For instructions, see the 'Basics of Registering an Application in Azure AD' section in. After you've created a client ID and secret for Connector for Microsoft Dynamics AX, the client ID must be accepted in Retail. Go to System administration Setup Azure Active Directory applications. Enter the client ID in the Client ID column, enter descriptive text in the Name column, and enter RetailServiceAccount in the User ID column.

Configure Connector for Microsoft Dynamics AX To configure Connector for Microsoft Dynamics AX, complete the procedures in all sections of this topic through the 'Running the Connector for Microsoft Dynamics AX installers' section. Use Azure Active Directory (Azure AD) credentials to sign in to the Retail headquarters or Retail trial. On the Welcome page, use the menu in the upper left to go to Retail Headquarters setup Retail scheduler Connector for Microsoft Dynamics AX. On the Action Pane, select New.

In the Profile field, enter a unique value. Under Real-Time Service location, in the Server field, enter the server URL where the Real-time service for 2012 R3 will be installed. Note Use can either use the same location where the current Real-time service was originally installed, or you can specify a new location. In the Port field, enter the port that the new Real-time service for AX 2012 R3 should use. In the Web application name field, enter the web application name that should be used in Internet Information Services (IIS). By default, RetailCDXRealTimeService is selected. In the Protocol field, select the protocol that the original Real-time service currently uses.

Note Although we recommend that you use HTTPS, net.tcp is listed for better support of previous installation scenarios. Under Connection information, in the Common name field, enter the friendly name of the certificate that the Real-time service for AX 2012 R3 should use. Together, this value and the value of the Passphrase field enable connections to the original Real-time service and the new Real-time service for AX 2012 R3.

In the Language field, select the language that the associated stores should use. On the Action Pane, select Save. On the Action Pane, select Retail scheduler parameters. You can now enter the details for the Async Server Connector service. Under HQ Message Database, in the SQL Server instance name field, enter the instance name of the Microsoft SQL Server that should be used. In the Server name field, enter the fully qualified domain name (FQDN) of the computer where SQL Server is used. Note In AX 2012 R3, the default value was HQMessageDB.

Back Office Steel City

On the Action Pane, select Save. Go to Retail Headquarters setup Retail scheduler Channel data group. Select the Default data group or the data group that is associated with the channels in your previous installation set (N-1 channels that used Enterprise POS and Modern POS from AX 2012 R3). On the Action Pane, select Full data sync. In the Select a distribution schedule field, select job 9999, and then select OK. In the dialog box that appears, select OK to confirm the full synchronization. All the data in the channel database is prepared for download.

Download the Connector for Microsoft Dynamics AX installers. Use Azure AD credentials to sign in to the Microsoft Dynamics Retail headquarters or Retail trial. On the Welcome page, use the menu in the upper left to go to Retail Headquarters setup Retail scheduler Connector for Microsoft Dynamics AX. In the list of connectors on the left, select the connector that you created earlier for this installation. On the Action Pane, select Download. On the drop-down menu, under Async Server Connector service, select Configuration file. Note Before you run the Connector for Microsoft Dynamics AX installers, make sure that the following requirements are met:.

Retail Back Office Software

The installer requires that the Microsoft.NET Framework version 4.5.1 be installed on the system. The installers install the Connector for Microsoft Dynamics AX applications only on the following operating systems.

Before you install any component, you must update the operating system with all service packs and updates that are available for it. Windows 7 Professional, Enterprise, or Ultimate edition (both x86 and x64 architectures). Home edition and Embedded edition aren’t supported. Windows 8.1 Update 1 Pro or Enterprise edition (both x86 and x64 architectures). Standard edition isn’t supported. Windows 10 Pro or Enterprise edition (both x86 and x64 architectures).

Home edition isn’t supported. Windows Server 2012 R2 or Windows Server 2016. The Connector for Microsoft Dynamics AX installers first extract the associated files and then begin the installation. Async Server Connector service. The installer validates that all prerequisites are met. These prerequisites include SQL prerequisites, such as a local installation of SQL Server, or the alternative prerequisites, such as SQL Command Line Utilities and other required SQL connectivity installations.

Note. To meet prerequisites, the SQL Server that is connected to must have Full-text search and, at a minimum, support for Transport Layer Security (TLS) 1.2.

For Microsoft SQL Server 2012, Service Pack 3 must be installed, at a minimum. For Microsoft SQL Server 2014, Service Pack 2 must be installed. If a system restart is required, the installer shows this requirement. Although the restart is recommended, the installer can continue without it. Verify the Application Object Server (AOS) URL (the URL that is used to access Retail headquarters), and then select Next. Note The certificate must use private key storage, and server authentication must be listed in the enhanced key usage property. Additionally, the certificate must be trusted locally, and it can’t be expired.

It must be stored in the personal certificate store location on the local computer. If a specific user is required, enter the user name and password that the service should run as. By default, the installer automatically generates a service account to use. This approach is more secure and is recommended, but it can't be used when the database is located on a separate computer.

Select Next to continue. Verify the HTTPS port that should be used, and verify that the host name of the computer is correct. Select Next to continue. Note. The HTTPS port is listed in the Store system profile. To access the Store system profile, on the Retail store details page, on the Store systems FastTab, select the profile ID of the selected Store system.

The installer automatically enters the host name. If, for any reason, the host name must be changed for the installation, change it here. The host name must be the FQDN of the system, and it must match the value that you entered on the Connector for Microsoft Dynamics AX page in the previous section of this topic. Enter the application ID (client ID) and secret that are associated with this Connector for Microsoft Dynamics AX installation. Additionally, verify the channel database ID, which is automatically entered from the configuration file.

Then select Install. Note. For information about how to correctly generate an Azure Web App to create a client ID and secret, see the 'Basics of Registering an Application in Azure AD' section in. When you create the Web App, the initial URI and URL don't have to be any specific value.

Only the application ID (client ID) and secret that are created are important. After the installation is completed, the final health page appears. This page shows whether the installation was successful. It also shows the health of each component, based on basic connection tests, and the location of this topic. If the installation wasn't successful, the page shows the location of the log files. After an application ID (client ID) and secret are created, the application ID must be accepted in Retail. Go to System administration Setup Azure Active Directory applications.

Back Office Usborne

Enter the client ID in the Client ID column, enter descriptive text in the Name column, and enter RetailServiceAccount in the User ID column. Add the client ID to the Retail shared parameters page in Retail. In Retail, go to Retail Headquarters setup Parameters Retail shared parameters. Select Identity providers. On the Identity providers FastTab, select the provider that begins with HTTPS://sts.windows.net/.

The values on the Relying parties FastTab are set, based on your selection. On the Relying parties FastTab, select +Add. Enter the client ID that was created for this installation. Set the Type field to Public and the UserType field to Worker. Then, on the Action Pane, select Save.

On the Action Pane, select Save. When you've finished, return to the application installer, and select Finish. Note The certificate must use private key storage, and server authentication must be listed in the enhanced key usage property. Additionally, the certificate must be trusted locally, and it can’t be expired.

It must be stored in the personal certificate store location on the local computer. If a specific user is required, enter the user name and password that the application pool should run as. By default, the installer automatically generates a service account to use. This approach is more secure and is recommended, but it can't be used when the database is located on a separate computer. Select Next to continue. Verify the HTTPS port that should be used, and verify that the host name of the computer is correct. Select Next to continue.

Note. The HTTPS port is listed in the Store system profile. To access the Store system profile, on the Retail store details page, on the Store systems FastTab, select the profile ID of the selected Store system. The installer automatically enters the host name. If, for any reason, the host name must be changed for the installation, change it here. The host name must be the FQDN of the system, and it must match the value that you entered on the Connector for Microsoft Dynamics AX page earlier in this topic. Enter the application ID (client ID) and secret that are associated with this Connector for Microsoft Dynamics AX installation.

Then select Install. Note. This application ID and secret can be the same application ID and secret that you used in the Async Server Connector service installation. For information about how to correctly generate an Azure Web App to create a client ID and secret, see the 'Basics of Registering an Application in Azure AD' section in. When you create the Web App, the initial URI and URL don't have to be any specific value. Only the application ID (client ID) and secret that are created are important.

After the installation is completed, the final health page appears. This page shows whether the installation was successful.

It also shows the health of the component, based on basic connection tests, and the location of this topic. If the installation wasn't successful, the page shows the location of the log files. If the application ID and secret aren't the same as the application ID and secret that you used for the Async Server Connector service, the application ID must be accepted in Retail. Go to System administration Setup Azure Active Directory applications. Enter the client ID in the Client ID column, enter descriptive text in the Name column, and enter RetailServiceAccount in the User ID column. If the application ID and secret aren't the same as the application ID and secret that you used for the Async Server Connector service, you must add the application ID (client ID) that was created for this installation to the Retail shared parameters page in Retail.

In Retail, go to Retail Headquarters setup Parameters Retail shared parameters. Select Identity providers. On the Identity providers FastTab, select the provider that begins with HTTPS://sts.windows.net/. The values on the Relying parties FastTab are set, based on your selection. On the Relying parties FastTab, select +Add.

Enter the client ID that was created for this installation. Set the Type field to Public and the UserType field to Worker. Then, on the Action Pane, select Save. On the Action Pane, select Save. When you've finished, return to the application installer, and select Finish. Note If the installer doesn't show a check mark for the component, wait 10 minutes, so that any cached values can be updated in the cloud. Then check again.

If the installer still isn't fully successful, run a full synchronization on the distribution schedule that this installation uses. Help secure the Connector for Dynamics AX applications According to current Payment Card Industry (PCI) security standards, the following options should be set in a production environment:. You should completely disable SSL (v2 and v3) on the computer. You should enable and use only TLS version 1.2 (or the current highest version). Note.

By default, the installers don't change these settings. (In this respect, these installers differ from other Self-service installers). To edit or enable these settings, follow these steps:. Press the Windows logo key+R to open a Run window. In the Open field, enter Regedit, and then select OK. In the User Account Control window, select Yes (if this step is required), and then, in the new Registry Editor window, go to HKEYLOCALMACHINE System CurrentControlSet SecurityProviders SCHANNEL Protocols. Important It's critical that you review security guidelines for IIS and PCI requirements.

Troubleshoot the Connector for Microsoft Dynamics AX applications This section will be more thorough in the future. For now, here is a checklist of things to verify:. In Retail, on the Retail shared parameters page, verify that the correct client ID has been added on the Relying Parties FastTab. In Retail, verify that every client ID that was created exists on the Azure Active Directory applications page. Uninstall the Connector for Microsoft Dynamics AX applications Use Control Panel in Microsoft Windows to uninstall Retail Store system.

Press the Windows logo key, and then enter Control Panel in the search box. In the search results, select Control Panel. In Control Panel, select Programs Uninstall a program. In the Programs and Features window, select Microsoft Dynamics 365 for Retail Store system, and then, above the list of programs, select Uninstall. Wait for the uninstaller to finish removing the program.