Paycom Data Targets

Overview

DataBlend supports the following data targets for creating records in Paycom

  • Punch Imports

  • Categories

 

Configuration

Setting 

Required/ Optional

Description 

Query

Required

Select the query that will generate the data for this target.
See the relevant target type documentation for additional details on what query columns are required for your target.

Query Mode

Required

Select New unless you have a reason to select Latest or Specific.

Credential

Required

Select a Paycom Credential from the list.

Target Type

Required

Select Timesheets.

 Template

Required column headers are described in the table below.

Column Header

 

Type

 

Description

 

hours

Float

Number of hours worked

clocktype

String

S = web time sheet

H = web time clock

K = kiosk

entrytype

Integer

1 = Punch

2 = Hours

3 = Earnings

4 = Units

punchtype

String

ID = In Day

OD = Out Day

OL = Out Lunch

IL = In Lunch

OB = Out Break

IB = In Break

OX = Out Transfer

IX = In Transfer

eecode

String

Employee Code

punchtime

String

UnixTime

Example Query:(CAST("to_unixtime"("now"()) AS bigint) "punchtime")

timezone

String

Time Zone (e.g. EST)

earncode

String

[a-zA-Z0-9]

 Advanced

History Retention

History Retention (Days) allows users to decide how long they want the information from their data targets to be stored. This field is optional.

Timeout (seconds)

The Timeout section allows users to determine if they would like to timeout collections taking longer than a set number of seconds to collect data.

Skip If No Records Found

The “Skip if No Records Found” button is used to eliminate sending information to Data Targets unnecessarily. Simply enable the “Skip if No Records Found” toggle. The use of this toggle is optional.

Agent

The Agent drop-down for users to select any agent they have established. This is optional.

Run As

Run As allows users to select from a drop-down list of users to run the Workflow. This is optional. Please note that Run As is only available to Admin users. If a user is set as the Run As and then demoted to a Member, the user which demoted the Run As user will instead be set as the Run As.