[
https://issues.apache.org/jira/browse/OFBIZ-10124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16303296#comment-16303296 ]
Timothy Boyden commented on OFBIZ-10124:
----------------------------------------
STEP 1: Navigate to Web Tools
STEP 2: Click Import/Export tab
STEP 3: Click XML Data Import
STEP 4: In Absolute Filename or URL Type: C:\temp\ofbiz-import\Party.xml
STEP 5: Click Import File button
Repeat Steps 4 & 5 for PartyGroup.xml. ContactMech.xml, PartyContactMech.xml. PartyContactMechPurpose.xml, PostalAddress.xml, and TelecomNumber.xml.
STEP 6: Navigate to Party Manager
STEP 7: Click Create New Party Group button
STEP 8: Fill in Party Group details
STEP 9: Click Save button
STEP 10: Click Search button on Find Party screen
STEP 11: Click newly created Party
STEP 12: Under Contact Information, click Create New button
STEP 13: For Select Contact Type. choose Postal Address, then click the Create button
STEP 14: Fill in Postal Address details and click Save button
STEP 15: Under Contact Information, click Create New button
STEP 16: For Select Contact Type. choose Phone Number, then click the Create button
STEP 17: Fill in Phone Number details and click Save button
Errors generated as noted in attached log. Summary - an error for key conflict was generated for each ContactMech Id that was imported. Key # incremented from 10000 to 10041 until it finally allowed the save to occur.
> Key conflict error for new Telecom Contact Mech record after ContactMech import
> -------------------------------------------------------------------------------
>
> Key: OFBIZ-10124
> URL:
https://issues.apache.org/jira/browse/OFBIZ-10124> Project: OFBiz
> Issue Type: Bug
> Affects Versions: Release Branch 16.11
> Environment: Windows 10 Professional x64. Java 8 JDK 152. MS SQL 2017 Linux Docker image.
> Reporter: Timothy Boyden
> Labels: contactmech, entityengine, keyvalue, telecom
> Attachments: ContactMech_TelecomNumber_KeyConflict_AfterImport_error-2017-12-23-2.log
>
>
> I imported 10 Party, 40 ContactMech, 10 PostalAddress, and 22 TelecomNumber records from another install of OFBiz, same release (16.11.03). I added a new Party, and a new PostalAddress ContactMech record no problem. I went to add a TelecomNumber ContactMech record for the same new Party, and received a key conflict error. I hit save again and could see that the error messages were incrementing the ContactMech key through all of the imported record's Id keys. After the 41st attempt to save the record, the Telecom record finally saved. It would seem the mechanism that the TelecomNumber ContactMech type uses to detect the next ContactMech key is not reading the SEQUENCE_VALUE_ITEM table to get the next key. Log attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Locked
