Asahi - Importing new balances

Created by Alex Schipor, Modified on Fri, 16 Dec, 2022 at 10:20 AM by Alex Schipor

Back up current touch loyalty (SQL Management Studio > Right click on customer loyalty > tasks > backup)

Restore in to Jon PC (SQL Management Studio > Right click on customer loyalty > tasks > restore)

Go to SQL Manager and go to tables > financial database, edit 200 rows - change top selection in properties to no (this will then display all records)

Grab customer table in the same way as this includes the employee number, name etc.

On the file sent over do a sum to work out the total that will be added (on october 2020 we found duplications on the file sent over and so it was causing discrepancy when running sum on total balance vs sum on vlookup)

Copy and paste the results in to excel (looking to use Index ID)

Vlookup against the card number with the starting balance file that has been sent over

Vlookup against the employee number to see if it gives same starting balance

Run sum on balance column to see what amount should be on the touchloyalty dashboard after import

ensure balance column has no empty data (must have 0)

Save to csv and ensure the last row is not a row of blank information (open csv in notepad++) - importing this will through up non-nullable column cannot have null value - this will then cause any further imports to display error even if you fix the blank.

If the above happens you will need to restore backup.

Import into jon test system using IndexID and Balance to financial db

import any name/employee number/card number changes using custID and customer db

Run report in touchloyalty customer balance with tel (employee number)

Run vlookup against card number and employee number using the balance excel file sent over to see if it matches.

Import in to live system using index id and balance if the above is all ok.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article