You have to go into the Preferences and under duplicates set "Handle Duplicate Request ID's By:" to Replace Old Record with New Record. That should work for you. And of course, keeping the request id fields mapped is crucial.
Brian Goralczyk Phone 574-643-1144 Email [email protected] On Mon, Mar 2, 2015 at 10:48 AM, Carina Burns <[email protected]> wrote: > So it turns out I have to do a definition and data import to upgrade us to > 8.1.02 since we have only custom apps and can't get the upgrade done in > steps/versions. I started the process only to find something badly wrong > when I double checked my data. > > The parent/child relationship between form record sets is lost as the > import tool is sequentially re-numbering the issue id field in the parent > form, DESPITE it being mapped when I do the import. The data was exported > using the 7.1 client tool as a report in .arx format. All other fields are > correct, attachments load correctly, only the entry id is wrong. I have > tried resetting the nextid number via the ARSCHEMA and re-importing. > However, as there are deleted records in the original dataset, the sequence > is again thrown off as soon as the numbering skips. Changing the "Handle > duplicate request id" settings to makes no difference. > > I would have thought that if the Issue ID field is mapped, that the > original ticket number would be retained. What am I doing wrong here? > This makes no sense. Surely there is some config I've failed to setup. > I'd really hate to do alter the new form tables and do a table copy with > sql commands. > > Suggestions? > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
