Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Processing | ||||||||
Line: 43 to 43 | ||||||||
The 'Raw Data' option displays all the extracted identifiers and the associated data: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
The columns have the following meanings: | ||||||||
Line: 52 to 52 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < | You can click on any row, and the system will drill down to show the elements (if any). For example, clicking on Rid 10 would display the 4 child elements. | |||||||
> > | You can click on any row, and the system will drill down to show the elements (if any). For example, clicking on Rid 24 would display the 8 child elements. | |||||||
All Elements/Data ElementsThe 'All Elements' and 'Data Elements only' display the same information, the only difference is the 'Data Elements only' will only show you the elements that contain data: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
The columns have the following meanings: | ||||||||
Line: 117 to 118 | ||||||||
When you run 'Define Field Map' you will see the following display: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
This is where we define how each Appx field should be populated. If you ran the 'Populate Field Map' option in the previous step, then this display will be populated with all the fields in the selected file(s). If you did not do that, you have to manually add each field we are importing. | ||||||||
Line: 129 to 130 | ||||||||
| ||||||||
Added: | ||||||||
> > | The XML Tag Type indicates which tag type this mapping is applicable to. Most data will be in the TEXT tag type, however, if your incoming data contains something like <phone> </phone>, the whitespace will not trigger a TEXT record in XVALUE. In this case, you might want to add another mapping triggered by the END ELEMENT tag. You can then use a subroutine to check values, etc, as required. | |||||||
Store MapThis option allows you to save the current mapping. | ||||||||
Line: 172 to 174 | ||||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Processinghis page describes the various processing and updating options. | ||||||||
Line: 26 to 26 | ||||||||
The title will default to your user initials, plus the current date/time. You can change this if you wish. You can drag and drop an XML file, or use the file chooser. Currently 0DX only supports XML, you cannot change that. The 'Hide Errors/Warnings' flag normally suppresses any problems with the source file. If you are having problems importing a file, you can uncheck this flag to see if there are any formatting problems with the incoming data. | ||||||||
Changed: | ||||||||
< < | Refer to the Tutorial or the Reference for a discussion of Ignorable / Replaceable segments. | |||||||
> > | Refer to the Tutorial or the Reference for a discussion of Ignorable / Replaceable segments. | |||||||
Once you click 'Execute' the tags and data will be extracted from the XML file and it will be ready for further review and/or importing in the next step.
View/Modify Processed Files & Import | ||||||||
Line: 43 to 43 | ||||||||
The 'Raw Data' option displays all the extracted identifiers and the associated data: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
The columns have the following meanings: | ||||||||
Line: 60 to 60 | ||||||||
The 'All Elements' and 'Data Elements only' display the same information, the only difference is the 'Data Elements only' will only show you the elements that contain data: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
The columns have the following meanings: | ||||||||
Line: 73 to 73 | ||||||||
You can click the 'Data Values' button for any selected row, and you will get a display of all the actual data values for each occurence of the element: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
The 'Data Values' option shows us the same information as above, but not constrained to any element, ie, we can scroll thru all the extracted data.
Refining | ||||||||
Line: 83 to 83 | ||||||||
In the 'Ignorable Segments' popup we can specify segments that are to be ignored (removed) when extracting the identifiers. For example, if 'ProspectData' was the top level identifier and is prefixed on all identifiers, we can remove it by entering 'ProspectData' as a segment to be ignored. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Replaceable Segments'Replaceable Segments' are used for a very particular situation. Consider the following XML fragment: | ||||||||
Line: 92 to 92 | ||||||||
Notice that the Segments all have the same name (j2:feature), and the identifier is really encoded in the attribute (name="..."). In this case, we can use the Replaceable Segments to move the attribute to the segment, which will allow us to map the segment to an Appx field: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Now our segment names will become "SourceName", "FileSystemProperties", "Path", "LastModified" instead of "j2:feature"
Regenerate Elements | ||||||||
Line: 105 to 105 | ||||||||
When you run 'Define File Map' you will see the following display: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
If you provided a map when you loaded the source file, then any existing File Mappings will be shown. The columns have the following meaning: | ||||||||
Line: 117 to 117 | ||||||||
When you run 'Define Field Map' you will see the following display: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
This is where we define how each Appx field should be populated. If you ran the 'Populate Field Map' option in the previous step, then this display will be populated with all the fields in the selected file(s). If you did not do that, you have to manually add each field we are importing. | ||||||||
Line: 133 to 133 | ||||||||
This option allows you to save the current mapping. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
If you enter the name of an existing mapping, it will be overwritten with the new mapping.
Retrieve MapThis option allows you to load an existing mapping. After loading it, you can refine it using the 'Define File Map' and 'Define Field Map' options, then save it under a new name or replace the original, using the 'Store Map' option. | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
ProcessingCreate Import SubrThis option will create a subroutine that does the work of importing the XML data into our Appx files: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
Fill in any Application and Process Name you want. When you click 'Proceed', the subroutine will be written and compiled. If any errors occur during the compile, you can view the subroutine in Application Design. You can also further customize the subroutine, however, you will lose those changes if you 'Create Import Subr' again.
Import Data | ||||||||
Line: 157 to 157 | ||||||||
This option will upload the data and run the import subroutine, all in one step. When you choose this option, you should see the following display: | ||||||||
Changed: | ||||||||
< < | ||||||||
> > | ||||||||
The title will default to your user initials, plus the current date/time. You can change this if you wish. You can drag and drop a file from your desktop, or use the file chooser. You must enter the import map name. Currently 0DX only supports XML, you cannot change that. The 'Hide Errors/Warnings' flag normally suppresses any problems with the source file. If you are having problems importing a file, you can uncheck this flag to see if there are any formatting problems with the incoming data. | ||||||||
Line: 172 to 172 | ||||||||
| ||||||||
Added: | ||||||||
> > |
|
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Processinghis page describes the various processing and updating options. _Overview:The 'Processing' options give us various ways of processing and importing data. Processing refers to extracting the identifiers and data from the source file. A mapping is not required for this step. Importing refers to running the import subroutine (created as part of defining the File/Field mapping) to update our Appx files. Each source file processed is held in temporary work files until you log off or delete them.UsageThe 'Upload and Process' option will upload the source file and extract the data and identifiers. You can upload several files, and their data will be kept separate. Processing does not actually import any data. The 'View/Modify Processed Files & Import' allows you to review all the files that have been uploaded and processed in the current session and refine the mappings, view the data, and ultimately run the import step to actually update the Appx files. The 'One Step - Upload/Import' combines the above functions, so you can upload, process and import the data all in one step.Upload and ProcessThis option allows you to upload a file to the server and process it. When you run 'Upload and Process', you will see the following display: The title will default to your user initials, plus the current date/time. You can change this if you wish. You can drag and drop an XML file, or use the file chooser. Currently 0DX only supports XML, you cannot change that. The 'Hide Errors/Warnings' flag normally suppresses any problems with the source file. If you are having problems importing a file, you can uncheck this flag to see if there are any formatting problems with the incoming data. Refer to the Tutorial or the Reference for a discussion of Ignorable / Replaceable segments. Once you click 'Execute' the tags and data will be extracted from the XML file and it will be ready for further review and/or importing in the next step.View/Modify Processed Files & ImportThis option will show you all the files that have been uploaded and processed in the current session. From here you can load an existing mapping, create a new mapping, modify the existing mapping, view the data, create the import subroutine and import the data. Files that you loaded via the 'Upload & Process' option will not have mapping assigned to them. You can use the 'Retrieve Map' button to load a previously defined mapping (must be in change mode to enable the button), or you create a mapping here by running 'Define File Map'Data ReviewThe Data Review options allow us to examine the extracted data.Raw DataThe 'Raw Data' option displays all the extracted identifiers and the associated data: The columns have the following meanings:
All Elements/Data ElementsThe 'All Elements' and 'Data Elements only' display the same information, the only difference is the 'Data Elements only' will only show you the elements that contain data: The columns have the following meanings:
Data ValuesYou can click the 'Data Values' button for any selected row, and you will get a display of all the actual data values for each occurence of the element: The 'Data Values' option shows us the same information as above, but not constrained to any element, ie, we can scroll thru all the extracted data.RefiningThe 'Refining' section allows us to fine tune the extraction of identifiers from the XML file.Ignorable SegmentsIn the 'Ignorable Segments' popup we can specify segments that are to be ignored (removed) when extracting the identifiers. For example, if 'ProspectData' was the top level identifier and is prefixed on all identifiers, we can remove it by entering 'ProspectData' as a segment to be ignored.Replaceable Segments'Replaceable Segments' are used for a very particular situation. Consider the following XML fragment:<j2:feature name="SourceName"> <j2:value>136</j2:value> </j2:feature> <j2:feature name="FileSystemProperties"> <j2:features> <j2:feature name="Path"> <j2:value>/usr/local/appx/archive/110928/136</j2:value> </j2:feature> <j2:feature name="LastModified"> <j2:value>2011-09-28T20:19:52-04:00</j2:value> </j2:feature> </j2:features>
Notice that the Segments all have the same name (j2:feature), and the identifier is really encoded in the attribute (name="..."). In this case, we can use the Replaceable Segments to move the attribute to the segment, which will allow us to map the segment to an Appx field:
Now our segment names will become "SourceName", "FileSystemProperties", "Path", "LastModified" instead of "j2:feature"
Regenerate ElementsWhenever you change the Ignorable or Replaceable segments, you must run 'Regenerate Elements' to reprocess the XML file using your new rules.MappingThis is where we can enter or modify the mapping rules. A 'File Map' indicates when a new record should be written to the Appx file, and a 'Field Map' indicates how the incoming data should be moved to an Appx field.Define File MapWhen you run 'Define File Map' you will see the following display: If you provided a map when you loaded the source file, then any existing File Mappings will be shown. The columns have the following meaning:
Define Field MapWhen you run 'Define Field Map' you will see the following display: This is where we define how each Appx field should be populated. If you ran the 'Populate Field Map' option in the previous step, then this display will be populated with all the fields in the selected file(s). If you did not do that, you have to manually add each field we are importing. For each field choose an appropriate 'Source Type'. if you leave the 'Source Type' blank they will be assigned the default values as per the Data Dictionary. The valid source types are:
Store MapThis option allows you to save the current mapping. If you enter the name of an existing mapping, it will be overwritten with the new mapping.Retrieve MapThis option allows you to load an existing mapping. After loading it, you can refine it using the 'Define File Map' and 'Define Field Map' options, then save it under a new name or replace the original, using the 'Store Map' option.ProcessingCreate Import SubrThis option will create a subroutine that does the work of importing the XML data into our Appx files: Fill in any Application and Process Name you want. When you click 'Proceed', the subroutine will be written and compiled. If any errors occur during the compile, you can view the subroutine in Application Design. You can also further customize the subroutine, however, you will lose those changes if you 'Create Import Subr' again.Import DataTo import the data into our Appx files, click the 'Import Data' button. This will run the subroutine that was created from our mapping, transferring the data from the internal 0DX files to the files/fields specified by our mapping.One Step - Upload/ImportThis option will upload the data and run the import subroutine, all in one step. When you choose this option, you should see the following display: The title will default to your user initials, plus the current date/time. You can change this if you wish. You can drag and drop a file from your desktop, or use the file chooser. You must enter the import map name. Currently 0DX only supports XML, you cannot change that. The 'Hide Errors/Warnings' flag normally suppresses any problems with the source file. If you are having problems importing a file, you can uncheck this flag to see if there are any formatting problems with the incoming data. Once you click 'Execute' the tags and data will be extracted from the source file and the import subroutine specified in the mapping will be run to import the data. When this is complete you will be returned to the menu.Comments:Read what other users have said about this page or add your own comments.-- JeanNeron - 2013-10-02
|