https://community.esri.com/t5/data-management-ideas/etl-parameter-to-disable-defaults/idi-p/1316783 <P>When migrating data from a source feature class to a destination feature class (new or existing), I found an issue if the field in the destination feature class has a default value applied.&nbsp; If the field has a value of Null in the source feature class, then the value in the destination feature class will be the default value instead of the Null value.&nbsp; So the data migration has created a data change.</P><P><STRONG>Source Feature Class Example:</STRONG></P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GKing_0-1691576969165.png" style="width: 400px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/77638iF8D250D54EC4EBD5/image-size/medium?v=v2&amp;px=400" role="button" title="GKing_0-1691576969165.png" alt="GKing_0-1691576969165.png" /></span></P><P><STRONG>Destination Feature Class Example:</STRONG></P><P>(the FundingSource field has a default value applied of 'Council')</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GKing_1-1691576984766.png" style="width: 400px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/77639i70C4907E99FB7B3A/image-size/medium?v=v2&amp;px=400" role="button" title="GKing_1-1691576984766.png" alt="GKing_1-1691576984766.png" /></span></P><P>It would be great if the ETL tools in ArcGIS Pro had some functionality to temporarily disable default values (e.g. an environment setting).&nbsp; Then when these tools are run, the user has the ability to decide if they want the default values applied or for the Null values to remain.</P><P>The context for this idea came from a recent Utility Network data migration I ran.&nbsp; The migration had multiple feature classes migrating into each Utility Network feature class.&nbsp; Default values were applied as part of the Utility Network design (destination feature classes).&nbsp; The source data had some Null values (data gaps) that were migrating into fields with default values.&nbsp; The client wanted to keep these as Null values instead of having default values applied automatically.&nbsp; As shown above, with the default values in place this resulted in unwanted data changes that needed to be resolved.</P> Wed, 09 Aug 2023 10:33:03 GMT GKing 2023-08-09T10:33:03Z https://community.esri.com/t5/data-management-ideas/etl-parameter-to-disable-defaults/idi-p/1316783 <P>When migrating data from a source feature class to a destination feature class (new or existing), I found an issue if the field in the destination feature class has a default value applied.&nbsp; If the field has a value of Null in the source feature class, then the value in the destination feature class will be the default value instead of the Null value.&nbsp; So the data migration has created a data change.</P><P><STRONG>Source Feature Class Example:</STRONG></P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GKing_0-1691576969165.png" style="width: 400px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/77638iF8D250D54EC4EBD5/image-size/medium?v=v2&amp;px=400" role="button" title="GKing_0-1691576969165.png" alt="GKing_0-1691576969165.png" /></span></P><P><STRONG>Destination Feature Class Example:</STRONG></P><P>(the FundingSource field has a default value applied of 'Council')</P><P><span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="GKing_1-1691576984766.png" style="width: 400px;"><img src="https://community.esri.com/t5/image/serverpage/image-id/77639i70C4907E99FB7B3A/image-size/medium?v=v2&amp;px=400" role="button" title="GKing_1-1691576984766.png" alt="GKing_1-1691576984766.png" /></span></P><P>It would be great if the ETL tools in ArcGIS Pro had some functionality to temporarily disable default values (e.g. an environment setting).&nbsp; Then when these tools are run, the user has the ability to decide if they want the default values applied or for the Null values to remain.</P><P>The context for this idea came from a recent Utility Network data migration I ran.&nbsp; The migration had multiple feature classes migrating into each Utility Network feature class.&nbsp; Default values were applied as part of the Utility Network design (destination feature classes).&nbsp; The source data had some Null values (data gaps) that were migrating into fields with default values.&nbsp; The client wanted to keep these as Null values instead of having default values applied automatically.&nbsp; As shown above, with the default values in place this resulted in unwanted data changes that needed to be resolved.</P> Wed, 09 Aug 2023 10:33:03 GMT https://community.esri.com/t5/data-management-ideas/etl-parameter-to-disable-defaults/idi-p/1316783 GKing 2023-08-09T10:33:03Z https://community.esri.com/t5/data-management-ideas/etl-parameter-to-disable-defaults/idc-p/1316823#M2260 <P>Can you please name the specific tools?</P> Wed, 09 Aug 2023 12:45:44 GMT https://community.esri.com/t5/data-management-ideas/etl-parameter-to-disable-defaults/idc-p/1316823#M2260 RobertKrisher 2023-08-09T12:45:44Z https://community.esri.com/t5/data-management-ideas/etl-parameter-to-disable-defaults/idc-p/1318622#M2264 <P>Hi Robert,</P><P>The <STRONG>Append</STRONG> tool was the GP tool that caused this result in the UNM migration process.</P><P>I also did a few tests and noticed I also got the same results for <STRONG>Feature Class to Feature Class,</STRONG>&nbsp;<STRONG>Table to Table </STRONG>and the <STRONG>Merge</STRONG> tools as well.</P><P>These tests were run in ArcGIS Pro v2.9.0.</P> Tue, 15 Aug 2023 11:05:58 GMT https://community.esri.com/t5/data-management-ideas/etl-parameter-to-disable-defaults/idc-p/1318622#M2264 GKing 2023-08-15T11:05:58Z