Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] B. User interfaceminoralways2014-02-06 16:352014-03-27 14:05
ReporterchelipfView Statuspublic 
Assigned ToAugustoMauch 
PrioritynormalResolutionno change requiredFixed in Version
StatusclosedFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version3.0PR14Q2
OSLinux 64 bitDatabasePostgreSQLJava version1.6.0_27
OS VersionDebian WheezyDatabase version9.1Ant version1.8.2
Product Version3.0MP31SCM revision 
Review Assigned To
Web browserMozilla Firefox
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0025678: When creating a new line, @variable@ of a combo is set with the old default value.

DescriptionFor example, you have in a tab a column ad_user_id as a table reference (references to AD_USER table) and the default value (as a result of the select sentence that fills the combo) when the combo is painted in the user interface is Cheli (ad_user_id = '525AF15DEFF14C948C396D4718A7A8A3'). If a create a new line in my tab then the @AD_User_ID@ is set to '525AF15DEFF14C948C396D4718A7A8A3' when it should be null because it is a "new" line without any value in that moment.
Steps To Reproduce-Create a new line in any tab, that tab must contain a combo box (tabledir, table, etc) and should be a mandatory field. The @variable@ then is set with the value it is filled in.
-Create another line. The @variable@ value by default will be set with the old @variable@ one.
- If you log out and log in again @variable@ is set to null by default. After the first insert it is set again with the old @variable@ value every time yo insert a new line.
Proposed SolutionEvery time you create a new line all the @variable@ values must be set to null by default.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to feature request 0025762 newAugustoMauch To be able to set a table /tabledir columns as unique relative to its master tab if exists. 
related to feature request 0026111 newAugustoMauch Add a flag at column level to avoid the load of the value stored in session in the initial value of the variable 

-  Notes
alostale (manager)
2014-03-12 11:23

Adding more info:
- Tenemos una solapa con un campo propio, por ejemplo usuario.
- La primera vez que accedemos a la ventana, el valor de la variable usuario
- Guardamos el valor X
- Le damos a nuevo, el valor de la variable @PREFIX_AD_USER_ID@ es X, en vez de ser nulo.
Es decir, es como si la segunda y siguientes veces, el valor por defecto de la variable @PREFIX_AD_USER_ID@ fuera el Ășltimo valor guardado. Esto hace que dĂ© problemas al utilizar el campo @PREFIX_AD_USER_ID@ en validaciones, auxiliar inputs...
chelipf (reporter)
2014-03-18 17:44

This is the validation rule I use:

sfb_budget_area_id not in (select sfb_budget_area_id from sfb_budget_user_area where ad_user_id = @AD_User_ID@ and sfb_budget_area_id is not null and (sfb_budget_area_id <> @Sfb_Budget_Area_ID@ or @Sfb_Budget_Area_ID@ IS NULL))
AugustoMauch (manager)
2014-03-18 21:10

After discussing it with the reporter, it seems that the problem is that the flag 'Store in Session' is checked for the column whose value is being initialized from the last value used for that column. This is the expected behaviour for Stored in Session columns.

The reporter is going to check if it is possible to unset this flag, and to see if in that case the problem is no longer reproducible.
chelipf (reporter)
2014-03-19 00:03

I have checked it and it works as you expect when the variable is not set as stored in session, but the problem persists when it is.

I still think that even when it is stored in session the variable must be set with the default field value, null or anything the default value could be, when creating a new line (pristine) and the form is loaded for the first time, instead of still be set with the old stored in session one. It is supposed that the default value of that variable when you start to fill out the form is null or the default one you define in the application dictionary. As we have talk this evening it could be a new feature for next releases.

Thank you Augusto.

- Issue History
Date Modified Username Field Change
2014-02-06 16:35 chelipf New Issue
2014-02-06 16:35 chelipf Assigned To => dbaz
2014-02-06 16:35 chelipf Web browser => Mozilla Firefox
2014-02-06 16:35 chelipf Modules => Core
2014-02-06 16:35 chelipf Triggers an Emergency Pack => No
2014-02-10 23:07 chelipf Tag Attached: Sidesoft
2014-02-19 18:09 jonalegriaesarte Web browser Mozilla Firefox => Mozilla Firefox
2014-02-19 18:09 jonalegriaesarte Target Version => 3.0MP32
2014-02-19 18:09 jonalegriaesarte Assigned To dbaz => AugustoMauch
2014-03-11 13:19 jonalegriaesarte Web browser Mozilla Firefox => Mozilla Firefox
2014-03-11 13:19 jonalegriaesarte Resolution time => 1394838000
2014-03-12 11:23 alostale Note Added: 0065093
2014-03-18 11:26 AugustoMauch Status new => scheduled
2014-03-18 11:26 AugustoMauch fix_in_branch => pi
2014-03-18 17:44 chelipf Note Added: 0065272
2014-03-18 21:10 AugustoMauch Note Added: 0065278
2014-03-18 21:10 AugustoMauch Status scheduled => feedback
2014-03-19 00:03 chelipf Note Added: 0065282
2014-03-27 14:04 jonalegriaesarte Relationship added related to 0025762
2014-03-27 14:05 jonalegriaesarte Status feedback => closed
2014-03-27 14:05 jonalegriaesarte Resolution open => no change required
2014-03-27 14:08 jonalegriaesarte Relationship added related to 0026111

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker