Skip to Content

To understand EMIGALL nested data structures

I am trying to understand the nested data structures in an EMIGALL data objects.  From the image below you can see a data object has a sub-object, and sub-sub-object and so on.... I wonder how this is setup?  Where do I go to see the hierarchy of the data structures?  How is data supposed to be populated?

Thanks!

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Oct 20, 2015 at 08:58 PM

    a method I use to work my way forwards on a given migration activity will be to

    1. enter the data import screen for the require migration object (shift+f6)
    2. on "Import File" tab, create a file
    3. on "Import File" tab, change the file
    4. in the "process import file screen" Create data object. (call it anything you want)
    5. in the "entry for legacy system key" pop up, click "specify data"
    6. this pops up a data entry screen relevant to the structure of the record data type you are interacting with.
    7. Click the tick to go back (you dont NEED to enter any data here)
    8. you will be presented with in the "entry for legacy system key" pop up again for the next structure in the sequence or the same structure if it supports multiple entries.
    9. repeat 5-7 f or click the next structure button (f5) depending on the structure you are simulating.
    10. end.

    Its easy to delete the sample key you have generated & start over till you get what you need.

    if anyone knows an easier way please let me know too 😉

    though its also pretty self evident once you have a few successful in my opinion.

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 20, 2015 at 10:02 PM

    Hi David.

    When in a migration object (for example, FACTS), click "Utilities - Structure display - Display customer structure". There, you will see entries like "Struct.:  EANLHKEY DataType:  KEY". It means that, in your text file, you should have a structure named "KEY", for example:

    ksm1 KEY data1 data2

    No matter how nested they are, they have their own unique identificator.

    Hope it helps.

    Marko

    Add comment
    10|10000 characters needed characters exceeded