If the Mapping Type is… | Complete these fields… |
Delimited File or Data Dictionary Import | ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Remote Database | ![]() ![]() ![]() |
XML/XSD File | ![]() ![]() |
Note: | For conceptual objects, the rows from parent object are included only when they satisfy the child filter. Parent objects without any child objects are also excluded. |
Option | Description |
Operator | Specify the operator. You cannot combine AND and OR in the filter criteria. |
Entity | Select the object on which to apply the filter. OneData objects cannot contain a semi-colon (;) in the object name because semi-colons are the filter delimiter. If needed, the semi-colon can be specified in the object display name. |
Attribute | Select the column on which to apply the filter. This field also includes DECODE columns. Select the DECODE column, if you want to select from the description columns mapped to a reference column. |
Description Attribute | Select the description column. If a DECODE column is selected in the Attribute, this field is populated with the columns of the related object. Ensure that the Description Attribute selected in the filter is correctly mapped in the Mapping Attributes section. |
Filter Value | Select the operator condition and filter value. Equals and not equals are case insensitive comparisons. Lesser than and greater than apply to numeric values (without decimals) and dates. You can add multiple values separated by comma. Click the arrows to add each condition to the filter. To add multiple conditions, modify the filter definition and add each new condition to the filter. The filter definition cannot be edited. To remove the last filter criteria added, click Undo. |
The following restrictions apply to filters: ![]() ![]() ![]() ![]() ![]() The following is an example of the filter syntax: <Object_Name>.<Column_Name><Operator><Filter_Value> or <Object_Name>.<ForeignKey_Name>#<Desc_Attribute> <Operator><Filter_Value> |
Tip: | To clear filter conditions, click Undo until all filter criteria is cleared. If you change the object in the Object Mapping. click Refresh Filter to repopulate the entity list. |
Option | Description | ||
Processing Mode | Select how OneData processes the data in the import file for the selected object. ![]() ![]() ![]() ![]() ![]() ![]() | ||
External DQ Mode | Select Enable to perform the Cleansing and Matching processes while executing this interchange mapping. This loads the data from a source to a consolidation staging object. The mapping from Staging to Gold must be defined. Applicable only for consolidation objects. | ||
Data Compare Criteria | Applicable only for the update only or update existing entries processing modes. Perform Case sensitive or Case insensitive updates. Case sensitive updates reduce delays while importing. | ||
Execution Batch Size | Size of the execution batch that is forwarded to the exception queue when a partial commit is enabled. This overrides the size configured in the OneData property, onedata.interchangeexecution.batchsize. For more information about configuring onedata.properties file, see Administering webMethods OneData. By default, OneData processes the records in batches of 100 and performs the commit at the end of the import process. | ||
Enable Partial Commit | When selected, OneData commits data at the end of each batch, even if the import does not complete successfully. This means that the records that are inserted or updated at the connection level are committed to the database.
| ||
Enable Multiple Connection Usage | When selected, uses isolated connections within an execution batch and automatically enables partial commits at the batch level.
| ||
Exception Queue Automatic Retrigger | Applicable only if the OneData property Enable Partial Commit is true. Select to capture only faulty records in a batch to the Exception queue. Clear this option to capture all records in a batch to the Exception queue. | ||
Skip columns with zero-length value | Select to skip processing of columns with zero-length values. If selected for a conceptual object, all constituent objects must have at least one record in each level. A missing value in any level causes unexpected results. For example, in a Country-State-City conceptual object, select this option only if all the objects have at least one record in the source object, as in the following example: <!--Record 1--> <Country>Country_Name_1 <State>State_Name_1 <City>City_Name_1</City> </State> </Country | ||
Accept Date into Timestamp Column | Select to convert a date column to the OneData timestamp format when the date column is mapped to a timestamp column.
| ||
Ignore missing parent reference | Select to avoid exceptions when a parent reference is not provided in the input. | ||
Bypass temporal validation | Select to ignore temporal validation exceptions in temporal objects. | ||
Bypass regular expression and Rules Engine | Select to ignore regular expression and rules engine validations during an import. | ||
Bypass Workflow | Select to ignore workflow rules during an import. | ||
Bypass Data Audit | Select to skip adding entries into data audit trails for the data being imported. | ||
Start import at row | The starting row number at which to begin the import. Not applicable for remote database or XML file imports. | ||
Service Audit Log Level | Select the logging level for inbound data import service requests through REST, Interchange Mapping, and JMS: ![]() ![]() ![]() ![]() | ||
Source System | Enter a description about the source system of the payload. | ||
Enforce where clause on remote entity (Optional) | Build a where condition to restrict which data is imported. The Remote Database import job applies this condition to the source data to fetch the values. Then the filter, if specified, is applied to the resulting values. Applicable only for remote database imports. |
Note: | The source attributes are predefined. An additional row can be added to map a column even if it does not exist at source. |
Detail | Description |
Profile Name | The name of the interchange mapping profile. |
Profile Description | The description of the profile. |
Additional Row Count | Adds an additional column to the object during the import. For example, to add a column in the object that does not exist in the import file, you can use this field and specify a default value. Add the row while mapping the attributes and setting default value (explained in next step). |
Set | Click Set to define additional rows. |
Detail | Description |
Source Attribute | The name/number of column in the input file. |
Destination Entity | The OneData object into which to map the column. For example, for a conceptual object, multiple objects can be viewed and attributes mapped to the required object. |
Destination Attribute | Select the attribute into which to map the Source Attribute. |
Description Attribute | If the Destination Attribute is a DECODE of any attribute in the entity, all the attributes in that entity are populated in this field for this decoded value. While using DECODE, if the column maps to more than one record from the object the import results in error. |
Default Value | Specify a default value. This value is only used when the source and destination attributes are null. |
Constant Value | Specify a constant value. When the source attribute is null, the destination attribute is updated with the constant value, regardless of whether the destination attribute was null. |
Format | Specify the format for the attribute value. |
Python Transformation | If required, input the python script for deriving the required detail from the Source Attribute. |
Note: | If the destination object contains a sequence column, OneData notifies you that the value imported for this attribute will be overwritten by the sequence value generated after import. |