Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0042120Openbravo ERPA. Platformpublic2019-10-25 12:522022-02-01 07:24
ReporterAtulOpenbravo 
Assigned ToTriage Platform Base 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0042120: DB consistency in configScript is not shown as warning in update.database
DescriptionDB consistency in configScript is not shown as warning in update.database, when few candidates are removed in a cleanup process and configScript have references for theses candidates, while building application following information is seen in the logs

for eg:

[java] We didn't found the row that we wanted to change. Table:[AD_FIELD] PK[: 801022]
[java] We didn't found the row that we wanted to change. Table:[AD_FIELD] PK[: 801031]

This information is for the fields that were removed during Old Costing Cleanup.

This should appear as warning in the update.database task.
Steps To Reproduce-
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to feature request 00414213.0PR20Q1 closed AtulOpenbravo Unsupport legacy cost engine 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2019-10-25 12:52AtulOpenbravoNew Issue
2019-10-25 12:52AtulOpenbravoAssigned To => platform
2019-10-25 12:52AtulOpenbravoOBNetwork customer => No
2019-10-25 12:52AtulOpenbravoModules => Core
2019-10-25 12:52AtulOpenbravoTriggers an Emergency Pack => No
2019-10-25 12:52AtulOpenbravoRelationship addedrelated to 0041421
2022-02-01 07:24alostaleAssigned Toplatform => Triage Platform Base

There are no notes attached to this issue.