{"section":"known-issues","requestedLocale":"en","requestedSlug":"kit-created-by-integration-doesnt-receive-a-table-of-values","locale":"en","slug":"kit-created-by-integration-doesnt-receive-a-table-of-values","path":"docs/en/known-issues/Marketing & Merchandising/kit-created-by-integration-doesnt-receive-a-table-of-values.md","branch":"main","content":"## Summary\n\nThe kit created by integration is not creating a values table even after a price component is added. \n\nThis behavior is partly due to the fact that the feature does not accept a default value in kit creation. For one of the characteristics of a kit is that the shopkeeper can practice a price different from that of the component.\n\n## Simulation\n\nCreate a kit via Web Service (Soap) (Only possible via Web Service)\n\n**Step 1**:\n[Download the integration manual](https://help.vtex.com/en/tutorial/manual-of-classes-and-methods-used-on-webservice)\n\n**Step 2**:\nRun kit creation route: `StockKeepingUnitKitInsertUpdate`\n\n## Workaround\n\nTo work around this problem, the path is quite simple. Looking at the kit, follow the path described below:\n\nBlue Arrow > SKU > Grey Arrou (edit) > Kit > Change > Save\n\nThe component must have a price already registered. Here we're just saving the form again to force indexing. To verify it, just see the table of values associated with the SKU Kit.\n\nTo solve this problem through API, simply add a value table creation route for SKU (after you've created the kit): https://documenter.getpostman.com/view/101975/vtex-pricing-api/6YsWxKT#06450a0e-a7b4-360c-7058-3095cd03ef08"}