<?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 Re: What is the best way to do a mass field calculate on branch versioned data? in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/what-is-the-best-way-to-do-a-mass-field-calculate/m-p/1672658#M45804</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/199986"&gt;@MDB_GIS&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Here are a couple of things I would suggest&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Run the calculation via the feature service, not the database.&lt;/LI&gt;&lt;LI&gt;Try to close the attribute table and disable layer drawing during this operation. Leaving these options running contribute can to the performance issue&lt;/LI&gt;&lt;LI&gt;Check your internet connection for any network latency. (VPN etc.)&lt;/LI&gt;&lt;LI&gt;If the service has validation rules and attribute rules each update triggers extra checks. You can temporarily disable the rules (if allowed) for bulk updates&lt;/LI&gt;&lt;LI&gt;You can also consider running the operation in chunks (e.g. 5000 at a time) or using python.&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Fri, 12 Dec 2025 15:42:53 GMT</pubDate>
    <dc:creator>SeyiO</dc:creator>
    <dc:date>2025-12-12T15:42:53Z</dc:date>
    <item>
      <title>What is the best way to do a mass field calculate on branch versioned data?</title>
      <link>https://community.esri.com/t5/data-management-questions/what-is-the-best-way-to-do-a-mass-field-calculate/m-p/1670848#M45803</link>
      <description>&lt;P&gt;I added a new field to a dataset and needed to field calculate about 20k features. I started the calculation about 30 minutes ago and it is still going. Any way to speed this up?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 14:04:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/what-is-the-best-way-to-do-a-mass-field-calculate/m-p/1670848#M45803</guid>
      <dc:creator>MDB_GIS</dc:creator>
      <dc:date>2025-12-05T14:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: What is the best way to do a mass field calculate on branch versioned data?</title>
      <link>https://community.esri.com/t5/data-management-questions/what-is-the-best-way-to-do-a-mass-field-calculate/m-p/1672658#M45804</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/199986"&gt;@MDB_GIS&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Here are a couple of things I would suggest&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Run the calculation via the feature service, not the database.&lt;/LI&gt;&lt;LI&gt;Try to close the attribute table and disable layer drawing during this operation. Leaving these options running contribute can to the performance issue&lt;/LI&gt;&lt;LI&gt;Check your internet connection for any network latency. (VPN etc.)&lt;/LI&gt;&lt;LI&gt;If the service has validation rules and attribute rules each update triggers extra checks. You can temporarily disable the rules (if allowed) for bulk updates&lt;/LI&gt;&lt;LI&gt;You can also consider running the operation in chunks (e.g. 5000 at a time) or using python.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Fri, 12 Dec 2025 15:42:53 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/what-is-the-best-way-to-do-a-mass-field-calculate/m-p/1672658#M45804</guid>
      <dc:creator>SeyiO</dc:creator>
      <dc:date>2025-12-12T15:42:53Z</dc:date>
    </item>
  </channel>
</rss>

