Hydrants Map<\/strong> is active, containing a feature class of fire hydrant points with labeling enabled.<\/span><\/li>\n<\/ol>\n"},{"acf_fc_layout":"image","image":{"ID":2937629,"id":2937629,"title":"GenerateID_FireHydrantStartingMap","filename":"GenerateID_FireHydrantStartingMap-e1756331790789.jpg","filesize":33600,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-e1756331790789.jpg","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-id\/generateid_firehydrantstartingmap","alt":"","author":"365172","description":"","caption":"","name":"generateid_firehydrantstartingmap","status":"inherit","uploaded_to":2643142,"date":"2025-08-27 19:17:35","modified":"2025-08-27 19:17:35","menu_order":0,"mime_type":"image\/jpeg","type":"image","subtype":"jpeg","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":800,"height":512,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-213x200.jpg","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-e1756331790789.jpg","medium-width":408,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-e1756331790789.jpg","medium_large-width":768,"medium_large-height":492,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-e1756331790789.jpg","large-width":800,"large-height":512,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-e1756331790789.jpg","1536x1536-width":800,"1536x1536-height":512,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-e1756331790789.jpg","2048x2048-width":800,"2048x2048-height":512,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-727x465.jpg","card_image-width":727,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_FireHydrantStartingMap-e1756331790789.jpg","wide_image-width":800,"wide_image-height":512}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"First, right-click on the Fire Hydrants layer in the Contents pane. From the context menu, click on Data Design > Attribute Rules<\/strong>. The Attribute Rules Data Design view will open.<\/p>\nIn the ribbon, click on the bottom half of the Calculation Rule<\/strong> button. From the context menu, select Templates<\/strong> > Generate ID<\/strong>.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2642792,"id":2642792,"title":"GeneratIDContextMenuOption","filename":"GeneratIDContextMenuOption.png","filesize":45790,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-id\/generatidcontextmenuoption","alt":"","author":"365172","description":"","caption":"","name":"generatidcontextmenuoption","status":"inherit","uploaded_to":2643142,"date":"2025-01-01 02:05:06","modified":"2025-02-11 18:14:05","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":449,"height":257,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","medium-width":449,"medium-height":257,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","medium_large-width":449,"medium_large-height":257,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","large-width":449,"large-height":257,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","1536x1536-width":449,"1536x1536-height":257,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","2048x2048-width":449,"2048x2048-height":257,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","card_image-width":449,"card_image-height":257,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2024\/12\/GeneratIDContextMenuOption.png","wide_image-width":449,"wide_image-height":257}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"The Generate ID Template Attribute Rule GP tool dialog opens.<\/p>\n
Tool Overview<\/strong><\/h3>\n"},{"acf_fc_layout":"image","image":{"ID":2643072,"id":2643072,"title":"GenerateIDTool","filename":"GenerateIDTool.png","filesize":65203,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool.png","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-id\/generateidtool","alt":"","author":"365172","description":"","caption":"","name":"generateidtool","status":"inherit","uploaded_to":2643142,"date":"2025-01-02 20:06:13","modified":"2025-02-11 18:14:05","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":499,"height":1019,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool-213x200.png","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool.png","medium-width":128,"medium-height":261,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool.png","medium_large-width":499,"medium_large-height":1019,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool.png","large-width":499,"large-height":1019,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool.png","1536x1536-width":499,"1536x1536-height":1019,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool.png","2048x2048-width":499,"2048x2048-height":1019,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool-228x465.png","card_image-width":228,"card_image-height":465,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateIDTool.png","wide_image-width":499,"wide_image-height":1019}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"\n- The Expression <\/strong>parameter allows us to specify a subset of the features we\u2019d like to apply the Generate ID rule to using a SQL expression. Since we want all of the fire hydrant features to have formatted ID values we\u2019ll leave this parameter as is (this is default).<\/li>\n
- The Field<\/strong> parameter allows us to specify the field that we\u2019d like ID values to be written to. Let\u2019s choose HydrantID.<\/li>\n
- The Create Sequences <\/strong>parameter allows us to choose if we\u2019d like the Generate ID tool to create database sequences for the IDs we specify. Numeric values associated with IDs are stored in database sequences. The rule increments the sequence every time it is triggered. You might choose to disable this option if you already have existing database sequences you\u2019d like to use.<\/li>\n
- The Definition Type<\/strong> parameter allows us to define the format of the ID. There are three options:<\/li>\n<\/ol>\n
\n- \n
\n- Builder<\/strong> \u2013 The ID format will be constructed using the ID Builder. This is the option we will use (choose it from the dropdown).<\/li>\n
- Table<\/strong> – The ID format will be defined from a table using the ID Definition Table parameter.\n
\n- If you run the Generate ID Template Attribute Rule GP tool from the Geoprocessing Pane rather than from the Attribute Rules Data Design View, the output folder includes an ID Definition Table .csv file.<\/li>\n
- The ID Definition Table is a table of the sequence definition configurations. You can edit and reuse the IDs you configured when you select this parameter. Simply select the .csv file from your file system!<\/li>\n<\/ul>\n<\/li>\n
- Coded Values<\/strong> \u2013 An ID configuration entry and sequence will be generated for each combination of coded values or subtypes from selected fields.\n
\n- Pro Tip:<\/strong> <\/em>To configure the formatting of ID values generated using this definition I recommend using the ID Definition Table generated when running the tool via the Geoprocessing Pane. Run the tool with the Create Sequences option disabled. Edit the formatting of the IDs in the ID Definition Table using a text editor of your choice. Afterwards, rerun the tool with the Table Definition Type.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
\n- The ID Builder<\/strong> parameter allows us to configure IDs we\u2019d like the template attribute rule to generate. Let\u2019s format our fire hydrant IDs to match the specifications provided by the city (
hyd_#####<\/code>):<\/li>\n<\/ol>\n\n- \n
\n- \n
\n- Filter SQL<\/strong> allows us to specify an optional SQL expression to select which features we\u2019d like to apply the ID to based on attribute values. In our example, we want our hydrant ID value to be added to all<\/em> fire hydrants so we’ll leave the parameter as is.<\/li>\n
- Description<\/strong> is an optional description for the ID value that will be added to the rule settings for the attribute rule. Let\u2019s give our ID the following description: \u201cIDs for fire hydrants.\u201d<\/li>\n
- Sequence Name<\/strong> is the name of the database sequence to be created. Let\u2019s call our database sequence \u201cHydrantIDs\u201d<\/li>\n
- Starting Value<\/strong> is the starting number of the sequence. We already have manually added ID values for the first three hydrants, so let\u2019s start our sequence at \u201c4\u201d (the default value is 1).<\/li>\n
- Increment Value <\/strong>describes how the sequence value will be incremented. Let\u2019s set our increment value to 1 (this is default).<\/li>\n
- Prefix <\/strong>is an optional string or value that will be placed before the sequence value. Since we want our hydrant IDs in the format
hyd_#####<\/code> we should set our prefix to \u201chyd_\u201d.<\/li>\n- Suffix<\/strong> is an optional string or value that will be placed after the sequence value.<\/li>\n
- Padding<\/strong> is an optional positive number that represents the number of digits, where zeros will be used to fill the unused digits. To create hydrant IDs in the format
hyd_#####<\/code> where unused digits (the #s) are zeros, let\u2019s set the padding to 5.<\/li>\n- Separator<\/strong> is an optional string value used to join the prefix, sequence, and suffix. We don\u2019t need one to meet our formatting requirements for hydrant IDs.<\/li>\n
- The Add Another<\/strong> button at the bottom of the ID builder parameter, allows us to add multiple formatted IDs to our fire hydrant class. We might choose to do this, for example, to distinguish between various fire hydrant types (e.g.,
hydTypeA_#####<\/code>, hydType_#####<\/code>, etc.). For our example we’ll stick with just one ID.<\/li>\n- Each sequence can be previewed to help us validate the formatting we configured.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n
Review and Modify the Generated Rule<\/strong><\/h3>\nClick the OK<\/strong> button at the bottom of the tool to generate the template attribute rule. In the Attribute Rules Data Design View a new calculation rule appears called \u201cGenerateID\u201d. Rename the rule to \u201cSet Hydrant IDs\u201d.<\/p>\n"},{"acf_fc_layout":"image","image":{"ID":2643092,"id":2643092,"title":"GenerateID_ARRuleName","filename":"GenerateID_ARRuleName.jpg","filesize":77248,"url":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName.jpg","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/arcgis-pro\/data-management\/attribute-rules-generate-id\/generateid_arrulename","alt":"","author":"365172","description":"","caption":"","name":"generateid_arrulename","status":"inherit","uploaded_to":2643142,"date":"2025-01-02 20:31:00","modified":"2025-02-11 18:14:05","menu_order":0,"mime_type":"image\/jpeg","type":"image","subtype":"jpeg","icon":"https:\/\/www.esri.com\/arcgis-blog\/wp-includes\/images\/media\/default.png","width":1090,"height":266,"sizes":{"thumbnail":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName-213x200.jpg","thumbnail-width":213,"thumbnail-height":200,"medium":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName.jpg","medium-width":464,"medium-height":113,"medium_large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName.jpg","medium_large-width":768,"medium_large-height":187,"large":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName.jpg","large-width":1090,"large-height":266,"1536x1536":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName.jpg","1536x1536-width":1090,"1536x1536-height":266,"2048x2048":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName.jpg","2048x2048-width":1090,"2048x2048-height":266,"card_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName-826x202.jpg","card_image-width":826,"card_image-height":202,"wide_image":"https:\/\/www.esri.com\/arcgis-blog\/app\/uploads\/2025\/01\/GenerateID_ARRuleName.jpg","wide_image-width":1090,"wide_image-height":266}},"image_position":"center","orientation":"horizontal","hyperlink":""},{"acf_fc_layout":"content","content":"If you scroll down to the script expression in the Details Pane, you can see the Arcade script that was generated. I’ve included the script in the collapsible below (note: it’s quite long!)<\/p>\n\nClick here to view Generate ID Attribute Rule Arcade script expression from ArcGIS Pro 3.4<\/strong><\/summary>\n <\/p>\n
\/*\r\nwhere_clause (Text): A SQL Expression used to determine if the rule should continue(matches query), or return early\r\nseq_infos (Array): Array of sequence dictionaries\r\n where_clause (Text): A SQL expression applied to $feature to identify the sequence to use\r\n description (Text): A description of the sequence, this is for informational purposes and does not affect the execution\r\n prefix (Text): A string place before the sequence value, can be an empty string\r\n suffix (Text): A string placed after the sequence value, can be an empty string\r\n padding (Text): Pads the sequence number to a given length, can be an empty string. The format must such as '0000' for a 4 digit number such as 0005\r\n sequence_key (Text): The key used in the get_sequence_value function to identify the sequence\r\n separator (Text): A string used to join the prefix, sequence and suffice, can be an empty string\r\n intersect_values (Dictionary): The parameters used to look up a value in an intersecting layer to get an ID to determine a unique sequence for rows\r\n target_name (Text): The unqualified target class name\r\n where_clause (Text): An optional sql expression to limit the results from the target class\r\n spatial_operator (Text): The optional string for spatial filtering. Intersects\/Within.\r\n search_distance (Number): The optional buffer distance to apply to spatial_operator.\r\n search_units (Text): The optional units to apply to search_distance.\r\n\trow_id_field (Text): The field in the intersected class used to determine the sequence used\r\n\tid_values (Dictionary): A Dictionary where the keys are the values(as text) from the field in row_id_field in the intersected layers and the value is the key of the sequence to use\r\n*\/<\/span>\r\nvar<\/span> rule_settings = {\r\n 'where_clause'<\/span>: null<\/span>,\r\n 'seq_infos'<\/span>: [\r\n {\r\n 'where_clause'<\/span>: ''<\/span>,\r\n 'description'<\/span>: 'IDs for fire hydrants'<\/span>,\r\n 'prefix'<\/span>: 'hyd_'<\/span>,\r\n 'suffix'<\/span>: null<\/span>,\r\n 'padding'<\/span>: '00000'<\/span>,\r\n 'sequence_key'<\/span>: 'HydrantIDs'<\/span>,\r\n 'separator'<\/span>: null<\/span>,\r\n 'intersect_values'<\/span>: {\r\n 'target_name'<\/span>: null<\/span>,\r\n 'where_clause'<\/span>: null<\/span>,\r\n 'spatial_operator'<\/span>: 'Intersects'<\/span>,\r\n 'search_distance'<\/span>: null<\/span>,\r\n 'search_units'<\/span>: null<\/span>,\r\n 'order_by_clause'<\/span>: null<\/span>,\r\n 'row_id_field'<\/span>: null<\/span>,\r\n 'id_values'<\/span>: {\r\n },\r\n },\r\n },\r\n ],\r\n};\r\n\r\nfunction<\/span> get_sequence_value<\/span>(sequence_key) {\r\n return<\/span> Decode<\/span>(\r\n sequence_key,\r\n 'HydrantIDs'<\/span>, NextSequenceValue<\/span>('HydrantIDs'<\/span>),\r\n null<\/span>\r\n );\r\n}\r\n\r\nfunction<\/span> get_feature_set<\/span>(key) {\r\n return<\/span> Decode<\/span>(\r\n key,\r\n null<\/span>\r\n );\r\n}\r\n\r\nfunction<\/span> IsEmpty2<\/span>(value) {\r\n var<\/span> type = TypeOf<\/span>(value);\r\n if<\/span> (type == ''<\/span>) {\r\n return<\/span> true<\/span>; \/\/ null<\/span>\r\n } else<\/span> if<\/span> (type == 'Boolean'<\/span>) {\r\n return<\/span> !value;\r\n } else<\/span> if<\/span> (type == 'String'<\/span>) {\r\n return<\/span> IsEmpty<\/span>(value);\r\n } else<\/span> if<\/span> (\r\n (type == 'Array'<\/span>) ||\r\n (type == 'Dictionary'<\/span>) ||\r\n (type == 'FeatureSet'<\/span>)\r\n ) {\r\n for<\/span> (var<\/span> x in<\/span> value) {\r\n return<\/span> false<\/span>;\r\n }\r\n return<\/span> true<\/span>;\r\n } else<\/span> if<\/span> (type == 'Number'<\/span>) {\r\n return<\/span> IsNan<\/span>(value);\r\n } else<\/span> if<\/span> (type == 'Point'<\/span>) {\r\n return<\/span> IsNan<\/span>(value.x);\r\n } else<\/span> if<\/span> (type == 'Multipoint'<\/span>) {\r\n return<\/span> Count<\/span>(value.points) == 0<\/span>;\r\n } else<\/span> if<\/span> (type == 'Polyline'<\/span>) {\r\n return<\/span> Count<\/span>(value.paths) == 0<\/span>;\r\n } else<\/span> if<\/span> (type == 'Polygon'<\/span>) {\r\n return<\/span> Count<\/span>(value.rings) == 0<\/span>;\r\n } else<\/span> if<\/span> (type == 'Extent'<\/span>) {\r\n return<\/span> IsNan<\/span>(value.xmin);\r\n } else<\/span> if<\/span> (\r\n (type == 'Feature'<\/span>) ||\r\n (type == 'DateOnly'<\/span>) ||\r\n (type == 'Time'<\/span>) ||\r\n (type == 'Date'<\/span>) ||\r\n (type == 'FeatureSetCollection'<\/span>) ||\r\n (type == 'Portal'<\/span>) ||\r\n (type == 'Function'<\/span>)\r\n ) {\r\n return<\/span> false<\/span>\r\n }\r\n return<\/span> null<\/span>;\r\n}\r\n\r\nfunction<\/span> features_to_featureset<\/span>(features) {\r\n \/\/ Converts features array to feature set.<\/span>\r\n if<\/span> (TypeOf<\/span>(features) == 'FeatureSet'<\/span>) {\r\n return<\/span> features;\r\n }\r\n var<\/span> rows = [];\r\n var<\/span> feat, feat_dict;\r\n for<\/span> (var<\/span> i in<\/span> features) {\r\n feat = features[i];\r\n feat_dict = {\r\n '__oid__'<\/span>: i + 1<\/span>,
"}],"short_description":"Generate ID template attribute rules allow you to auto generate IDs for features while editing.","flexible_content":[{"acf_fc_layout":"content","content":"