Using Setup Data Manager

Setup Data Manager (SDM) Moves and manages configuration data across software and hardware environments. (SDM Setup Data Manager moves and manages configuration data across software and hardware environments.) lets you publish configuration (setup) data from one tenant to another tenant. Setup data is data that you enter as part of the configuration of the suite. For example, setup data includes pay rules, labor levels, and manager summaries. You can copy all setup data or select specific setup data.

Use Setup Data Manager to save the time of manually re-entering setup data in multiple environments, eliminate the potential for a user to make a mistake when re-entering setup data, and allow you to update a number of setup data policies all at once.

SDM adds or updates setup data items based on the name of the item:

  • If the item name already exists on the target database, then the item is updated.
  • If the item name does not exist on the target database, then the item is added.
  • An item is never deleted from the target database, regardless of whether it exists or has been deleted from the source database.

The only exceptions to the items above are for Business Structure Represents the logical structure of an organization as it concerns staffing. It contains the locations and jobs to which an employee may be assigned. elements, Business Processes An organized flow of activities or tasks that achieves a business goal. An automated business process minimizes the amount of paperwork and manual tasks to complete that process by way of automatic actions, online forms, and automatically generated messages., Process Models, Attestation The act of confirming or attesting that something is true. For example, when punching out, users may need to attest that they took their meal breaks. Workflows, and Attestation Models, which are added or updated based on an internal ID. This allows you to change the name of an item but keep its place in the business structure. This means that a business structure node that was created on one tenant, always has a different ID than any node on another tenant, and is considered a unique setup item. For nodes on different tenants to be considered the same they must have originated on the same tenant.

The changes made to setup data on the target server during the data transfer are written to the server’s audit trail, just as if they were entered manually on the target system. This means that a business structure node that was created on one tenant, always has a different ID than any node on another tenant, and is considered a unique setup item. For nodes on different tenants to be considered the same they must have originated on the same tenant.

Note: You should make your configuration changes first to a non-production tenant. Afterward, you can migrate the configurations to the production tenant, after appropriate testing, using the Setup Data Manager tool. The types of configurations include integrations, reports, KPIs , and so on. Directly changing configurations in the production environment could unintentionally cause issues to occur.

Key features of SDM

With SDM you can:

For your convenience, the version numbers from both the source and target are displayed when you select items for data transfer.

Note: To keep you informed about the possibility of incomplete data transfer, some scenarios generate warnings that indicate when the data transfer only partially succeeded and that some items may be missing from the target. For more information, see Version compatibility messages.

To exit SDM, close the tab in which it is open and return to the Home page The page that is presented to the user upon login, which contains the tiles that let the user access or navigate to common tasks. to log out.