Summary

Use this tab to define settings for a manual synchronisation. The information entered in each field depends on:

• The type of import or export data.
• Where the data is.
• Where you want the data to go.
• The format of the data.

Fields

Type:

Select Import or Export depending on whether you are importing data from another system or exporting PayGlobal data to another system.

Select Custom to synchronise to the 'Magic', 'Hayes' 'JDE', 'Cf', 'Equinox' or 'SAN' software applications.

Database table:

The name of the PayGlobal table to import to or export data from.

Path:

Enter the location of the import data file or export file, or click the pick list icon and browse to the file location.

The recommended Import location in PayGlobal is: '[INSTALLDIR]\Dataxx\Import'.

The recommended Export location in PayGlobal is:
'[INSTALLDIR]\Dataxx\Export'.

If the Path field is empty, then PayGlobal automatically uses the path to the company Import or Export folder. For example, if Type = "Export" and Path is blank, PayGlobal will default to the company data Export folder.

File name:

For Import, the filename is the name of the file to be imported. Make sure you enter the full filename and extension.

For Export, the filename is the name that you want the exported file to be called. Always use the extension ‘.txt’ after the filename to avoid complications when opening with another application.

File type:

PayGlobal supports logical (.csv or fixed width format) synchronisation. PayGlobal can also support software packages that do not use .csv or fixed width formats, such as the 'Magic', 'Hayes' or 'Cf' software packages. Talk to your PayGlobal Consultant if you want to synchronise to another software system that does not support any of these formats. Additional development costs may be incurred.

First line is header:

If 'Yes' is selected here, the import will ignore the first line of the file. This is useful if the first line is field names.

Field names in header:

(Enabled for Import only)

• Yes

  The Fields tab page does not need to be completed. PayGlobal automatically takes the field names from the database file or from the first line of the .csv file.

• No

  Setting this field to 'No' gives you more control over the fields that will be imported or exported. You will then need to specify the import or export fields on the Fields tab page.

Query:

(Enabled for Export only). Use a query to filter the export data.

When you export a synchronisation file, PayGlobal applies the query to the database table before the export process begins. Therefore data from the export file is only written for records applicable to the query.

Custom type:

These software packages are hardcoded in PayGlobal and do not use .csv or fixed width formats for importing or exporting.

Date format:

This is the format used for dates. For example, ddmmyy or mm/dd/yy.

Time format:

This is the format used for time. For example HH:MM or HHMM.

Empty table:

(Enabled for Import only).

• Yes

  Empties the data table before importing new or updated data.

• No

  Imports the new data by adding it to the existing data. No duplicate records are created; information is simply updated.

Delete file after import:

(Enabled for Import only).

• Yes

  The file is deleted after it has been imported.

• No

  Recommended. The file may be manually deleted after checking that import details are correct. The imported file is renamed to *.bak.

Can add records:

(Enabled for Import only).

• Yes

  To include additional records in synchronisation.

• No

  To prevent duplicate or unwanted records being imported during synchronisation.

Audit import:

(Enabled for Import only)

• Yes

  To create an audit log of the import.

• No

  No audit log is created for the import.

Ignore blanks:

(Enabled for Import only).

This field determines whether blank or [NULL] fields in the import file overwrite existing values in the PayGlobal database.

Importing a blank field:

• Yes

  Blank field value does not overwrite the current field value in the PayGlobal database.

• No

  If the PayGlobal database field is not an entity code, then the blank field value overwrites the current field value in the PayGlobal database.

Importing a NULL field:

• Yes

  If the PayGlobal database field is not an entity code, then NULL field values overwrite the current field values in the PayGlobal database.

• No

  NULL field values do not overwrite the current field values in the PayGlobal database.

You cannot overwrite entity code values, such as Employee Code or Department Code. If you try to import blank or NULL values for entity code fields, then the synchronisation will fail and an error message will appear. You can import blank or NULL values for other mandatory PayGlobal fields because they are not verified during synchronisation. However, when you open the affected record in PayGlobal, an error message appears and you have to add the new value.

See also

Synchronisation

Synchronisation - Fields

Synchronisation Makeup

Export Files

Import Files