{"section":"known-issues","requestedLocale":"en","requestedSlug":"activateifpossible-set-to-false-if-mandatory-specifications-are-not-fully-saved-on-catalog-admin","locale":"en","slug":"activateifpossible-set-to-false-if-mandatory-specifications-are-not-fully-saved-on-catalog-admin","path":"docs/en/known-issues/Catalog/activateifpossible-set-to-false-if-mandatory-specifications-are-not-fully-saved-on-catalog-admin.md","branch":"main","content":"## Summary\n\nCurrently, the product ActivateIfPossible field in the catalog admin, of a product, is incorrectly set to \"false\" when an user tries to save the product specifications and there is still a mandatory specification not yet filled upon saving\n\n## Simulation\n\n1 - create an inactive product with at least one sku and mandatory specifications (2+) not yet filled.\n\n2 - also, for this product, create it with the activateIfPossible field set to \"True\"\n\n3 - after its creation, on the catalog admin, edit the product and attempt to save it with some, but not all, mandatory specifications filled.\n\n4 - The activateIfPossible field will beset to \"false\" incorrectly and consequently the product will not be automatically set to active after all fields and other criteria are met.\n\n## Workaround\n\nUse APIs to save the specifications or save all mandatory specifications at once in the admin"}