Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0052606Openbravo ERP00. Application dictionarypublic2023-05-30 00:382023-06-23 14:48
Reporteraxelmercado 
Assigned ToTriage Platform Base 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0052606: Unable to create a computed column for m_offer_product table
DescriptionThe partner Practics has reported that they are trying to create a computed column in the m_offer_product table which generates the attached error (img1).

For our part, we have investigated and also reproduced the problem in a clean environment, also can not create the computed column in a pristine, always in the m_offer_product table, it generates the second attached error (img2).
Steps To Reproduce1-In the backoffie, create a computed column in the m_offer_products table. For example with the following query: (select pricelist from m_productprice where m_productprice.m_product_id=m_product_id limit 1).

2- Create a new field for the computed column in the "Products" tab for the "discount and promotions" window.

3- Export the changes, compile and build the environment.

4- Login to the client, go to the Discount and promotions window, select a value and try to open the "Products" tab.

5- Verify that it shows an error, whatever the query is.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 0052859 closed AugustoMauch It is not possible to have computed columns both in m_product and m_offer_product 
Attached Filespng img1.png (141,275) 2023-05-30 00:39
https://issues.openbravo.com/file_download.php?file_id=18598&type=bug
png

png img2.png (203,795) 2023-05-30 00:39
https://issues.openbravo.com/file_download.php?file_id=18599&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2023-05-30 00:38axelmercadoNew Issue
2023-05-30 00:38axelmercadoAssigned To => Triage Platform Base
2023-05-30 00:38axelmercadoModules => Core
2023-05-30 00:38axelmercadoTriggers an Emergency Pack => No
2023-05-30 00:39axelmercadoFile Added: img1.png
2023-05-30 00:39axelmercadoFile Added: img2.png
2023-05-30 07:16PracticsIssue Monitored: Practics
2023-06-02 01:37ivazquezIssue Monitored: ivazquez
2023-06-05 23:19ivazquezNote Added: 0150758
2023-06-12 15:06AugustoMauchNote Added: 0151061
2023-06-12 15:06AugustoMauchStatusnew => closed
2023-06-12 15:06AugustoMauchResolutionopen => no change required
2023-06-12 15:08PracticsNote Added: 0151062
2023-06-23 14:48AugustoMauchNote Added: 0151567
2023-06-27 18:14AugustoMauchRelationship addedduplicate of 0052859

Notes
(0150758)
ivazquez   
2023-06-05 23:19   
Hello Team

There is any update related to this issue?

Regards,
Ignacio Vazquez
(0151061)
AugustoMauch   
2023-06-12 15:06   
There is no issue, the query just requires to use an alias, replace

select pricelist from m_productprice where m_productprice.m_product_id=m_product_id limit 1

with

select pp.pricelist from m_productprice pp where pp.m_product_id=m_product_id limit 1
(0151062)
Practics   
2023-06-12 15:08   
Why? If it's not normally required.
(0151567)
AugustoMauch   
2023-06-23 14:48   
Why? If it's not normally required -> I reviewed all the computed columns currently defined in our standard modules and all of them have aliases