0034779: FIC check for "a column and an auxiliary input have the same name" could probably be done at compile time

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0034779

Openbravo ERP

A. Platform

public

2016-12-20 11:04

2022-02-01 08:09

Reporter

shuehner

Assigned To

Triage Platform Base

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0034779: FIC check for "a column and an auxiliary input have the same name" could probably be done at compile time

Description

There is some data validation running in the FormInitializationComponent which can reports errors like:

2016-12-20 10:42:42,680 [ajp-bio-127.0.0.1-8009-exec-27] ERROR org.openbravo.client.application.window.FormInitializationComponent - Error: a column and an auxiliary input have the same name in ADTab(FF80808130BB89090130BB9A3A2B0043) (name: Accounting, window: 94EAA455D2644E04AB25D93BE5157B6D). This will lead to wrong computation of values for that column.

For example as reported in 34778

From description and quick check of the code in method checkNamingCollisionWithAuxiliaryInput it looks like this check could be done at compile time which makes it much easier to mass-check (i.e. using ci)

Steps To Reproduce

Proposed Solution

Additional Information