"}],"short_description":"In attribute rules we protect against stack overflow when we believe an infinite loop is detected. This blog goes through ways to avoid","flexible_content":[{"acf_fc_layout":"content","content":"Consider this table, we have two fields: group_name<\/em> and common_name<\/em>. The common_name<\/em> must match for all rows within the same group.<\/p>\n We would like to create an attribute rule that ensures if the common_name<\/em> is updated for a row, all rows within the same group receive the same name. This rule is straightforward; however, due to the attribute rules’ nature, updating the common_name will trigger the rule again. This repeated triggering can lead to attempting to update the same rows repeatedly, causing a cycle and potentially exhausting the Arcade engine execution instances. Resulting in the infamous error:<\/p>\n<\/div>\n<\/div>\n<\/div>\n “The evaluation of attribute rules is cyclic or exceeds maximum cascading level”<\/strong><\/em><\/p><\/blockquote>\n <\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2907132,"id":2907132,"title":"blog1","filename":"blog1.png","filesize":4411,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/prevent-infinite-loops-in-attribute-rules\/blog1-16","alt":"","author":"7511","description":"","caption":"","name":"blog1-16","status":"inherit","uploaded_to":2906922,"date":"2025-07-24 20:26:41","modified":"2025-07-24 20:26:41","menu_order":0,"mime_type":"image\/png","type":"image","subtype":"png","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":281,"height":222,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","medium-width":281,"medium-height":222,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","medium_large-width":281,"medium_large-height":222,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","large-width":281,"large-height":222,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","1536x1536-width":281,"1536x1536-height":222,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","2048x2048-width":281,"2048x2048-height":222,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","card_image-width":281,"card_image-height":222,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/07\/blog1.png","wide_image-width":281,"wide_image-height":222}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":" Let us author the rule anyway to prove this.<\/p>\n <\/p>\n"},{"acf_fc_layout":"sidebar","content":" An Attribute rule script that updates the same table, but fails with large rows.<\/p>\n This rule works for groups of rows with a few rows but fails when there is a large number of rows to be updated.<\/p>\n<\/div>\n<\/div>\n<\/div>\n To work around this issue, we need to differentiate between edits made by the user and edits made by the attribute rules. To achieve this, we can either add a new field or utilize an existing field in the table to indicate that the rule performed the update. During attribute rule execution we will set a specific value in this field (e.g. 1) to indicate the edit has been triggered from an attribute rule.<\/p>\n Subsequently, we will incorporate logic to revert the field value back to its original state, ensuring no impact on the data or schema.<\/p>\n I will introduce a new field called “t” and populate it with random values. It is important to note that these values will remain unchanged; they will temporarily alter during editing and then be reset back to their original values.<\/p>\n<\/div>\n<\/div>\n<\/div>\n An Attribute rule script that updates the same table, works with any number of rows.<\/p>\n And when we attempt to edit, you can see that the values update correctly without any errors, and the field we used to indicate attribute rule edits remains unchanged.<\/p>\n<\/div>\n<\/div>\n<\/div>\n <\/p>\n\r\n\/\/if the common_name hasn't change quit.<\/span>\r\nif<\/span> ($feature<\/span>.common_name == $originalfeature<\/span>.common_name) return<\/span>;\r\n\/\/grab the variables <\/span>\r\nvar<\/span> g = $feature<\/span>.group_name\r\nvar<\/span> gid = $feature<\/span>.GlobalID\r\nvar<\/span> n = $feature<\/span>.common_name\r\n\/\/look up all common_names same group and update them, we want to avoid updating the same feature and features with same name. <\/span>\r\nvar<\/span> fs = Filter<\/span>($feature<\/span>set, \"group_name = @g and globalid <> @gid and (common_name <> @n or common_name is null)\"<\/span>) \r\nvar<\/span> updates = []\r\nfor<\/span> (var<\/span> f in<\/span> fs) \r\n push<\/span> (updates, {\"globalId\"<\/span>: f.globalid, \"attributes\"<\/span>: {\"common_name\"<\/span>: n }})\r\n\r\nreturn<\/span> {\r\n \"edit\"<\/span>: [{\"className\"<\/span>: \"main.mytable\"<\/span>, \"updates\"<\/span>: updates}]\r\n}\r\n\r\n<\/code><\/pre>\n","image_reference":false,"layout":"standard","image_reference_figure":"","snippet":"","spotlight_name":"","section_title":"","position":"Center","spotlight_image":false},{"acf_fc_layout":"content","content":"\r\n\r\n\/\/if the common_name hasn't change quit.<\/span>\r\nif<\/span> ($feature<\/span>.common_name == $originalfeature<\/span>.common_name) return<\/span>;\r\n\r\n\/\/if this field has this value set, it means attribute rules has set it. We can use it to stop execution so we don't do further updates.<\/span>\r\n\/\/We want to reset the original value of the field. <\/span>\r\n\/\/This field can be any existing field or a new field.<\/span>\r\nif<\/span> ($feature<\/span>.t == 1<\/span> && $originalFeature<\/span>.t != 1<\/span> ) return<\/span> {\"result\"<\/span>: {\"attributes\"<\/span>: {\"t\"<\/span>: $originalFeature<\/span>.t}}}\r\n\r\n\r\n\/\/grab the variables <\/span>\r\nvar<\/span> g = $feature<\/span>.group_name\r\nvar<\/span> gid = $feature<\/span>.GlobalID\r\nvar<\/span> n = $feature<\/span>.common_name\r\n\/\/look up all common_names same group and update them, we want to avoid updating the same feature and features with same name. <\/span>\r\nvar<\/span> fs = Filter<\/span>($feature<\/span>set, \"group_name = @g and globalid <> @gid and (common_name <> @n or common_name is null)\"<\/span>) \r\nvar<\/span> updates = []\r\nfor<\/span> (var<\/span> f in<\/span> fs) \r\n push<\/span> (updates, {\"globalId\"<\/span>: f.globalid, \"attributes\"<\/span>: {\"common_name\"<\/span>: n , \"t\"<\/span>: 1<\/span>}}) \/\/set the field to 1 indicating attribute rules did the update. <\/span>\r\n\r\nreturn<\/span> {\r\n \"edit\"<\/span>: [{\"className\"<\/span>: \"main.mytable\"<\/span>, \"updates\"<\/span>: updates}]\r\n}\r\n\r\n\r\n\r\n<\/code><\/pre>\n","image_reference":false,"layout":"standard","image_reference_figure":"","snippet":"","spotlight_name":"","section_title":"","position":"Center","spotlight_image":false},{"acf_fc_layout":"content","content":"