Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0049187 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Openbravo ERP] A. Platform | minor | have not tried | 2022-05-03 11:24 | 2022-05-03 12:02 | |||||||
| Reporter | caristu | View Status | public | |||||||||
| Assigned To | Triage Platform Base | |||||||||||
| Priority | high | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| Summary | 0049187: Is not possible to have a display logic for a button based in a property field | |||||||||||
| Description | Is not possible to have a display logic for a button based in a property field | |||||||||||
| Steps To Reproduce | Found this trouble in the EDL module that has a window that makes this issue reproducible. 1- As system admin go to the [Windows, Tabs and Fields] window 2- Create a property field using the property "eDLProcess.reprocessPolicy" as shown in the attached image. 3- Note that the window has an auxiliary input to get the reprocess policy, and the "Process" button has a display logic based on it. But now, the display logic will be calculated based on the newly added property field. 4- Try to access to the EDL process window. An error is shown and the following stacktrace appears in the log: Caused by: org.openbravo.base.util.CheckException: Property with Reprocess_Policy does not exist for entity OBEDL_Request at org.openbravo.base.model.Entity.getPropertyByColumnName(Entity.java:591) ~[classes/:?] at org.openbravo.client.application.window.OBViewFieldHandler.getFields(OBViewFieldHandler.java:163) ~[classes/:?] at jdk.internal.reflect.GeneratedMethodAccessor498.invoke(Unknown Source) ~[?:?] | |||||||||||
| Proposed Solution | This is the code[1] that throws the exception. It seems that it does not take into account the case of the field being a property field. [1] https://gitlab.com/openbravo/product/openbravo/-/blob/master/modules/org.openbravo.client.application/src/org/openbravo/client/application/window/OBViewFieldHandler.java#L161 [^] | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|||||||||||||||||
|
|||||||||||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2022-05-03 11:24 | caristu | New Issue | |
| 2022-05-03 11:24 | caristu | Assigned To | => Triage Platform Base |
| 2022-05-03 11:24 | caristu | Modules | => Core |
| 2022-05-03 11:24 | caristu | Triggers an Emergency Pack | => No |
| 2022-05-03 11:55 | caristu | Relationship added | related to 0044945 |
| 2022-05-03 12:02 | caristu | Proposed Solution updated | |
| 2022-05-03 12:02 | caristu | Proposed Solution updated | |
| 2022-05-03 12:06 | caristu | Relationship added | blocks 0049191 |
| 2022-05-03 12:06 | caristu | Relationship deleted | related to 0044945 |
| 2022-08-24 10:53 | caristu | Relationship added | has duplicate 0050045 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |