Dayforce Reports to Data Warehouse Target

any of your ceridian dayforce reports can be configured to be part of the data feed (aka replication) to your targeted data warehouse of choice dlh io does this by conncting to your ceridian dayforce docid 3f3b3 toiuutq366unalv source connector and you will see available dayforce reports underneath your list of tables/entities that are available to be replicated ceridian dayforce reports listed in dlh io in order for your dayforce reports to be replicated as is from your dayforce account you need to update each dayforce report you wish to replicate in your dayforce account so that the report is accessible by the user you used to create your dlh io dayforce source connection the user you used to create your dlh io dayforce source connection has security access to the report category the report is of type v2 the report integration name is prefixed with dlh otherwise the report will not be found by dlh io for example, a report named executives pay summary must have a name and an integration name of dlh executives pay summary to access any ceridian report, make sure access to the report library feature is granted to the ceridian role used in system admin > roles > features tab within ceridian if the report is attached to a report category, access to this category also needs to be granted in the feature screen in this example, access to the compensation management category is granted to access the compensations cycle report that is attached to the compensation management category dayforce report with required parameters if the dayforce report will only run after entering parameters, dlh io is able to pass a value to each dayforce parameter open the ceridian dayforce source connection and click the options button for the desired ceridian report you only need to update the attribute value(s) field start by finding the guid for the associated parameter and then set the value provide each of the 'parameters' with their values in a single line for example, if the parameter guid is 2f4bf025 b4d1 4048 bc17 fa1d7f93ee81 and its type is of a boolean you would then enter, 2f4bf025 b4d1 4048 bc17 fa1d7f93ee81=false, on a new line dynamic parameters the above example works well for those situations where a hardcoded parameter value is sufficient for each sync bridge run if you want the parameter value to be dynamic for each run, then the following example is appropriate in the example below, the guid (a) references a date value and the goal is for the date to be dynamic so during each sync bridge run, the date that is passed to ceridian as the parameter is today's date set the attribute value equal to {{local dt | format date('mm/dd/yyyy hh\ mm\ ss a') }} if the report is still not showing in datalakehouse io , read more about this access via the following shared document, how to configure ceridian dayforce reports in dlh io common issues ceridian set throttle limits for getting data from reports to 10 reports per second up to 50 reports per hour once the throttle threshold is met the datalakehouse io sync bridge will pause an hour and continue the sync bridge in other terms, you can replicate up to 50 reports from ceridian to your what is a target connection? docid 3wx 24ml25noxc1atdbs4 before the sync bridge will need to pause for one hour before continuing with data replication details on ceridian api throttle limits also, keep in mind the amount of records on each report will also impact throttle limits