Latest Contributions by DeanAnderson2

‎02-14-2022

Had not used that for domains before. That fixes the domain attribute. As to the CoGo Attributes I am not sure what is up. I just entered one line using traverse. (n44-00-00e 200 feet long) as below. I then use the divide tool and divided the line from start of line 100 feet and the results are: What I expect to have happen (and based on your response) would be two lines both with a length of 100. Instead my second line (while retaining the direction) has a NULL distance. Is this the correct behavior? I am not getting something.

‎02-14-2022

I am working with the Divide Line tool. My line feature class has several key attributes. When I divide the line (ie. 200 feet from beginning). The tool creates the two new lines correctly. The parent has the retired by record field assigned correctly making the parent line historic. So Far all is good. Unfortunately, I have a number of attributes (such as LineType) that are not replicated in the children while others (cogo attributes and a field called source) are. Is this the expected behavior ? (Also I am using 2.8.3). The documentation is pretty clear that it should keep the attributes. I am just not sure why my linetype is not kept (it has a domain) and why I lost my cogo distance on the remainder. Please let me know Thanks

‎12-17-2021

Thanks for letting me know! I was not able to find it anywhere.

‎12-16-2021

At this time, when a task is complete the contents (display, select set, edit set) are set as they were when the task was run. It would be great to have an option that would set the environment (display, select set, edit set) back to what existed before the task was started. 1. User environment exists 2. Task runs and contents sets the environment to be what is needed during the task 3. Based on an option the environment is reset to what is was before the task started (Step 1: User environment exists).

‎12-16-2021

Good thought, I tried that with a couple of test tasks for the cartographers. The problem is that they come at the "short cut" tasks from a number of different business processes so that there is not a specific contents set that will work. I thought if I created some tasks that represent "edit environments" that this would be more flexible and transparent. Also... I was thinking I would let users change & customize these environment setting tasks to fit their way of doing business. Whereas, I do not want them messing with "production tasks".

‎12-16-2021

That is too bad. This would be very helpful. As it is now I am creating a series of tasks that do nothing but set a particular edit environment (what's visible, selectable, and editable) which is not a great work around. Should I submit this need in the ideas section? ]

‎12-16-2021

We are starting to use tasks. We are using tasks as an aid to complete multi-step processes consistently and to provide "shortcuts" to get specific tasks done. Within tasks using contents to set was is visible, selectable, and editable is great! However, is there a way when the task is completed that what is visible, selectable, and editable will be returned to what they were before the task was started?

‎12-07-2021

At the suggestion of Amir, I am reposting this question here. In my parcel fabric design I have created additional feature classes that I want a field type to be "GUID" for a specific field (such as "created by record") and use these fields in my editing process. The fields function as all other fields do except when I go to use the "Set Default Attribute Tool". Unfortunately, the Set Default Attribute Tool appears to not allow this. Is there some reason why? The tools works as expected for all other field types. When using the "Assign Default to Field" interactively the field with a type of GUID does not appear (see below) and when I try to run the tool as a python script it errors. out. The work around I am using is to set the field type to be a Textfield but that is kind of annoying and its just not right.

‎12-04-2021

In my parcel fabric design I have created additional feature classes that I want a field type to be "GUID" for a specific field (such as "created by record") and use these fields in my editing process. The fields function as all other fields do except when I go to use the "Set Default Attribute Tool". Unfortunately, the Set Default Attribute Tool appears to not allow this. Is there some reason why? The tools works as expected for all other field types. When using the "Assign Default to Field" interactively the field with a type of GUID does not appear (see below) and when I try to run the tool as a python script it errors. out. The work around I am using is to set the field type to be a Textfield but that is kind of annoying and its just not right.

‎11-16-2021

Tried to use the attribute rules. Users will need to be able to assigned related feature with a plan but this does not happen All the time and unfortunately, with enterprise attribute rules can not be turned off an on (unless this recently changed). My current work around is to get the globalid from the current activerecord and use the arcpy.AssignDefaultToField_management tool to set the default value for each feature that is participating. Once it is turned on all features added after that time will have the global id updated. Once it is turned off this will not happen.

‎11-16-2021

I have figured out a simple work around. You can get the active record globalid for the record from one of the layers that participates in the fabric if you click the "Show Only Active". This sets up the definition query which you can get the ActiveRecordNumber from. In the following bit of code the Taxlot_Lines is a feature layer that is part of the fabric. RecordNumber is the final variable that contains the globalid of the active record. aprx = arcpy.mp.ArcGISProject("CURRENT") Map = aprx.activeMap mapTaxlotLineLyr = Map.listLayers("Taxlot_Lines")[0] TaxlotLineLayerWhereClause = mapTaxlotLineLyr.definitionQuery RecordNumber = TaxlotLineLayerWhereClause.split('{')[1] RecordNumber = RecordNumber.split('}')[0]

‎11-09-2021

That is it! Have not used CIM before so this is a great introduction to it. Thanks

‎11-08-2021

Parcel fabric has default definition queries Taxlot_lines - (RetiredByRecord Is NULL). I have successfully added additional definition queries to support other business needs and can manually change between them. Is there any way to change which definition query to use with Python. Also I create a new definition query with the layer property but would rather not delete and create them all the time. Especially when parcel fabric comes with some already.

‎11-01-2021

Have not been able to find this. Any idea what release this is planned for?

‎10-07-2021

Sorry for my absence. Took a short vacation and then was slammed with some non-gis deadlines. Very much appreciate the comments Amir and Frank. 1. The relationship classes and filters do work. But it requires me to set this all up and manage. (Yes I know I am lazy.) From a gis support persons perspective it would be great to have a tool/command that did this and then honored it through some basic operations as folllows: -- When an record is active these features would automatically be assigned to the active record (the same way a line that participates in the parceltype would be. -- When features are selected for the active record these features would be selected -- When Show only Active record is clicked you would see these feature as well. At this time all of these capabilities need to be managed within the task environment and with scripts. 2. Retire Records - Sorry about terminology - when a number of functions impact a record and the features associated with record are assigned "Retired By Record" I want this to also be done to the related feature classes. To Be Clear - I am referring to a point, line and annotation feature classes that are used for cartographic purposes to assist in replicating a record. The following diagram illustrates some of these features (highlighted in red). I our redesign to Pro/Fabric and review of business practices these features remain as annotation and lines (I hope this helps describe what I am talking about).

Online Status	Offline
Date Last Visited	‎05-13-2026 09:38 AM

My Ideas

Latest Contributions by DeanAnderson2

Re: It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

Re: ArcGIS Pro Tasks and Returning to Starting Point

Have an option to reset the task contents upon completion of a task to what they were before the task started.

Re: Can you reset task contents so selection and edits are returned to what was set before you ran the task

Re: Can you reset task contents so selection and edits are returned to what was set before you ran the task

Can you reset task contents so selection and edits are returned to what was set before you ran the task

Assign Default Field with DataType GUID

Assign Default Field with DataType GUID

Re: Add ability to associate cartographic feature classes to record types in the fabric.

Re: Get GlobalID of current record

Re: Programmatically select layer definition query

Programmatically select layer definition query

Re: Icons for custom geoprocessing tools - ArcGIS Pro

Re: Add ability to associate cartographic feature classes to record types in the fabric.

Re: adding metadata with ArcPy using export does n...

Re: Attribute rule not working with merge to updat...

Make the snapping settings per task – optional. So...

Re: Exporting a feature class with a related table...

Re: Exporting a feature class with a related table...

Web AppBuilder Custom Widgets