What about this in product_usability?
add a product.product menu in inventory settings?
to import all fields, you need to pass through the product.product menu. While in 90% of the cases we disables product variants.
product.template external ID utility
so once the power user imported the catalog using a product.product menu, what happens is that product.product records do have an external ID, but product.template records don't. But often you may have other related things to import (say secundary product unit) and these other objects can be carried by the product.template instead of the product.product so it's currently not easy for the user to import these things later...
What could we do? Have a button to populate the product.template external ids from the product product ones?
a bit related to https://github.com/akretion/pattern-import-export but may be we can have basics things here.
cc @clementmbr @kevinkhao @sebastienbeau
What about this in product_usability?
add a product.product menu in inventory settings?
to import all fields, you need to pass through the product.product menu. While in 90% of the cases we disables product variants.
product.template external ID utility
so once the power user imported the catalog using a product.product menu, what happens is that product.product records do have an external ID, but product.template records don't. But often you may have other related things to import (say secundary product unit) and these other objects can be carried by the product.template instead of the product.product so it's currently not easy for the user to import these things later...
What could we do? Have a button to populate the product.template external ids from the product product ones?
a bit related to https://github.com/akretion/pattern-import-export but may be we can have basics things here.
cc @clementmbr @kevinkhao @sebastienbeau