Filename unique error for media when using multi-tenant-plugin

[tapartdev]

Describe the Bug

When using the multi-tenant-plugin, uploading a media file with a filename that already exists under a different tenant triggers a validation error. The error occurs even though the filename is unique within the current tenant.

Expected behavior:

The media file should upload successfully since the filename is unique within the context of Tenant B.

Actual behavior:

A validation error is returned:

{
    "errors": [
        {
            "name": "ValidationError",
            "data": {
                "errors": [
                    {
                        "message": "Value must be unique",
                        "path": "filename"
                    }
                ]
            },
            "message": "The following field is invalid: filename"
        }
    ]
}

Notes:

The error seems to enforce global uniqueness rather than tenant-scoped uniqueness.

This issue prevents uploading files with the same name across different tenants.

Link to the code that reproduces this issue

Reproduction Steps

Set up multiple tenants using the multi-tenant-plugin.

Upload a media file (e.g., image.jpg) under Tenant A.

Switch to Tenant B and try to upload a media file with the same filename (image.jpg).

Which area(s) are affected?

plugin: multi-tenant

Environment Info

Payload version: 3.69.0

[github-actions]

Please add a reproduction in order for us to be able to investigate.

Depending on the quality of reproduction steps, this issue may be closed if no reproduction is provided.

Why was this issue marked with the invalid-reproduction label?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We prefer a link to a public GitHub repository created with create-payload-app@latest -t blank or a forked/branched version of this repository with tests added (more info in the reproduction-guide).

To make sure the issue is resolved as quickly as possible, please make sure that the reproduction is as minimal as possible. This means that you should remove unnecessary code, files, and dependencies that do not contribute to the issue. Ensure your reproduction does not depend on secrets, 3rd party registries, private dependencies, or any other data that cannot be made public. Avoid a reproduction including a whole monorepo (unless relevant to the issue). The easier it is to reproduce the issue, the quicker we can help.

Please test your reproduction against the latest version of Payload to make sure your issue has not already been fixed.

I added a link, why was it still marked?

Ensure the link is pointing to a codebase that is accessible (e.g. not a private repository). "example.com", "n/a", "will add later", etc. are not acceptable links -- we need to see a public codebase. See the above section for accepted links.

Useful Resources

• Reproduction Guide
• Contributing to Payload