<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Issue setting default values on a merged feature using an Inspector object. in ArcGIS Pro SDK Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/issue-setting-default-values-on-a-merged-feature/m-p/1613612#M12900</link>
    <description>&lt;P&gt;Hello. I have encountered an anomaly while using an Inspector object to set attribute values for merged polyline features. I am using the &lt;A href="https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic9527.html" target="_blank"&gt;Merge(Layer,IEnumerable&amp;lt;Int64&amp;gt;,Inspector)&lt;/A&gt; method as part&amp;nbsp;my edit operation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The feature table I'm working with has fields that are not null, domains applied, and default values set. When assigning attribute values for the merged feature using the Inspector, I have noticed that if I assign the default value for the field, the value will not be applied and I get a field validation error because the value must not be left null. If I don't assign a value at all for the field, the default value is still not applied. If I assign any other value listed in the domain that is not the default value, the attribute value is successfully applied.&lt;/P&gt;&lt;P&gt;In searching for similar forum posts, I found this. It follows a somewhat similar pattern, but when working with feature templates:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-questions/null-value-set-on-feature-template-with-default/td-p/1278259" target="_blank"&gt;https://community.esri.com/t5/arcgis-pro-questions/null-value-set-on-feature-template-with-default/td-p/1278259&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I am using version 3.4 of the SDK and do not recall having this issue with previous versions. Thanks for your time!&lt;/P&gt;</description>
    <pubDate>Mon, 12 May 2025 12:51:00 GMT</pubDate>
    <dc:creator>MRJ1</dc:creator>
    <dc:date>2025-05-12T12:51:00Z</dc:date>
    <item>
      <title>Issue setting default values on a merged feature using an Inspector object.</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/issue-setting-default-values-on-a-merged-feature/m-p/1613612#M12900</link>
      <description>&lt;P&gt;Hello. I have encountered an anomaly while using an Inspector object to set attribute values for merged polyline features. I am using the &lt;A href="https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic9527.html" target="_blank"&gt;Merge(Layer,IEnumerable&amp;lt;Int64&amp;gt;,Inspector)&lt;/A&gt; method as part&amp;nbsp;my edit operation.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The feature table I'm working with has fields that are not null, domains applied, and default values set. When assigning attribute values for the merged feature using the Inspector, I have noticed that if I assign the default value for the field, the value will not be applied and I get a field validation error because the value must not be left null. If I don't assign a value at all for the field, the default value is still not applied. If I assign any other value listed in the domain that is not the default value, the attribute value is successfully applied.&lt;/P&gt;&lt;P&gt;In searching for similar forum posts, I found this. It follows a somewhat similar pattern, but when working with feature templates:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.esri.com/t5/arcgis-pro-questions/null-value-set-on-feature-template-with-default/td-p/1278259" target="_blank"&gt;https://community.esri.com/t5/arcgis-pro-questions/null-value-set-on-feature-template-with-default/td-p/1278259&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I am using version 3.4 of the SDK and do not recall having this issue with previous versions. Thanks for your time!&lt;/P&gt;</description>
      <pubDate>Mon, 12 May 2025 12:51:00 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-questions/issue-setting-default-values-on-a-merged-feature/m-p/1613612#M12900</guid>
      <dc:creator>MRJ1</dc:creator>
      <dc:date>2025-05-12T12:51:00Z</dc:date>
    </item>
    <item>
      <title>Re: Issue setting default values on a merged feature using an Inspector object.</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/issue-setting-default-values-on-a-merged-feature/m-p/1615295#M12913</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;We found a similar issue within our Pro 3.5 development cycle where the EditOperation.Create(Layer, Inspector) created rows with null values instead of the default values with fields that have domains attached.&amp;nbsp; It sounds very much like the issue you are seeing.&amp;nbsp;&lt;/P&gt;&lt;P&gt;We fixed this issue within 3.5 which was released a few days ago.&amp;nbsp; &amp;nbsp;Are you able to upgrade to Pro 3.5 to see if your issue is resolved?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you are not able to upgrade, then would adding a Modify after the Merge (within the same EditOperation) be a workaround.&amp;nbsp; Make sure that you specify EditOperation.ExecuteMode = ExecuteModeType.Sequential prior to the Merge and Modify calls.&amp;nbsp; &amp;nbsp;I would suggest using the version of the Modify that takes a dictionary of attributes - &lt;A href="https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic9530.html" target="_blank"&gt;https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic9530.html&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Narelle&lt;/P&gt;</description>
      <pubDate>Fri, 16 May 2025 02:25:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-questions/issue-setting-default-values-on-a-merged-feature/m-p/1615295#M12913</guid>
      <dc:creator>NarelleChedzey</dc:creator>
      <dc:date>2025-05-16T02:25:50Z</dc:date>
    </item>
    <item>
      <title>Re: Issue setting default values on a merged feature using an Inspector object.</title>
      <link>https://community.esri.com/t5/arcgis-pro-sdk-questions/issue-setting-default-values-on-a-merged-feature/m-p/1616465#M12929</link>
      <description>&lt;P&gt;Thank you! I can confirm that this issue appears to be resolved now after upgrading to Pro 3.5.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 14:34:06 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-sdk-questions/issue-setting-default-values-on-a-merged-feature/m-p/1616465#M12929</guid>
      <dc:creator>MRJ1</dc:creator>
      <dc:date>2025-05-20T14:34:06Z</dc:date>
    </item>
  </channel>
</rss>

