Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0008574 | Openbravo ERP | 02. Master data management | public | 2009-04-15 09:11 | 2009-09-30 00:00 |
|
Reporter | arunkumar | |
Assigned To | shuehner | |
Priority | low | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | |
Platform | | OS | 5 | OS Version | |
Product Version | main | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | No |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0008574: Error message for displaying the duplicate key of the business partner category should be user friendly |
Description | Creating a business partner category with the search key that was already existing throws an error message. But it is not user friendly. |
Steps To Reproduce | # Login as userA
# Go to Master data management->Business partner Setup->Business partner Category
# Click a new record and enter the search key "CRT" which was existing already.
An error message is displayed since the search key exists already.
ERROR: duplicate key value violates unique constraint "c_bp_group_value"
But that was not user friendly. |
Proposed Solution | The error message should be displayed like "A business partner category already exists with the same search key" |
Additional Information | |
Tags | No tags attached. |
Relationships | related to | defect | 0009781 | 2.50MP4 | closed | vmromanos | There are some incorrect translations in Spanish translation (I) | related to | defect | 0009384 | | closed | shuehner | Poor error message inserting a duplicated search key for business partners |
|
Attached Files | BusinessPartnerSearchKey.JPG (162,343) 2009-04-15 09:11 https://issues.openbravo.com/file_download.php?file_id=1179&type=bug

|
|
Issue History |
Date Modified | Username | Field | Change |
2009-04-15 09:11 | arunkumar | New Issue | |
2009-04-15 09:11 | arunkumar | Assigned To | => rafaroda |
2009-04-15 09:11 | arunkumar | File Added: BusinessPartnerSearchKey.JPG | |
2009-04-15 09:11 | arunkumar | OBNetwork customer | => No |
2009-04-15 09:11 | arunkumar | Regression testing | => No |
2009-04-15 09:44 | thirumalai | Note Added: 0015365 | |
2009-04-15 09:44 | thirumalai | Issue Monitored: thirumalai | |
2009-04-22 20:00 | psarobe | Status | new => scheduled |
2009-04-22 20:00 | psarobe | Assigned To | rafaroda => shuehner |
2009-04-22 20:00 | psarobe | fix_in_branch | => pi |
2009-09-15 19:36 | shuehner | Note Added: 0020094 | |
2009-09-15 19:36 | shuehner | Status | scheduled => feedback |
2009-09-15 20:28 | shuehner | Relationship added | related to 0009781 |
2009-09-15 20:29 | shuehner | Relationship added | related to 0009384 |
2009-09-29 10:00 | arunkumar | Note Added: 0020427 | |
2009-09-29 10:31 | shuehner | Status | feedback => closed |
2009-09-29 10:31 | shuehner | Note Added: 0020429 | |
2009-09-29 10:31 | shuehner | Resolution | open => no change required |
2009-09-30 00:00 | anonymous | sf_bug_id | 0 => 2870159 |
Notes |
|
|
Similar to issue - 0008553 |
|
|
|
Hi,
the current code uses auto-generated error messages if no special error message text for a constraint is present (like here).
The current (autogenerated) text for this case is:
An entry in BusinessPartnerCategory with the same (Client, Search Key) already exists. (Client, Search Key) must be unique.
Is this auto-text clear enough? Or do we still need a specialized manually written message here? |
|
|
|
Yes the following auto generated text is enough:
An entry in BusinessPartnerCategory with the same (Client, Search Key) already exists. (Client, Search Key) must be unique.
You mark the issue as resolved. |
|
|
|
No change required as the new auto-generated error message texts are good enough in this case. |
|