{"section":"known-issues","requestedLocale":"en","requestedSlug":"creating-a-mandatory-active-sku-specification-is-not-inactivating-category-skus","locale":"en","slug":"creating-a-mandatory-active-sku-specification-is-not-inactivating-category-skus","path":"docs/en/known-issues/Catalog/creating-a-mandatory-active-sku-specification-is-not-inactivating-category-skus.md","branch":"main","content":"## Summary\n\nCurrently, when a mandatory specification is created **after** active skus are already present on a given category, they are not being inactivated.\n\nThe expected scenario, as per the UI warning below, is that when a mandatory specification is created on a category, all active skus on this given category are inactivated until the given specification has its values filled.\n\n ![](https://vtexhelp.zendesk.com/attachments/token/YYcHzuU2WkcD7DP1ZvcAOYm0J/?name=image.png)\n\nResult\n\n ![](https://vtexhelp.zendesk.com/attachments/token/Gn0CO1DGe9fxU0w066bZblOcX/?name=image.png)\n\n## Simulation\n\n1 - For a category that has 1+ active skus, go to the category menu (https://myaccount.myvtex.com/admin/Site/Campo.aspx)\n\n2 - create a new sku field filling in the \"isMandatory\" and \"isActive\" fields as true\n\n3 - The aforementioned display message of \"all skus will be inactivated\" will be shown\n\n4 - reacess the sku within this category no note that nothign has really happened, it will have reached an incorrect state of active skus with mandatory fields left empty.\n\n## Workaround\n\n-"}