unique_name that conflicts with an existing resource. Datasets, access rules, and views all share a single namespace — NQL does not distinguish between them — so unique_name must be unique across all three resource types.
Error response
When this occurs
You receive this error when creating or renaming any of the following and the chosenunique_name is already in use:
- Dataset — A new or renamed dataset conflicts with an existing dataset, access rule, or view
- Access rule — A new or renamed access rule conflicts with an existing dataset, access rule, or view
- View — A new or renamed view conflicts with an existing dataset, access rule, or view
customer_events will fail if a dataset or view with that name already exists.
How to resolve
- Check the
detailfield — It identifies the conflicting name - Choose a unique name — Pick a
unique_namethat doesn’t conflict with any existing dataset, access rule, or view - Check for cross-type conflicts — If the name looks unfamiliar, the conflict may be with a different resource type (e.g., a dataset blocking an access rule name)
- Update instead of create — If you intended to modify an existing resource, use the update endpoint with the correct resource ID instead of creating a new one
Related content
Access Rules
Understand how access rules control data access
Datasets
Understand dataset schemas and structure
Error Reference
Overview of common API errors

