{"section":"known-issues","requestedLocale":"en","requestedSlug":"subaccounts-are-not-automatically-allocated-to-a-cluster","locale":"en","slug":"subaccounts-are-not-automatically-allocated-to-a-cluster","path":"docs/en/known-issues/Storage/subaccounts-are-not-automatically-allocated-to-a-cluster.md","branch":"main","content":"## Summary\n\n\nSubaccounts are not automatically allocated to a cluster upon creation. As a result, masterdata search do not function correctly for these subaccounts.\n\n\n#### Simulation\n\n\n\n1. Create or access a subaccount that has not been manually allocated to a cluster.\n2.\n\nAttempt to call the Masterdata Search API, such as:\n\n    GET https://..com/api/dataentities/CL/search?_fields=id\n3. Observe that the response returns an 500 error indicating that the masterdata search is not functioning.\n\n\n#### Workaround\n\n\nThe API from this documentation can also allocate an account to a cluster - Customer and address forms do not exist in multistores. To use it the user must have the resource ADMIN_DS on its role."}