The entry_template and entry_template$raw tables don't contain all of my templates

Raksha
Raksha
  • Updated

Issue

The number of templates stored in the entry_template table doesn't match the number of templates available to my organization. This issue also applies to the entry_template$raw table in the data warehouse.

Environment

Your organization's postgreSQL warehouse

Cause

The entry_template table only displays templates that live in collections owned by the entire organization, and that are accessible to all members of the organization. Permissions for the entry_template table behave this way to ensure users can't view templates in the entry_template table that they don't have View access to in the Benchling platform. The same permission behavior applies to the entry_template$raw table.

The warehouse currently supports row-level permissions, which only show the objects or rows in a table that the warehouse user has READ access to. Those permissions are derived from projects or registries. Templates live in neither; they are stored in template collections, and the warehouse doesn't have a way to inherit permissions from template collections.

Templates may also not appear if the organization does not have minimum read access to the template collection. If personal ownables are disabled in the organization, all items are owned by the organization directly, which can affect visibility in the warehouse.

Resolution

To better understand template usage, like how many entries are created from templates and which templates are used the most, you can query the entry_template_id column in the entry table.

To find the template name of a given template's API ID, call the GET/entry-templates API endpoint.

Was this article helpful?

Have more questions? Submit a request