Query on Reports

Originally posted by Hanu Indrakanti on September 15, 2025 at 9:35 AM.

We are looking for guidance on creating a report in Dayforce that can capture employee attribute changes along with both the previous (old) value and new value.

Our requirement is to have a single report that can track changes across multiple employee attributes, for example:

·       Department

·       Manager

·       Job Title

·       Manager Location

·       First/Last Name

·       Other employee attributes as required

Ideally, the report would provide information in a structure similar to:

Employee | Changed Attribute | Old Value | New Value | Effective Date / Change Date

We understand that these attributes may belong to different entities within Dayforce. We have explored creating individual reports based on the respective entities; however, this would require maintaining multiple reports and mapping each report to the corresponding employee attribute.

We also understand that Dayforce provides a “Create Report from Topic” capability and that change-reporting topics may provide access to historical changes, including previous and new values. We attempted to create a report using this approach but were unable to configure a report that satisfies the above requirement.

Could you please help us confirm:

1.      Is there a reporting topic or standard reporting approach in Dayforce that can provide old and new values for changes across multiple employee attributes in a single report?

2.      If supported, which report topic, entities, and fields should be used to build this report?

3.      Can attributes belonging to different entities, such as Department, Manager, Job Title, Location, and Name, be represented in the same change report?

4.      Are there any required configurations, background jobs, permissions, or feature settings that must be enabled for old/new value reporting?

5.      If this cannot be achieved through a single report, could you please confirm whether this is a Dayforce reporting platform limitation and advise on the recommended alternative?

Our goal is to establish a generic and scalable change-reporting mechanism, rather than maintaining a separate report for every employee attribute/entity.