This articles was previously titled "Scale that is too large error". The error message wording has since changed. The article title has been updated to reflect that, but the potential solutions described below are still applicable.

If you get an error message about  “more decimal places than the destination header is configured to store ”, it indicates you are trying to import a value that has too many decimal places for the destination OpenGround header. (Note - the screenshot below still shows the old wording for this same error.)

You can fix this in the mapping file like below. Note the commented-out “Copy” mapping has been replaced by an “Evaluate” mapping. The Evaluate mapping uses the fixed() function to round the value to 3 decimal places. It’s also recommended to use an IsDefined() condition to make sure the source field has data for that record. This has been done below for both the DepthTop and DepthBase mappings.

 

You can check how many decimal places the destination header is configured to store by going to System>Configuration Packs>Manage Model and navigating to the header.

 

Note that in some circumstances, these changes may result in duplicate key errors if key fields for multiple records are rounded to the same value. If that is the case, there may be additional OpenGround key fields you can map to uniquely identify each record. Or alternatively, you can potentially increase the number of Decimal Places stored for the header in Manage Model instead of using an expression to round the value. If those approaches, don't work, you may need to clean these values in the source data set.