Friday, December 25, 2015

Duplication of Receipt number in LS Retail Transactions | Microsoft Dynamics Nav

duplication of receipt number in ls retail microsoft dynamics nav

Have you ever come across a situation when you find that your Receipt Number has been duplicated in Transaction Header or Trans. Sales Entry table in Navision?

It is strange to find out but it is true that this is a bug in LS Retail. The reason for this bug can be from one of the following reasons:
  • The major reason of duplication of Receipt number is due to the dependency on the LSRetail.ini file which is located on a specific path of the system provided in the Retail Setup table. The other reasons are related to this LSRetail.ini file.
  • It can occur because of the failed suspension action, because that is the only action the is interfering with how receipt numbers are issued.
  • The duplication of Receipt number is occurring after the suspended receipt number has been retrieved from the POS Transaction table.
  • The LSRetail.ini file is overwritten between getting the new unposted Receipt number and writing the last Posted Transaction in Transaction Header.
  • There was error writing to the LSRetail.ini file due to an issue with the permission of writing in the drive where the file is located.

Workaround for the issue

There are two workaround solutions to this problem of duplication of Receipt numbers:

  • First one is to customize the database and introduce a new field for the Receipt number i.e Posted Receipt Number in the tables. This new Posted Receipt number is generated without any dependency on the LSRetail.ini file. What else we must do for this customization:
    • Create a Number Series for the Posted Receipt number.
    • Write code in the EPOS Main to increment the number series with 1 and store it to the POS Transaction and POS Trans. Line Table only when the transaction has been totaled. This way the Receipt number is generated only for the completed transactions.
    • Also, write code in the POS Post utility to transfer the new field data from POS Transaction table to the Transaction Header table and other related tables. 
  • Second option is to use the LS Navision POS use the POSSESSION (single instance) codeunit to store the Last Receipt number, which is the INI file used to have i the previous versions, instead of reading the last Receipt number from the table.

Suggestions, comments and questions are most welcome!


  1. Thank full , EPOS he was new Way to help to us to get the business running sucessfull.

  2. fantastic post. epos Its pretty interesting article, love this kind of post...

  3. Its good and informative post, gives a lot of knowledge. retail epos i would like to see more from you....

  4. Thanks for some good retail epos write post ups. like to see more from you.

  5. Thanks for sharing the important points of view with us. retail epos It is really very nice blog.I will be waiting for your further write ups thanks once again.

  6. Thanks for posting epos software for retail your valuable thoughts with us & our readers. Thank You

  7. Thanks for good post.emperium epos software for retaillike to see more from you.I really like it.

  8. I finnally found nice blog, epos system Thanks for sharing wonderful information.

  9. Thanks for sharing such unique information epos software which are in actual fact as well as helpful for us.Keep it up.....

  10. By carefully negotiating the terms and structure of the transaction, a business seller could walk away with a deal that provides a significantly larger economic benefit than a transaction that provides 100% of the proceeds at closing.소액결제현금화

  11. It is advisable to check and re-check all details while conducting an online transaction because banks are not responsible if you enter wrong data entry or incorrect details.소액결제현금화