Latest Contributions by AmirBar-Maor

When the data is copied from a file to an enterprise geodatabase, the table names used in the expressions should be swizzled to the new names. If the rules use table names that are not available in the source and target, I would disable those rules. If that approach fails, you will quickly find out. BTW - if you want to create an empty schema quickly, instead of using delete rows, you can export an XML workspace (schema only), delete the data, and then import the XML Workspace to create an empty schema. ... View more

If you are using an enterprise deployment (feature services) and would like to see the name of the record in the popup, you will need to update the name of the relationship class with the name of the relationship between the 'layers'. You can find that name in the layer properties 'Relates' tab:   Once you have updated the pop expression with the relationship name you should be good:         ... View more

@RobertChaney  If I understand correctly, you want to hide the trailing zeros if the distance ends with '.00' . Is that also true for Radius and ArcLength? The label expression we ship with the software has many options you can tweak. This could be another option. If you think many other organizations will want that please submit an idea for it. Thanks, Amir ... View more

@BobNoyes  In general, we recommend performing large data manipulations on a file geodatabase. Why? Performing such manipulations in a named version increases the feature table size and might not perform as fast. The reason you cannot use the Truncate tool is because the feature classes participate in a topology. If you want to run ist faster start by running the geoprocessing tool Disable Parcel Topology and once you are done with the data manipulation, run Enable Parcel Topology. You will notice that every command runs faster when the topology is turned off as there are no need to update dirty areas. The price to pay for that is having to validate the entire data extent again. It will create a dirty areas for the entire data extent once you enable the toplogy again. Personally, I would: Copy the data to a file geodatabase and save a copy as backup Run Disable Parcel Topology Run Truncate table Append the updated data Run Enable Parcel Topology Perform Quality Assurance Make sure there are no open versions with pending edits  Delete the feature dataset containing the old data on SQL Server  Copy and paste the feature dataset with the updated data to the enterprise geodatabase (SQL Server) Enable versioning  Open the publication map Overwrite the published services Test  Such an operation should be carried out in the test environment first.   I hope this helps. ... View more

@DianeBaker  We understand why this can be frustrating and it is concerning that other mappers have encountered it. Unfortunatly I was not able to reproduce the issue 😞 You write that this happens 'on occasions' - can you provide any hints?  Always with curves on exit direction Does this happen after the traverse closes? Does this happen with traverse that have multiple curves? just one curve? Do you use ArcGIS Enterprise? Or a file geodatabase? If you enter an asterisk ('*') in the direction to force tangency again, does the cell become editable again? Or is the cell completly lockd out? Any other hints are greatly appreciated. If you can reproduce the issue, please contact technical support and DM us with the case number. ... View more

Thanks for the clarification  @JesseCloutier  The idea is 'open' for voting again @CathyAppleton  ... View more

@CathyAppleton  I don't know why kudos is disabled (also for me). The status of the idea should not disable it. @JesseCloutier - FYI ... View more

@MizukiKayano2  Please change the title of the idea to indicate that those tools should create points when splitting parcel fabric lines. My answer related to using those tools on parcel polygons. As for using the group template in the traverse tool - this is still an open idea and has not been implemented yet.  So, there's no need to rush and implement group templates for the Traverse tool. ... View more

@MizukiKayano2  The divide tool does create points. The Split tool does not create points for 'inner points" - should it? As for the traverse creating points - isn't this the same as this idea for the ability to use group template  in traverse? https://community.esri.com/t5/arcgis-parcel-fabric-ideas/traverse-tool-should-populate-cogo-for-multiple/idi-p/1561394   ... View more

@DianeBaker  As a workaround, you can always take data offline and then sync to the branch version. But before that make sure your system is configured properly (map, server, DBMS...). We have a meetup scheduled to discuss it soon.   ... View more

@MizukiKayano2  We are already working on it. ... View more

@DucksInaRiver  The workflow to create a traverse that includes calls to natural boundaries (bounds) as well as 'metes' is supported and well documented. The general outline of the workflow would be: Create an active record - all the created features will be associated with the legal record they came from such as a deed or a plat. Assuming the dimensions are in 'ground', set your Ground To Grid correction Enter the boundary lines of the parcel, you can alternate between entering COGO dimensions and digitizing or tracing natural features. In that case you should not have any misclose information and hence no need for any misclose adjustment, as you have stated. Create a Parcel Seed and Build to create a parcel Attribute your parcel At any point you can press the toggle "Show Only Active Record" to only see the feature you are entering.   I hope this help There are many videos online and on the parcel fabric community videos that show that. ... View more