<< Click to Display Table of Contents >> Navigation:  EDP > Customizability > Ignore Unmapped Columns

In some situations a user may want to use Insert and Replace in EDP, but do not want to replace all non-null values with null values.

 

For example, suppose a lab EDD is received and uploaded to the database. After the data has been loaded, a very simple set of result data is exported to be reviewed by the validator. The validator may review the data and add qualifiers. In some cases, the validator may determine that a reported detect is actually a non-detect. In that case, the validator will need to replace the existing result value with a null value. When the validator has completed the data review, the data needs to be loaded back into EQuIS. First use Insert and Replace commit types to replace the existing result values with the validated null values. However, Insert and Replace will also overwrite all of the other fields that are not in the simple dataset reviewed by the validator.

 

To accommodate scenarios such as that described above, EDP has been modified so that a user can choose to only update fields that are mapped in the format during the commit. So if you have a simple "Validator" EDD format that only maps to a few fields in the DT_RESULT table, the commit process will only update those fields. Any of the other fields will not be updated when you commit. With this change in EDP, the Package tab will show only those fields that are going to be updated.

 

If unmapped columns are to be ignored by EDP, then add the msprop:IgnoreUnmappedColumns attribute to the EQuIS Format Definition (EFD) file as shown below:

 

 

After making the desired changes to the format file, it is required when using Professional EDP (with application-level security) or Enterprise EDP that the format either be encrypted by EarthSoft (i.e., *.xse) or be embedded as a resource in a strong-named .NET assembly (i.e., *.dll). See Securing EDD Formats for additional information.