How validations work when publishing from a Batch Upload

Summary

Before files in a batch upload go to the asset bank, Bynder checks each file against your portal's metadata setup. A file can carry values on fields you can't see or edit, so some files may be blocked from publishing even when nothing looks wrong. This article explains which settings block publishing and which don't, so you can prepare your batch and know what to expect when you publish or request approval.

Who?

Batch Uploads in Workspace are available to Publishers with Access Workspace and Upload assets permissions, and Requesters with Access Workspace and Upload assets with mandatory approval permissions.

Why?

Metadata can be added to files in a batch in several ways: by you, by an integration through the Asset API, or automatically by metadata extraction from embedded file data. Because of this, a file can have values on fields that you can't see or edit. Depending on your portal configuration, this can block publishing.

How?

Check Which Settings Block Publishing

Use this table to see what can stop a file from being published before you publish or request approval. The same rules apply to Publishers and Requesters.

Configuration Blocks publishing? What happens What to do
Required fields Yes Every file needs a value for each required metaproperty. Publishers can publish the files that are ready. Requesters can't create the request until every file is complete Fill in the missing fields. See Fill in required fields below
Asset name Yes Every file needs a name before it can be published Fill in the Name field
Metadata extraction in progress Yes Bynder is still extracting metadata from the file. This can take longer for large files Wait until processing finishes, then publish again
Interrupted or failed upload Yes Only the interrupted and failed ones cannot be published. User can resume the upload by re-uploading the file(s) or remove from the batch.
Show / hide automation (dependent metaproperties) Yes, if a hidden dependent metaproperty has a value. Metadata extraction can set a value on a dependent metaproperty while it's still hidden Select the parent option that makes it visible. See Resolve values on hidden dependent metaproperties below.
Hide metaproperty on asset upload and edit Yes, if it has a value and you don't have the Edit hidden metaproperties on assets permission. With the permission, you can see the metaproperty and publish. Without it, you can't see it. Contact your portal administrator.
Option no longer exists Yes The file has an option that was deleted from the portal’s taxonomy. Contact your portal administrator.
Metaproperty no longer exists Yes The file has a value of a metaproperty that was deleted from the portal’s taxonomy. Contact your portal administrator.
Metaproperty visibility restricted for your user or group No The metaproperty isn't shown to you and you can't edit it. Values added automatically stay on the asset. Nothing
Option set to Disabled in upload & edit No You can't select the option. If it was added automatically, it stays on the asset. Nothing
Option set to Hide media No After publishing, who can see the asset follows the access rules set on that option. Nothing

Fill in Required Fields

Required fields are the most common reason a file can't be published. Publishers can publish the files that are ready and fix the rest later. Requesters can't create the approval request until every file in the batch has all required fields filled in.

  1. In the top right of the batch, click Publish or Request approval.

  2. In the review modal, click Show details to see the files listed under Files are missing required fields.

  3. Click Cancel (Publishers) or Resolve issues (Requesters) to return to the batch.

  4. Fill in the required fields on each file, either in the cells in List view or in the inspector.

  5. Click Publish or Request approval again.

For more on editing fields, see Editing modes in a batch upload.

Resolve Values on Hidden Dependent Metaproperties

Some metaproperties only appear when a specific option is selected in another metaproperty. For example, Asset Subtype only appears after you select an Asset Type. Metadata extraction can set a value on a dependent metaproperty while it's still hidden, which blocks the file even when you don't see any empty fields.

  1. Open the file in the inspector.

  2. In the parent metaproperty, select the option that makes the dependent metaproperty visible.

  3. Review the value of the dependent metaproperty and update it if needed.

  4. If you're not sure which option is correct, contact your portal administrator.

Level: Proficient

Proficient-level articles are for users who have some prior Bynder knowledge. These articles require you to know the basics and may also require higher-level portal rights to accomplish the task outlined within the article. 

Updated