Hi Team, we have this error happening when trying to update a workspace

Some of given referenced 'createdBy' entities do not exist. Not existing IDs: [Identifier(fundingcircle)/Organization(invblp2fgi)] - status: 400

but point is, we don't even use separate Organisations per customer, so we have no Organisations registered in our account, how could they have created a resource using a completely separate organisation?

New message text here

@kapa.ai if a user is deleted, are the insights created by them still kept?

A message from kapa.ai

ok, but I would like someone from support to check if this is true, as we didn't delete any users

We will review this and get back to you with more details 🙂

Hi Jhonatan, just to be sure, what we’ve confirmed on our side is that deleting a user who originally created a dashboard or insight does not break the content. When the creator user is removed, GoodData automatically removes the

createdBy

reference from the metadata. The object remains editable, and when another user modifies it, a valid

modifiedBy

is added. We were able to delete the creator user and continue editing the dashboard with another admin user without seeing any errors. Please note that this test was done by creating and editing a dashboard directly from the UI, without knowing which action on 'update a workspace' you are performing. That said, since you’re seeing this error and you’re confident no users were deleted, it would be helpful to better understand what exactly you’re doing and how. Any additional details will help us make sure we’re on the same page. In particular, feel free to share: • The workspace ID • The exact operation that fails (UI action or API call) • The user performing the action This will allow us to confirm whether this is expected behavior in your environment or something that needs to be fixed.

Untitled

When you use the declarative APIs (PUT on the workspace layout), these fields are validated: if you send a

createdBy

that does not correspond to an existing user in the organization, the request fails with a 400 error, which is what you are seeing. To move forward I would suggest: Export a fresh layout of the workspace using the declarative layout GET endpoint: This gives you the current, valid state of the workspace, including only

createdBy

/

modifiedBy

references that the server currently accepts (or with those fields already removed if the original users were deleted). [*Workspace declarative API*; Object authors and editors] Use this fresh layout as your new baseline: Re‑apply only the changes you actually need on top of this new file. In particular, check any objects that still contain

createdBy

and make sure they reference valid users in your organization. PUT the updated layout back: If the PUT succeeds when using the freshly exported layout (with or without minimal edits), it confirms that the original error was caused by stale or invalid metadata in the older layout file (such as the

createdBy: "fundingcircle"

reference). If you still see the same error even after working from a fresh export, please let us know the workspace and the exact payload you’re PUT‑ing so we can investigate further.