Admin API call to UpdateCatalogItems with a CatalogVersion other than the primary causes the specified catalog to become the primary (and subsequently used in all calls where CatalogVersion is omitted). Is this intended behavior or a bug? At the very least it's undocumented (https://api.playfab.com/Documentation/Admin/method/UpdateCatalogItems).
This causes problems as we use different catalogs to store special meta items, and the game should always use our set primary catalog.
Steps to reproduce and verify:
- Create CatalogA and CatalogB where CatalogA is the primary.
- Verify that GetCatalogItems API call with no specified CatalogVersion return the items of CatalogA.
- Call UpdateCatalogItems with "CatalogVersion":"CatalogB" and arbitrary update data.
- Verify that GetCatalogItems API call without specified CatalogVersion now instead returns the items of CatalogB.
As a side note, in the dashboard CatalogA still has a star and is being marked as the primary. This is fixed by using "Edit Catalog" and saving (without performing any changes), which will correctly show that CatalogB is now the primary.