Store connect - IDispatch error #3119: Violation of PRIMARY KEY

If you are running the N-jobs to move over data to the POS, and following error occurs in the store connect
IDispatch error #3119:Violation of PRIMARY KEY constraint 'I_20137STAFFIDX'. Cannot insert duplicate
key in object 'dbo.RBOSTAFFTABLE'. 2011-08-16
07:34:53.000
N-1060

The cause is that in the Transfer field list:
(Retail Scheduler/Subjobs/Setup/Transfer Field List)
The Field Type on all To Fields are set to = None

How it suppose to look is illustrated below:

 
If you read the fields with store connect from the menu
(Retail Scheduler/Distribution location/Functions)
Then all field types are restored to the correct values.

Buttons in the POS layout are not all localized.

Buttons in the POS layout are not all localized.:

Buttons in the POS layout are not all localized.
The text is displayed in English only
Here is a preview from the POS till layout




Solution:
Modification needed to change the label of the ”fixed” image
button.
Step by step example

1. Go to the AOT/resources  and find  RBO_Image_110_png
2. Open the resource file and press export

       3. Edit the files with example a picture editor



      4. Go to the Retail Headquarters/Setup/RetailPOS/Button Grid
      5. Choose Payments and press the designer button
      6. Mark the Currency and click on the Button properties
      7. Right click and go to main table on the PictureID (110)
      8. Press select and mark your changed picture file and ok
      9. The result is like this
 


         10. Go now to the Retail Scheduler and replicate the N-1090 Terminals job
         11. Log into POS
The result is that the button now changed.

How to Monitor Retail Store Connect messages

Configure upload options

1. Click Retail scheduler > Setup > Store integration > Retail Store Connect upload options.
2. Configure how frequently you want to upload Retail Store Connect messages and which Retail Store Connect messages to upload. You can decide to upload all messages or just error messages.
3. Click Retail scheduler > Setup > Store integration > Retail Store Connect profile.
4. On the Configuration tab, in the Retail Store Connect upload options field, assign the upload options that you specified in step 2.
5. Click Functions, and then click Send configuration.

View, cancel, and delete messages

1. Click Retail scheduler > Periodic > Store integration > Message status.
   
   You can view all the messages in the message database. You can also cancel any messages about errors. Messages about errors might affect performance.
2. Click Retail scheduler > Periodic > Store integration > Delete messages

How to access multiple POS from one machine

Update the POS.EXE configuration file (original text further down on the page).
In addition to the original description, I want to provide the example file and what you will see at the POS when you start it.

Example File POS.EXE.CONFIG
<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <section name="AXRETAILPOSW7" type="LSRetailPosis.Settings.ConfigFile.AppConfiguration, SystemSettings, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
        <section name="GTSCLAB" type="LSRetailPosis.Settings.ConfigFile.AppConfiguration, SystemSettings, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
   </configSections>
    <AXRETAILPOSW7 LocalConnectionString="Data Source=LOCALHOST;Initial Catalog=AxRetailPOS;Integrated Security=SSPI;Persist Security Info=false;Pooling=false;TrustServerCertificate=true;Encrypt=TRUE"
        StoreId="S0002" TerminalId="0003" DatabasePhysicalFilePath="C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\"
        DATAAREAID="CEU" UseSnapshotIsolation="true"/>
    <GTSCLAB LocalConnectionString="Data Source=GTSCLAB-dk;Initial Catalog=AxRetailPOS;Integrated Security=SSPI;Persist Security Info=false;Pooling=false;TrustServerCertificate=true;Encrypt=TRUE"
        StoreId="S0001" TerminalId="0001" DatabasePhysicalFilePath="C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Data\"
        DATAAREAID="CEU" UseSnapshotIsolation="true"/>
</configuration>

Result:
It is now possible to connect to a different configuration / POS database


POS Technical Reference.pdf

Controlling startup

Starting
Microsoft Dynamics AX for Retail POS can be controlled by the config file and
startup parameters.

The config file

The
config file is an XML file whose file name is POS.exe.config. It is located in
the same directory as the EXE file. The config file is constructed as follows:

<?xml version="1.0"
encoding="utf-8"?>

<configuration>

<configSections>

<section name="FirstSection"
>

<section
name="SecondSection" >

</configSections>

<FirstSection
LocalConnectionString=" " LocalUserName=" "
LocalPassword="" .. other variables>

<SecondSection
LocalConnectionString=" " LocalUserName=" "
LocalPassword="" .. other variables>

</configuration>

As
shown above, the config file can have one or more sections specified within the
configSection tag. Each section must have its own tag and can have the
following parameters:

LocalConnectionString

Tells
Retail POS about the connection string. A typical connection string is shown in
the example config file above.

LocalUserName

Stores
an encrypted user name that connects to the database if integrated security is
set to false in the connection string. An unencrypted name can also be put
directly into LocalConnectionString.

LocalPassword

Stores
an encrypted password for the person who connects to the database; if
integrated, security is set to false in the connection string. An unencrypted
password can also be put directly into LocalConnectionString.

RemoteConnectionString,
RemoteUserName, and RemotePassword

Not
used by Retail POS. Retail POS Technical Reference Controlling startup 2

StoreId

The ID of the store. Because a number of settings are
store-related, changing the store ID can result in an error if related store
data is missing.

TerminalId

The ID of the POS register. When Retail POS starts, the
terminalID of the config file must match an entry found in the
RBOTerminalTable. Otherwise, an error occurs.

DataAreaId

This parameter equals the field DATAAREAID found in most of
the tables in the database. This field makes it possible to start Retail POS
with different data, depending on the dataareaid.

DatabasePhysicalFilePath

When Retail POS starts and no database is found, a database
is created. If you must create the database using a path other than the default
path, you can specify it in the parameter DatabasePhysicalFilePath.

UseLocalSqlExpress

If this is set to true, Retail POS does not install
Microsoft SQL Server Express.

What is Dynamics AX for Retail?

Main features of Microsoft Dynamics AX for Retail

Microsoft Dynamics AX for Retail is a comprehensive solution with  all the store components necessary to mange transactions, customer loyalty and payment processing; a headquarters module to handle assortments, replenishment, pricing and promotions; and ERP capabilities to handle warehouse and logistics and back end processes.

From sales to supply, you can create transactions, track sales, understand consumer behavior, manage inventories, reduce shrink and improve overall operations.  You can gain visibility across the entire enterprise, as well as connect with your local sites and your supply chain to grow your business and set you apart from the competition.

 

Centralized Store Management

Microsoft Dynamics AX for Retail can centrally manage stores and POS terminals from back office. Currency, account and item masters to be used in transactions, roles and permissions of store staffs and hardware configuration including POS visual profiles and screen layouts can be all setup from back office. Centralized management helps ensure critical updates across the organization: configurable, flexible inventory and financial updates, sales order payments, gift card usage, and issuance and usage of loyalty points. In addition, journal entries with dimensions are automatically generated by daily closing and transferred to back office. Employees at back offices can view the updated sale information by store, POS terminal, sales person and item and so on.

 

Flexible POS

Purpose-built POS components are integrated into Microsoft Dynamics AX for Retail. POS user interface can be optimized for store roles with graphical “drag and drop” designer for improved productivity and customer service. AX Retail POS can work offline, ensuring that your stores remain fully operational during network interruptions. All data is automatically updated when the connection is restored.

AX for Retail – Import Logs operation fails when run in batch

As part of the process to receive a purchase order from the POS client the Import Logs operation needs to run.  When performing an Import Logs operation in batch, the process will always fail.  The reason this fails is that one of the methods attempts to update the Import Logs form, which is not present when running in batch.  In order to allow the batch processing, make the following changes to \Classes\HHTProcessImportLog\runEnd

protected Integer runEnd()

{

;

    this.updateBlock(HHTImportStatusTypeBase::Processing,HHTImportStatusTypeBase::Ended);

  if (!this.isInBatch())

  {

    if (formHasMethodBookRefresh == unknownNoYes::Unknown)

        formHasMethodBookRefresh = formHasMethod(this.formRunObject(),identifierStr(bookRefresh)) ? unknownNoYes::Yes : unknownNoYes::No;

    if (formHasMethodBookRefresh == unknownNoYes::Yes)

        this.formRunObject().bookRefresh();

  }

    return 0;

}