Did anybody ever faced an issue after patching a c...
# community-help
s
Did anybody ever faced an issue after patching a collection with a reference field to another collection? It seems like I can break the collection that way. Further calls to retrieve the collection do not yield the reference field. However, when trying to patch it again (even with adding a different field), I am just getting an error stating:
Copy code
{
  "message": "There are duplicate field names in the schema."
}
Running on self hosted v28.0 Confirmed it is reproducible for me. Dropping the collection and including the reference from initial creation works like a charm, too. Just the patching (so adding to an existing collection) seem to be cause the issue.