Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2014-02-04T23:04:31Z by DonaldN
MatL
MatL
14 Posts
ACCEPTED ANSWER

Pinned topic Single unique key or compound - Can't import records with duplicate names - CRMUD0069E

‏2014-02-04T18:04:45Z |

I would like to see if anyone has had experience importing records with duplicate Name fields, even if a separate unique Id field is used. Either with just "TranducerId" as a unique key, or with both "TransducerId" and "Name" as a compound key, I get the import error when importing records having to do with this field:

CRMIR0008E Record validation failed!

Details=CRMUD0054E These fields have invalid values:

RecordImpactedTransducer...

   CRMUD0069E The field "RecordImpactedTransducer" has multiple entries which do not identify existing entities of type ImpactedTransducers:

   (None)

   3D6-2

Import example:

"TransducerId","Name","Project","Product"

"1115","(None)","ProjectA","ProductB"

"1107","(None)","ProjectA","ProductB"

See attachments for Designer-related info:

Thank you!

  • pdubovitsky
    pdubovitsky
    376 Posts
    ACCEPTED ANSWER

    Re: Single unique key or compound - Can't import records with duplicate names - CRMUD0069E

    ‏2014-02-04T18:57:40Z  in response to MatL

    Based on the error message, the problem is with "RecordImpactedTransducer" field data:
    "has multiple entries which do not identify existing entities of type ImpactedTransducers"

    It looks like the referenced field values (ImpactedTransducers) have not been imported (or created) in the database yet.

     

    Pavel

  • DonaldN
    DonaldN
    244 Posts
    ACCEPTED ANSWER

    Re: Single unique key or compound - Can't import records with duplicate names - CRMUD0069E

    ‏2014-02-04T23:04:31Z  in response to MatL

    You need to take multiple steps in the correct order in order to import the records with references and back references. When you import a reference field, the record that it references to has to exist, otherwise you will get errors similar to that you posted. Have a look at this technote, do some practice and you should get a better idea.

    http://www-01.ibm.com/support/docview.wss?uid=swg21126345