DataMasque Portal

Moving Resources

You can move a resource to another project at any time. Its name, content and history stay the same.

Who can move resources

Administrators and Mask Builders can move resources. Moving a ruleset library or discovery config library also needs the Manage Ruleset Libraries permission. Built-in seed files belong to no project and cannot be moved.

Move resources

To move one or more resources of any type:

  1. Click Projects and Resources under Manage in the sidebar.
  2. Find the resources with the Project and Type filters and the Search resources by name field (see Filtering and searching).
  3. Select each resource's checkbox. To select every resource on the page, select the checkbox in the header row. The selection is kept when you change the page. Changing the filters or the search deselects any resource they hide.
  4. Click Move to project… above the table.

You can also start a move from these pages:

  • On the Database Masking, File Masking, Ruleset Libraries, Discovery Configurations, Discovery Config Libraries, Ruleset Generation Configurations or Table References pages, click Move to project… in a row's menu.
  • On the Files page, click the move Move button icon in a file's row.
  • On the Ruleset Management page, select rulesets and click the Move button.
  • On the edit page of a saved resource, click the move Move button icon at the right end of the Project field.

These actions open the Projects and Resources page with those resources selected and the Move to project dialog open.

Move to project dialog

In the Move to project dialog:

  1. Click Show list to check which resources are selected.
  2. In the To project field, choose the destination project.
  3. Read the notices, which list the resources that cannot move and any references that will need updating after the move.
  4. Click Move.

All of the resources move together. If any cannot move, the Move button is disabled until you deselect it or resolve its conflict. A selected resource that is already in the destination project stays there, and the others move.

Warning: A run can fail if a file it uses moves while the run is in progress.

Resources that cannot move

In each of the following cases, a resource cannot move between projects:

  • The destination project already has a resource of the same type and name. Rename one of them first.
  • Another resource of the same type and name is being moved from another project, such as two libraries called emails in projects A and B both moving to project C. Rename one of them first.
  • The destination project already has a file on disk where the resource's file would move to. Contact DataMasque support for assistance.

The move dialog lists any of the above issues, for example:

Move to project dialog with a name clash

Moving a resource does not update references to it, or the names it uses to refer to other resources. For the changes needed after a move, see Updating references.

If a ruleset is moved, all runs that used that ruleset also move to the same project. Likewise, if a discovery config is moved, all discovery runs that used that configuration move to the same project.

Resources that are synced to Git

Rulesets and other YAML documents that are synced to a Git repository do not automatically get pushed to their new location. When you next push a moved resource from the editor pages, the resource is pushed to its new project's folder. Its auto-pull fails until you push it.

Note: The copy of the file in the old folder is not removed from the repository. You may wish to delete this old file with git rm.