Create a field using Data Grid extension

Oct 13, 2025 by sorusgentrification.com 52 views

Introduction

Directus is a powerful and flexible headless CMS that allows users to create, manage, and integrate data from various sources. However, like any complex system, it is not immune to bugs and issues. In this article, we will explore a specific problem that users have encountered when using the "Save as Copy" feature in Directus. We will delve into the details of the issue, provide a step-by-step guide on how to reproduce it, and discuss the possible causes and solutions.

Describe the Bug

The issue at hand is that when a user tries to save a copy of a collection using the "Save as Copy" feature, Directus makes a GET request to the item with fields parameters including a deleted field name. This results in an infinite loading screen, and the user is unable to proceed. The problem is not limited to a specific field or collection, but rather seems to be related to how Directus handles the "Save as Copy" feature.

To Reproduce

To reproduce this issue, follow these steps:

Create a field using Data Grid extension: Go to your Directus instance and navigate to the "Collections" page. Create a new collection or select an existing one. Then, go to the "Fields" tab and click on the "Add Field" button. Select the "Data Grid" extension and create a new field.
Add data to a collection using this field: Once the field is created, add some data to the collection using this field. Make sure to include some sample data to test the issue.
Delete the field from collection: Go back to the "Fields" tab and delete the field you created in step 1.
Update a separate field (can be any) then click "save as copy" button: Update a separate field in the collection, and then click on the "Save as Copy" button. This should trigger the GET request to the item with fields parameters.
Observe the error in network tab in browser: In the browser's developer tools, navigate to the "Network" tab and look for the GET request to the item with fields parameters. You should see an error similar to the one below:

{
    "errors": [
        {
            "message": "You don't have permission to access field \"Quantity_table\" in collection \"SKU\" or it does not exist. Queried in root.",
            "extensions": {
                "reason": "You don't have permission to access field \"Quantity_table\" in collection \"SKU\" or it does not exist. Queried in root.",
                "code": "FORBIDDEN"
            }
        }
    ]
}

Directus Version

The issue was encountered on Directus version v11.5.1.

Hosting Strategy

The Directus instance was self-hosted using a Docker image.

Database

The database used was PostgreSQL (postgis/postgis:13-master).

Possible Causes and Solutions

Based on the issue description and the steps to reproduce it, there are a few possible causes and solutions:

Directus not updating schema fields: It is possible that Directus is not updating the schema fields correctly, leading to the issue. To resolve this, you can try updating the schema fields manually or using a script to update the fields.
Data Grid extension issue: The issue might be related to the Data Grid extension itself. You can try disabling the extension or updating it to the latest version to see if it resolves the issue.
Directus configuration issue: There might be a configuration issue with Directus that is causing the problem. You can try checking the Directus configuration files or consulting the documentation to see if there are any known issues or workarounds.

Conclusion

Q: What is the "Save as Copy" feature in Directus?

A: The "Save as Copy" feature in Directus allows users to create a duplicate of a collection, including all its fields, data, and relationships. This feature is useful for creating a backup of a collection or for creating a new collection based on an existing one.

Q: What is the issue with the "Save as Copy" feature in Directus?

A: The issue is that when a user tries to save a copy of a collection using the "Save as Copy" feature, Directus makes a GET request to the item with fields parameters including a deleted field name. This results in an infinite loading screen, and the user is unable to proceed.

Q: What are the steps to reproduce the issue?

A: To reproduce the issue, follow these steps:

Create a field using Data Grid extension.
Add data to a collection using this field.
Delete the field from collection.
Update a separate field (can be any) then click "save as copy" button.
Observe the error in network tab in browser.

Q: What is the error message that is displayed in the network tab?

A: The error message is:

{
    "errors": [
        {
            "message": "You don't have permission to access field \"Quantity_table\" in collection \"SKU\" or it does not exist. Queried in root.",
            "extensions": {
                "reason": "You don't have permission to access field \"Quantity_table\" in collection \"SKU\" or it does not exist. Queried in root.",
                "code": "FORBIDDEN"
            }
        }
    ]
}

Q: What are the possible causes of the issue?

A: The possible causes of the issue are:

Directus not updating schema fields
Data Grid extension issue
Directus configuration issue

Q: How can I resolve the issue?

A: To resolve the issue, you can try:

Updating the schema fields manually
Disabling the Data Grid extension
Updating the Directus configuration
Consulting the Directus documentation or seeking help from the Directus community

Q: Is this issue specific to a particular version of Directus?

A: The issue was encountered on Directus version v11.5.1. However, it is possible that the issue may exist in other versions of Directus as well.

Q: Can I prevent this issue from occurring in the future?

A: Yes, you can prevent this issue from occurring in the future by:

Regularly updating the schema fields
Disabling the Data Grid extension when not in use
Updating the Directus configuration regularly
Consulting the Directus documentation or seeking help from the Directus community

Q: Where can I find more information about this issue?

A: You can find more information about this issue in the Directus documentation, community forums, or by contacting the Directus support team.