Chip, I'm going to guess the issue was with the Parent records. What is it? It could be a number of things especially if this is a mature project that's already been through several previous upgrades. My first hunch is that there's something in the data of a few fields that's causing some esoteric collision and 4D just says, "forget this" and moves on.
If you have multiple datafiles to convert then you'll want to figure it out. If you only need to convert the one datafile and you can import the missing records I'd focus on verifying it and not worry about why the conversion was weird. You only need a valid datafile at the end of the day and life is too short. On Wed, Mar 29, 2017 at 1:37 PM, Chip Scheide via 4D_Tech < [email protected]> wrote: > So - I m moving a v12 application to v13 (I'm getting closer to current > version : ) ) > > I am testing the conversion of the data file. > There are structural changes between the versions. > > I took a copy of the live (v12) data file, and opened it in the new > structure (v13) > 4D converted the datafile, then my conversion code ran, and everything > seemed to be OK. > > I am going through the data to see that everything actually moved > correctly. > I found a discrepancy, in one table there is about 1% of the records > which were NOT in the converted data file, along with their child > records (Requisition and line items for the requisitions). > > Exporting these records from the live data and importing into the new > version appears to work. > > So... my question is: > What is going on?? > Why are the parent and child records missing? > Ideas? > > -- Kirk Brooks San Francisco, CA ======================= ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
