{"section":"known-issues","requestedLocale":"en","requestedSlug":"manually-changing-flagsku-in-the-url-allows-a-specification-type-to-be-improperly-changed","locale":"en","slug":"manually-changing-flagsku-in-the-url-allows-a-specification-type-to-be-improperly-changed","path":"docs/en/known-issues/Catalog/manually-changing-flagsku-in-the-url-allows-a-specification-type-to-be-improperly-changed.md","branch":"main","content":"## Summary\n\n\nCurrently, when an specification is created, it's set as either a SKU or Product type and this should not be changed after its creation.\n\nHowever, there a glitch in the catalog admin that allows these fields to be incorrectly changed from their original type (from SKU to product or vice-versa), when manipulating the URL of the admin page.\n\n\n##\n\n## Simulation\n\n\n1 - access a product specification list in your account https://account_name.myvtex.com/admin/site/Campo.aspx\n\n2 - create a specification and hit save\n\n3 - its format will have the following query parameters (example) ...CampoForm.aspx?Id=20&**flagSku=0**&idCategoria=3 --> the \"flagSKu\" data = 0 means it is a product specification.\n\n4 - change this flag to =1 and hit enter.\n\n5 - Upon reloading the page, hit save.\n\n6 - the product specification was now converted to a product specification, which is not a desired behaviour in the catalog.\n\n\n##\n\n## Workaround\n\n\n-"}