Latest Contributions by AmirBar-Maor

@JoeGuziStarkCountyOH  I am using ArcGIS Pro 3.0 against a 10.9.1 Enterprise and the rule works for me. The only difference might be that I did not check the 'Batch' option since I want the name field to be calculated as the feature is created. You you mark the batch option it means you can defer when the rule is being executed and need to use the error inspector or the Evaluate Rules geoprocessing tool. The one 'gotcha' I've noticed is that after creating the sequence in the geodatbase I could not find it and had to use the geoprocessing history to make sure I have the correct sequence name.   I hope this helps Amir ... View more

@AEGIS  1. What type of information should be exported? Task group name + description,  task name + description, step name + instructions? Should the actions also be exported? 2. How is the exported information going to be used? 3. Format: based on the use above... would exporting the task to a CSV file be better? ... View more

@JoeGuziStarkCountyOH  It seems everybody already gave you the correct tips! My only tip: don't get desperate - we'll figure it out. Attribute Rules are stored in the geodatabase as part of the schema and are also executed in the geodatabase. This is why they use the table name and not the layer name. If you are certain you used the 'fully qualified' table name in your expression and it still refuses to work, please contact technical support. @HusseinNasser2 - FYI   return nextsequencevalue("XXX.XXX.ParcelNumberAssignmentSequence"); All  ... View more

@Paul_Christensen  Thanks for posting this question.  Would you be able to open a technical support case and provide your data so we can have a look into it? The polygons of administrative parcels do not participate in the topology and should not create a large dirty area. If you update a point that is shared with an administrative boundary, it should take a bit longer to update the administrative parcel polygon which usually has a large and complex (multipart) geometry. But it should never feel like the software is freezing, at a minimum it should show a progress dialog. If you do open a case please mention this post to expedite the process.   ... View more

@SamMontoia1  Thanks for posting your expression to display the retired record name as part of the post "See the Record Name as part of the parcel properties". Why we do not simply hide the GUID field? 1. When publishing data for editing the service itself becomes the schema. Hiding fields can be done when authoring maps (in the Pro client as well as web). 2. We made a conscious decision not to hide any table or any fields. We have learned from the ArcMap parcel fabric that hiding things later requires you to have special tools to 'unhide' them. It also makes them 'special' which translates to risk in terms of software quality.   3. GlobalIDs are the new ObjectIDs. None of them are meaningful or pretty but highly required. The open possibilities for new and exciting workflows across different clients, connected and disconnected as well as between organizations. 4. Hiding them, or any other field to that matter is very easy. ... View more

@DeanAnderson2  Since the parcel fabric controls simple feature classes this has nothing to do with the parcel fabric. When using web services, changing the schema is not done through the 'layer' but through the 'feature class'.  This means you have to connect to the database as the 'data owner' and drag the the 'feature class' to the geoprocessing tool. Another way to assign a default value is to use the data design view:   Just make sure to first stop the service, then modify the schema, then restart the service. In the fields data design view you can change any field property that is stored in the 'layer' like which field to highlight. Such changes do not require stopping and restarting the service. ... View more

With 3.0 a warning notification is displayed as soon as an edit is made in a location that is far from the active record geometry. That distance can be configured in the Active Record control. This also features in this video ... View more

With Pro 3.0 you can view the number of features that got appended for each parcel type as well as points and connection lines. @anna_garrett one less reason to get a headache while appending parcels 😉 ... View more

With Pro 3.0 you can resize the selected point area. The displayed points use incremental values from '1' instead of ObjectIDs. Those values are also displayed in the map which makes it easier to decide which point to preserve. ... View more

With Pro 3.0 the new geoprocessing tool 'Update COGO' mimics the Update COGO editing tool and can account for a combined scale factor (e.g. ground to grid correction) as well as a direction offset (e.g. basis of bearing). The correction can utilize Arcade expressions which opens the door to additional flexibility (e.g. - correct individual features based on their different elevation).   ... View more

In Pro 3.0 we are using 2 threads: 1 thread to support the fast entry of values in the traverse grid a second thread to commit the features.   The result: a super-fast responsive grid that accommodates any delay / slow performance in the main thread that commits the features to the geodatabase.  Why we did not use sketch? 1. Ability to save edits halfway through 2. Ability to label each course as they are being entered 3. Ability to change the symbology - for example: symbolize road frontage lines different than backlot lines. ... View more

This enhancement is included in Pro 3.0. The merge points selection tool can only select points. Other improvements point "label" with an incremental value starting from '1' and the ability to resize the selected points area in the pane. ... View more

The label expression for COGO lines has been improved in Pro 3.0. Improvements include the use of the new ConvertDirection Arcade method.   ... View more