How do I run Universal Data Transfer (UDT)?

Owned by Jenn Ferreris
Last updated: Mar 25, 2024

This article guides users on how to update labor or sales data by running Decision Logic’s Universal Data Transfer (UDT) application. 

Overview

Universal Data Transfer (UDT) is Decision Logic’s application used to import sales and labor data from the POS into Decision Logic’s platform.  The application is typically installed on the back office server.

Only available for Windows XP or newer versions.


UDT automatically sends the last 3 days of sales and last 7 days of labor to Decision Logic’s platform. 

 

There may be times when a user may need to run UDT, such as: 

  • Labor data is incorrect or missing when comparing Decision Logic to the POS.

  • Employee is not assigned a job code in the Employee Roster.

  • Employee does not exist (unknown) in the Employee Roster.

  • Missed declared tips for a tippable job code.

  • Clearing an issue with a previously unmapped item.

 

When one of the examples from above occurs, users will need to update information by one of the following methods:

 

The method is determined by the type of Point Of Sale (POS) the store has.  Universal Data Transfer (UDT) is run when a store has the following POS:

  • Micros

  • Aloha

  • Hunger Rush

  • QuikServe

 

Users will need to clear labor for each day that has incorrect or missing labor and Open Payroll, if payroll is posted, before running UDT.  Users will also need to clear sales for each day that has incorrect or missing sales.

Table of Contents

For additional questions or assistance, please submit a support ticket by visiting the Decision Logic Service Center.

 

Clear Labor or Sales

When users need to update labor data, they will need to Open Payroll before running Universal Data Transfer (UDT).  Follow the steps below to clear labor or sales for each day that has incorrect or missing data.

 

Operations > End of Day > End of Day

 

  1. Select a Store.

  2. Select a Date.

  3. Click Next.

     

  4. Click More Actions.

     

  5. Click Clear Labor or Sales.  Users will need to clear labor or sales for each day that has incorrect or missing data.

     

  6. Click Yes.

 

Open Payroll

Users will need to open payroll for missing or incorrect labor data.  Users will not need to open payroll when updating incorrect or missing sales data. Follow these steps to Open Payroll:

Operations > Payroll > Store Payroll

  1. Select a Store.

  2. Choose a Payroll Week date range.

  3. Click Open.

     

 

Leave the payroll week open until you perform the steps to run Universal Data Transfer (UDT).  After UDT has a successful transfer, users will need to re-post payroll.

 

 

Run Universal Data Transfer (UDT)

Follow the steps below to run the Universal Data Transfer (UDT) application on the back office computer.

  1. Launch UDT Client application.

     

  2. View the Status.  The status needs to be green to transmit data.

    1. Green - The client is running and ready to transmit data.

    2. Red - The client is not running and not ready to transmit data.

      1. Read this article for troubleshooting.

    3. Yellow - The client is not running and not ready to transmit data.

      1. Read this article for troubleshooting.

         

  3. Select a Run Date from the drop down.  Today’s date is selected by default.

    1. The UDT Client app will transmit 7 days of historical Labor Data and 3 days of historical Journal Data.

      1. Example:  If you select the 7th, then dates 1st-7th of Labor Data will update, and dates 5th-7th of Journal Data will update.

         

  4. Click Process Now.

     

  5. Check each task you need to transmit data to Decision Logic.  All tasks will be selected by default.

    1. Labor Data:  Consists of summary labor hours.

    2. Journal Data:  Consists of sales, comps, discounts, and payments.

    3. If not all tasks are selected by default, then you do not have the latest version of the UDT Client app.

  6. Click OK to begin processing the UDT task you selected to send data to Decision Logic.

     

 

 

The Process Log will indicate if the data was sent successfully.  Data should appear on your mydlweb.com website within 30 minutes of a successful send.

 

If validation is not successful, follow the steps in this article.

 

Troubleshooting

If you receive an Error validating a store, there are a few things that could cause this error in UDTStoreTask.log.

 a) The UDTClient service is running under an account that doesn't have Administrator privileges.
 b) The date/time and/or daylight saving settings are incorrect on the machine.
 c) The StoreID or StoreGUID in the configuration files is incorrect.

Situation

Suggested Step(s)

A

Configure the UDTClient service to use an account that belongs to an Administrator group.
Verify that the user is able to hit https://tac2.mydlweb.com/UDTService/Service.svc from a browser. 

B

Correct the date/time. The clock cannot be skewed more than 15 minutes. Be sure that the "Automatically adjust for Daylight Saving" option is enabled/checked.

C

Verify that the StoreID and StoreGUID appSettings are correct in the configuration file.

 

Errors With POS

Here are some common errors and solutions that may arise.

  • Task completed in error - no log files found match.
    This usually means that the task is unable to locate/connect to the data source.

POS

Suggested Step(s)

Aloha

 

  • Be sure that the RootDirectory value are correct in UDT Server Management

  • Look for errors in UDTStoreTask.log

  • Debug task in Visual StudioFix the timezone in Aloha in d:\bootdrv\alohags\data

Fix TimeZone in Aloha in d:\bootdrv\alohaqs\data

  1. Delete the timezone.ini file in d:\bootdrv\alohaqs\data

  2. Set the correct date, time and time zone in Windows

  3. Restart the ctlsvr service

Aloha then builds a new timezone.ini file the d:\bootdryMicros

Micros

  • Be sure that the ConnectionString value is correct in UDT Server Management

  • Look for errors in UDTStoreTask.log

  • Debug task in Visual Studio

Radiant

  • Be sure that the RootDirectory and FileMask values are correct in UDT Server Management

  • Look for errors in UDTStoreTask.log

  • Debug task in Visual Studio

Squirrel

  • Be sure that the ConnectionString value is correct in UDT Server Management

  • Look for errors in UDTStoreTask.log

  • Debug task in Visual Studio

 

 



If you'd like to receive news on software releases and product updates, please sign up for our email list.