You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, we're planning to port to 14 several assortment modules:
website_sale_product_assortment (once it will be ready)
stock_picking_product_assortment
product_pricelist_assortment
sale_order_product_assortment
While doing this, we realized that:
once there will be many assortments records in a db, it can become difficult to keep track what is the purpose of each assortment (was it created for website? for stock picking? for sales?)
every assortment created applies automatically to every context, so there isn't the possibility to define case: "Customer 1 can purchase products 1, 2, 3 on website, while on SO they can purchase products 1, 2, 3, 4, 5"
The idea is to add an applicability flag (eg: "apply to sales", "apply to website") to each module extending product_assortment to be displayed in the assortment form, in order to be able to decide where to use or not a certain assortment.
How do you suggest to proceed with this? add this change directly to migrations to 14, since none of these modules are migrated (therefore in use)? or do you suggest another approach?
There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.
Hi, we're planning to port to 14 several assortment modules:
website_sale_product_assortment (once it will be ready)
stock_picking_product_assortment
product_pricelist_assortment
sale_order_product_assortment
While doing this, we realized that:
The idea is to add an applicability flag (eg: "apply to sales", "apply to website") to each module extending product_assortment to be displayed in the assortment form, in order to be able to decide where to use or not a certain assortment.
How do you suggest to proceed with this? add this change directly to migrations to 14, since none of these modules are migrated (therefore in use)? or do you suggest another approach?
tagging contributors for comments, @rousseldenis @CarlosRoca13 @pedrobaeza :)
The text was updated successfully, but these errors were encountered: