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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Retail Modules] Retail APImajoralways2023-06-15 09:462023-06-26 07:03
ReporterngarciaView Statuspublic 
Assigned Toranjith_qualiantech_com 
PriorityurgentResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0052748: Currently it is not possible to uniquely identify a contact of a business partner

DescriptionCurrently, it is not possible to uniquely identify a contact of a business partner

The contacts of a business partner are created without username, so it is not possible to uniquely identify them
Steps To ReproduceAdd two contacts with the same first and last name to a business partner

Try to import it through JSON Based Import Process EDL Process and check the EDL Request finishes with the following error:

Error while importing an item: query did not return a unique result: 2

The log shows:

Caused by: org.hibernate.NonUniqueResultException: query did not return a unique result: 2
    at org.hibernate.query.internal.AbstractProducedQuery.uniqueElement( ~[hibernate-core-5.6.0.Final.jar:5.6.0.Final]
    at org.hibernate.query.internal.AbstractProducedQuery.uniqueResult( ~[hibernate-core-5.6.0.Final.jar:5.6.0.Final]
    at org.openbravo.dal.service.OBQuery.uniqueResult( ~[classes/:?]
    at org.openbravo.service.external.integration.importer.DalSynchronizableBusinessObjectImporter.getBobFromUniqueProperties(
Proposed SolutionIssue changed from Design Defect to Defect as we need to fix the fact that "Last Name" "Name" can not be used to uniquely identify Contacts.

The proposal is by now, use the property "Phone" as the parameter to identify a contact uniquely.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0052562 closedranjith_qualiantech_com Business Partner update through JSON Based Import Process EDL process fails if the bp has two contacts with same name 

-  Notes
hgbot (developer)
2023-06-22 06:29

Merge Request created: [^]
hgbot (developer)
2023-06-26 07:03

Directly closing issue as related merge request is already approved.

Repository: [^]
Changeset: 87c7b023567f2886cd709a4844623151a554e139
Author: Ranjith S R <>
Date: 23-06-2023 13:31:44
URL: [^]

Fixed ISSUE-52748: Phone should be unique identifier of ContactInfo
* Phone property should be not null and unique identifier
  when importing BusinessPartner/ContactInfo

M examples/Openbravo API.postman_collection.json
M src-db/database/sourcedata/OBEI_PROP_MAP_INSTANCE.xml
hgbot (developer)
2023-06-26 07:03

Merge request merged: [^]

- Issue History
Date Modified Username Field Change
2023-06-15 09:46 ngarcia New Issue
2023-06-15 09:46 ngarcia Assigned To => Triage Platform Conn
2023-06-15 09:46 ngarcia Triggers an Emergency Pack => No
2023-06-15 09:46 ngarcia Relationship added related to 0052562
2023-06-16 15:14 psanjuan Assigned To Triage Platform Conn => psanjuan
2023-06-16 15:14 psanjuan Proposed Solution updated
2023-06-19 12:01 psanjuan Assigned To psanjuan => Retail
2023-06-19 12:01 psanjuan Type design defect => defect
2023-06-19 12:01 psanjuan Proposed Solution updated
2023-06-19 12:34 ranjith_qualiantech_com Assigned To Retail => ranjith_qualiantech_com
2023-06-19 14:57 ranjith_qualiantech_com Status new => scheduled
2023-06-22 06:29 hgbot Note Added: 0151467
2023-06-26 07:03 hgbot Resolution open => fixed
2023-06-26 07:03 hgbot Status scheduled => closed
2023-06-26 07:03 hgbot Note Added: 0151613
2023-06-26 07:03 hgbot Note Added: 0151614

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker