Yoshi Tashiro (Quartile)

Here is a PR, but it seems it is on hold for now: https://github.com/pledra/odoo-product-configurator/pull/109

@samlopezf I just created a module to handle this requirement by extending `product_configurator_mrp`: https://github.com/yostashiro/odoo-product-configurator/tree/10.0-ext-configurator-mrp/product_configurator_mrp_ext This module also incorporates the content of https://github.com/pledra/odoo-product-configurator/pull/109 for now. I created a separate module instead...

@PCatinean Thanks for confirming the issue! Here is a workaround if anyone is interested: https://github.com/rfhk/cip-custom/tree/d3dff5f9776cba2428f79c1477a8902b29ae06fc/product_configurator_adj/views I can create a PR if this is the way to handle this issue.

Haven't checked in detail, but this https://github.com/odoo/odoo/pull/26133 may be related to the issue.

Looks like this report is about 16.0. `purchase_analytic` doesn't really change `analytic_distribution` of `purchase.order.line`, so I am not sure how it would affect the query where the error is thrown...

Yes, let's make it LGPL. @jdidderen-noviat Do you have some specific inconveniences in mind if we do not make the field stored?

A quick workaround I can think of is to shorten the field name to something like `analytic_acct_ids` which should keep the table name within 63-char limit.

Oh yes, that's right. Sorry.

@AungKoKoLin1997 Can you please rebase and push?

@AungKoKoLin1997 Contrary to my previous advice, have you thought about extending `_get_consumption_issues()` of mrp.production? I now think that the design will be more in line with the standard feature that...