<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Scale that is too large error</title><link>https://communities.bentley.com/products/geotechnical1/w/openground-wiki/66857/scale-that-is-too-large-error</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Scale that is too large error</title><link>https://communities.bentley.com/products/geotechnical1/w/openground-wiki/66857/scale-that-is-too-large-error</link><pubDate>Thu, 01 Jun 2023 22:35:06 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:ef7d0907-2459-442a-a475-d774520ec267</guid><dc:creator>Jesse Greenwald</dc:creator><comments>https://communities.bentley.com/products/geotechnical1/w/openground-wiki/66857/scale-that-is-too-large-error#comments</comments><description>Current Revision posted to OpenGround Wiki by Jesse Greenwald on 6/1/2023 10:35:06 PM&lt;br /&gt;
&lt;p&gt;If you get an error message about a &amp;ldquo;scale that is too large&amp;rdquo;, it indicates you are trying to import a value that has too many decimal places for the destination OpenGround header.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685659093470v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;You can fix this in the mapping file like below. Note the commented-out &amp;ldquo;Copy&amp;rdquo; mapping has been replaced by an &amp;ldquo;Evaluate&amp;rdquo; mapping. The Evaluate mapping uses the fixed() function to round the value to 3 decimal places. It&amp;rsquo;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685658804369v6.png" /&gt;&lt;/p&gt;
&lt;p&gt;You can check how many decimal places the destination header is configured to store&amp;nbsp;by going to &lt;em&gt;System&amp;gt;Configuration Packs&amp;gt;Manage Model&lt;/em&gt; and navigating to the header.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685658853309v7.png" /&gt;&lt;/p&gt;
&lt;p&gt;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 you may need to clean these values in the source data set.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>Scale that is too large error</title><link>https://communities.bentley.com/products/geotechnical1/w/openground-wiki/66857/scale-that-is-too-large-error/revision/2</link><pubDate>Thu, 01 Jun 2023 22:34:30 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:ef7d0907-2459-442a-a475-d774520ec267</guid><dc:creator>Jesse Greenwald</dc:creator><comments>https://communities.bentley.com/products/geotechnical1/w/openground-wiki/66857/scale-that-is-too-large-error#comments</comments><description>Revision 2 posted to OpenGround Wiki by Jesse Greenwald on 6/1/2023 10:34:30 PM&lt;br /&gt;
&lt;p&gt;If you get an error message about a &amp;ldquo;scale that is too large&amp;rdquo;, it indicates you are trying to import a value that has too many decimal places for the destination OpenGround header.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;You can fix this in the mapping file like below. Note the commented-out &amp;ldquo;Copy&amp;rdquo; mapping has been replaced by an &amp;ldquo;Evaluate&amp;rdquo; mapping. The Evaluate mapping uses the fixed() function to round the value to 3 decimal places. It&amp;rsquo;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685658804369v6.png" /&gt;&lt;/p&gt;
&lt;p&gt;You can check how many decimal places the destination header is configured to store&amp;nbsp;by going to &lt;em&gt;System&amp;gt;Configuration Packs&amp;gt;Manage Model&lt;/em&gt; and navigating to the header.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685658853309v7.png" /&gt;&lt;/p&gt;
&lt;p&gt;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 you may need to clean these values in the source data set.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item><item><title>Scale that is too large error</title><link>https://communities.bentley.com/products/geotechnical1/w/openground-wiki/66857/scale-that-is-too-large-error/revision/1</link><pubDate>Thu, 01 Jun 2023 22:31:29 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:ef7d0907-2459-442a-a475-d774520ec267</guid><dc:creator>Jesse Greenwald</dc:creator><comments>https://communities.bentley.com/products/geotechnical1/w/openground-wiki/66857/scale-that-is-too-large-error#comments</comments><description>Revision 1 posted to OpenGround Wiki by Jesse Greenwald on 6/1/2023 10:31:29 PM&lt;br /&gt;
&lt;p&gt;If you get an error message about a &amp;ldquo;scale that is too large&amp;rdquo;, it indicates you are trying to import a value that has too many decimal places for the destination OpenGround header.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/ErrorMessage.png" data-uw-rm-ima="un" /&gt;&lt;img style="max-height:240px;max-width:320px;" src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685658772705v5.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;You can fix this in the mapping file like below. Note the commented-out &amp;ldquo;Copy&amp;rdquo; mapping has been replaced by an &amp;ldquo;Evaluate&amp;rdquo; mapping. The Evaluate mapping uses the fixed() function to round the value to 3 decimal places. It&amp;rsquo;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.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685658804369v6.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;You can check how many decimal places the destination header is configured to store&amp;nbsp;by going to &lt;em&gt;System&amp;gt;Configuration Packs&amp;gt;Manage Model&lt;/em&gt; and navigating to the destination&amp;nbsp;header.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img style="max-height:240px;max-width:320px;" src="/resized-image/__size/640x480/__key/communityserver-wikis-components-files/00-00-00-06-06/pastedimage1685658853309v7.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;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 you may need to clean these values in the source data set.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;
</description></item></channel></rss>