Known Issues in Batch Uploads in Workspace

Summary

Batch Uploads in Workspace lets users upload, stage, enrich, and publish multiple assets at once. Some upload settings that work in the Main Uploader don't apply in Workspace, and some issues are still being fixed. This article lists these known issues and limitations, with workarounds where available, so you can prepare your users before they start using Workspace.

Who?

This article is for administrators whose portal uses custom upload settings in the Main Uploader. Bynder Support or your Customer Success Manager usually turns these settings on. If you're not sure which settings your portal uses, contact Bynder Support.

Why?

If your portal uses one of the settings below, your users may see different behavior in Workspace than in the Main Uploader. Knowing this upfront helps you prepare your users and avoid surprises.

Known issues

Hidden metaproperties stay visible after a permission change

A metaproperty can be set to read only or hidden in the upload and edit screen. If a user or group can see this metaproperty, and an administrator then removes their permission to see it, the user can still see the metaproperty in Workspace.

Workaround: Save a change in the taxonomy to refresh the settings.

  1. Open an existing metaproperty option in the taxonomy

  2. Save it without making any changes

The user no longer sees the metaproperty.

We're working on a fix for this issue.

Some options are missing from the list in autocomplete metaproperties

When a metaproperty is set to autocomplete, some options might not appear in the alphabetical list.

Workaround: Type the name of the option in the field's search to find it.

We're working on a fix for this issue.

When asset A is linked to another asset B in Batch Uploads using the Related Assets functionality, if user deletes asset A then the relations will still be visible with asset B, but only the UUID will be visible on the chip.

We 're working on a fix for this issue.

FAQ

Will the known issues be fixed?

Yes, we're working on fixes for the metaproperty issues listed above. We'll update this article when they're fixed.


 

Updated