Skip to main content

Bulk Actions

Easily update multiple assets at once via the search page

Updated over 5 months ago

Bulk actions are a great way to update multiple assets at once. You can use bulk actions to:

  • Edit Property: Modify specific property values for multiple assets.

  • Edit Relations: Adjust relationships between assets.

  • Restrict Discovery: Change visibility settings for assets.

  • Delete Assets: Remove selected assets permanently.
    ​


​Editing Assets

  1. On the Search page, you can use the filter panel to narrow down and select the assets you want to update.

  2. Click the Bulk Actions button in the top-right corner.

  3. Choose the action you want to perform.

  4. Define the values you want to update (this step might be different for each type of action).

  5. Click Save to execute the bulk action.

  6. A success message will be displayed indicating how many assets have been updated.
    ​

  • Why I can't see all properties?
    Bulk updates are only available for properties of the "dropdown" and "collaborator" types. If you need to update other property types, you'll need to do individually.

Deleting Assets

  1. On the search page, you can use the filter panel to select the assets you want to delete.

  2. Click the Bulk Actions button in the top-right corner.

  3. Choose the Delete option.

  4. A confirmation pop-up will appear, showing the number of assets selected for deletion. Click Accept to confirm. This action is not restorable. Once confirmed, it cannot be undone.

  5. A success message will be displayed indicating how many assets have been removed.

  • Why didn’t my bulk action execute for all assets?

    • Limitations: Bulk actions work best in batches of 200 items. If updating more assets, repeat the bulk action.

    • Insufficient Permissions: Each bulk action verifies your assigned access policies. If some assets weren’t updated, you might not have the necessary permissions to edit them.

      ‼️ Bulk deletes and bulk discovery restrictions can only be performed by superusers in dScribe.

Did this answer your question?