Description: This solution describes how to map notepads in a profile
The value you wish to import for Type must exist in the Notepad Types table in RE, or you must have the option in your profile, under General Settings, checked to "Add New Table Entries value if it does not already exist". You must also have sufficient rights in RE to add to this table if you wish to add the value during the import.
Notepad Type is always the Parent field, because it is the only one RE requires by default for Notepad entries. Since Type is the Parent field, always map it first. We are going to pretend you have mapped Notepad Type in Field B for this explanation.
Then you will map the other pieces of the note, such as Description and Notes. These are the Child fields of Type. After you choose their respective Record Types, you will need to map the Value Types. Continue to bear in mind that this is a Parent/Child relationship. The Value Type for Description and Notes will be, in this example, "Field B" because this is the location of the Parent field. This will be your only choice in the Value Type column if you have only one Type mapped.
What this tells IOM is to go look in the data file for the actual value, but link it to the Type in Field B. It works this way because we allow you to bring in multiple Notepad entries at once, and we need to tell IOM to which notepad to add the different notes, descriptions, titles and authors.
For versions 188.8.131.52 and Earlier:
For version 3.4 and Later:
If you have multiple Notepad entries to import in the same file, you may find it easier to map each set one at a time to make knowing which Parent field goes with which set of Child fields.
Refer to the ImportOmatic User Guide for additional information.