website logo
⌘K
Getting Started 🚀
What is DataLakeHouse.io?
Our Business-Value Focus
Learn the Basic Concepts
Connectors
Operations Applications
Asana
Aloha POS
Baremetrics
Beans Route
BILL
Bloom Growth
Bullhorn
Calendly
Ceridian Dayforce
ClinicalTrials.gov
ConnectWise
DBT Cloud
DBT Cloud Log Stream
Facebook Ads
Food Delivery Service Connector
Google Analytics 4
Google Play
Harvest
Hubspot
Jira
MailChimp
McLeod Transportation
Microsoft Teams
NetSuite (Oracle NetSuite)
NetSuite SuiteAnalytics
Optimum HRIS
QuickBooks Online
Salesforce
Salesloft
Shift4 Payments
Shopify
Square
Square Marketplace
Stripe
Toast
TriNet
Verizon Wireless Business
Workday HCM
Xero
Zendesk Sell
Zoom
Databases
Files & Object Storage
SQL Data Query
SSH Tunnel Setup for Hosted Database Systems
SQL Playground Editor
SQL Transformations
DBT Cloud Transformations
Terraform: Reverse Terraforming
Sync Bridge (Data Pipelines)
Create a Sync Bridge
Manually Run a Sync Bridge
Deleting a Sync Bridge
Historical Re-sync
Analytics
Access Analytics
Snowflake Usage Analytics
Data Catalog
Create the Catalog
Populate the Catalog
Access the Catalog
Data Warehouse Clouds
❄️Snowflake
Open Source DW Models
Alerts & Notifications
Slack Notifications
Logs & Monitoring
Security
Callback Links
Service Level Agreement (SLA)
Release Notes
July 2023
June 2023
May 2023
April 2023
Q3 2022
Q4 2022
Community Overview
Contributor Agreements
Code Contribution Guide
About
Customer Support
License
Viewpoint
Credit Consumption Breakdown
Docs powered by
Archbee
website logo
Connectors
...
Operations Applications
Ceridian Dayforce

Employee Pay Summary - manually changed records

4min

There are situations where a person has issues punching a clock and the time recorded in Ceridian needs to be manually adjusted. It's possible these adjustments are made by a manager in Ceridian several days later.

By default, a Sync Bridge replicates the last 30 days worth of Employee Pay Summary records.

When this situation occurs, Ceridian does not provide a field in their API to indicate that a punch has changed and provides the updated record as a new record in the API. To account for this situation a Transformation needs to be created in DataLakeHouse.io in order to mark the __DLH_IS_DELETED flag to TRUE.

Create a Transformation with Pre-SQL Update

  1. Login into DataLakeHouse.io and click on Transformations
  2. Select the option for PRE-SQL
  3. Enter a PRE-SQL update statement such as this one below and then save the transformation
UPDATE DATALAKEHOUSE_DB.PRODDB_CERIDIAN_DAYFORCE.EMPLOYEE_PAY_SUMMARY SET __dlh_is_active = false, __dlh_is_deleted = true WHERE EMPLOYEE_XREF IN ( SELECT DISTINCT(EMPLOYEE_XREF) FROM DATALAKEHOUSE_DB._TMP_PRODDB_CERIDIAN_DAYFORCE.EMPLOYEE_PAY_SUMMARY ) ;

After you've entered the Pre-SQL logic:

  • Complete the remainder of the required fields
  • Save the transformation form

Next time the bridge runs and completes a load for the EMPLOYEE_PAY_SUMMARY table your transformation and the update statement will run prior to loading the data into your target schema.



Updated 16 Jun 2023
Did this page help you?
PREVIOUS
Ceridian Dayforce
NEXT
Ceridian : Change Log & Notes
Docs powered by
Archbee
TABLE OF CONTENTS
Create a Transformation with Pre-SQL Update
Docs powered by
Archbee