Latest Contributions by DeanAnderson2

‎06-10-2024

I am familiar with the 3.2 field changes. But... if I did EVERYTHING in ArcPro 3.3 (created my project and map, created all feature classes, imported all tables from excel) then why is this need to be checked ? Nothing I am doing was done in ArcPro 3.1 (or earlier). I am just curious.

‎06-10-2024

Wow - that fixed it. Thanks! Funny thing. This entire project creation, data loading, etc. was all done using ArcPro 3.3 start to finish. So why did I need to check this checkbox ? Anyway, I am not sure I care. I NEVER would have found this. Thanks again.

‎06-05-2024

I want to check if this issue is a "feature" or a "bug". I am exporting a feature class with attributes from a related table. I figured out a workaround so will also include that. I am using ArcPro 3.3. What I have: I have a point feature class which contains many internet service point locations. I also have a table with just internet copper services. Not all point locations have a copper service but some can have two-three (different providers). I use JOIN (only keeping those that match) using a field called "Location_Id". When I look at the attributes everything looks great. I see the attributes and values from both the feature class and related table as expected. The Issue: When I export the results to a new feature class "Data --> Export Features" the new feature class contains the field definitions of the join table but all the fields have "null" values. Work Around: My work around was to create a new empty feature class containing the field definitions for the feature class and joined table. By using the editor cut/paste I was able to obtain the results I wanted. I did not use Append as the cut/paste worked. Question: Is the export data behavior I found a feature or a bug? I have not been able to find any comments on this. I was able to replicate the issue and work around with different feature classes and related tables.

‎02-14-2024

It worked great - Thanks. I am not sure why mine did not but I do not care and will do a bit more research on why.

‎02-14-2024

Thanks! I will try this out.

‎02-12-2024

I am testing validation rules. We have imported a lot of data and I want to implement validation rules to assist users in reviewing attribute values that need to be in the attribute domain. I am using ArcPro 3.2+. (I know I can do this from with the Attributes tab but want to use attribute validation rules. ) I have a domain with ALL county values 1-36 for a field called County. In my feature class (Taxcode) I selected a polygon and assigned it a null value (putting it outside the domain). I have created a couple of different arcade scripts to do the validation but both return all features in error when using the error inspector. I have looked at available examples and can not find this specific example. I did find code that looks at pole heights and another that includes subtypes. I have not been successful at using these examples to create my own SIMPLE approach. Here are the two ways I have done it. Example 1: return (Includes(Domain($feature,'County').codedvalues,$feature.County)) Example 2: var CountyDomains = Domain($feature,'County') var ValidCodes = [] var ValidCodes = CountyDomains["codedValues"] return (Includes(ValidCodes,$feature.County)) Both are valid expressions. In the error inspector both identify all features in the feature class as being in error. Its got to be doing something simple. What am I doing wrong?

‎11-28-2023

As a follow up.. I was also able to create a problem with versions and records between two maps using the following steps ( involves no python scripts.) I am still using ArcPro Fabric 3.2 and Enterprise/Branched Version 11.1 1. Created A version in "Map" (PF_ANDERSD.DeanTextVersion11_28_1) 2. Created a new Record (DeanTestVersion11_28_1) in "Map" 3. Set active Record 4. Used the MERGE tool - Combined two taxlots (703+701-> 701) -- ALL works fine -- Taxlots were merged -- Record geometry was created 5. Opened Second Map "TaxlotMap" 6. Changed Version (PF_ANDERSD.DeanTextVersion11_28_1) --- Problems Found --- a. Taxlot Polygons are NOT Merged ----b. Can NOT select the merged polygon ----c. Can no "refresh" the version ----d. New Record does NOT exist in the version

‎11-28-2023

I am using ArcPro 3.2 to access 11.1 Enterprise with Branched Versioning. I have been having problems with creating a record in a version using procedures posted in(Part 2 - Branch Version with Parcel Fabric) as discussed in my previous post "Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version". I also have a second issue. In my project, I have two maps, one is for general editing and the other for creating a voucher. Unfortunately when I set both maps to default my second map "retains" the record created previously. I have tried to refresh the versions with both maps, opening and closing the project files etc. The following two pictures illustrate my problem. This seems to be independent of my previous problem and just deals with how two maps point at the "default" environment. My question is --- is anyone else having this issue ? Map 1: Set to default. Only ONE record appears in the map extent. Map 2: Set to default. TWO records appear in the map extent. The second record should NOT be in default.

‎11-20-2023

Thanks for getting back to me. I am able to iterate thru all the layers. In interating through the list the script I USED to be able to include "Records" (FC/Layer) in the layer list. It now errors out saying that you can no longer do this. Best error message I get is when I use the "Change Version" tool on the "Records" layer. This also errors out in 3.2 (not 3.1X) python scripts. The problem comes when I try to use the python script to use the updateConnectionProperties method on the fabric (TaxlotsPF). When I use this the record is not accessible and if I try to create new record in this new version (because the fabric appears to have been moved) I ONLY see a "blank" menu (no prompts) or anything. I have attached the text script I used. Hope it helps. Again... The script allows me to change the feature classes / layers associated with the fabric (LOTS,PLATS,TAXLOTS,etc) and that all works fine. Changing other (non-fabric) feature classes (to the version) also works fine. The only layer that does not work correctly is the Records layers that is directly associated with the fabric .

‎11-20-2023

As a follow up. When I use the ChangeVersion tool in the python script as follows, all of the feature classes that participate in the record change. Unfortunately, the "TaxlotsPF: Records" feature class does not and remains in the old version. Versionmap = thisProject.listMaps("Map")[0] # same map as before pfLayer = Versionmap.listLayers("TaxlotsPF")[0] # same fabric as before edit = arcpy.da.Editor(WorkSpace) # my workspace edit.startEditing(False, False) edit.startOperation() arcpy.management.ChangeVersion( in_features=pfLayer, version_type="BRANCH", version_name=new_version_fullname, date=None, include_participating="INCLUDE" ) edit.stopOperation() edit.stopEditing(True) The results are.... All feature classes Except Records are transferred to the new eversion (also no error message).

‎11-20-2023

I am using ArcPro 3.2 accessing 11.1 Enterprise (will be upgraded soon to 11.2). I am testing my 3.1x code for creating a version in 3.2. I based my code on the ESRI Post (Part 2 - Branch Version with Parcel Fabric). This code has been working Great in 2.9 thru 3.1x. In 3.2 I can no longer change the version of the "Records" Feature class directly. However, this appears to happen when I change the version of the ParcelFabric that the Records feature class is a member of. Unfortunately, when I do this I can no longer create a new record in the new version. My steps for this test. 1. Create a new version (works great - no problem) 2. Get properties of new version (works great no problem) 3. Change the version manually (problems - Dialogue box is blank but code runs fine and version changes but problems) Code is as follows for changing the version is as follows: Versionmap = thisProject.listMaps("Map")[0] # Map map in my project (thisProject) pfLayer = Versionmap.listLayers("TaxlotsPF")[0] #TaxlotPF is my parcel fabric arcpy.AddMessage("-lyr: " + str(pfLayer.name)) # Just a message updated_props = pfLayer.connectionProperties arcpy.AddMessage(updated_props) # message to check properties arcpy.AddMessage('-----------------------') updated_props["connection_info"]["version"] = new_version_fullname # Props of the new version updated_props["connection_info"]["versionguid"] = new_version_guid pfLayer.updateConnectionProperties(pfLayer.connectionProperties,updated_props,auto_update_joins_and_relates = True, validate=True) new_props = pfLayer.connectionProperties Please let me know if I am doing something wrong ? I have tried several variations of this tool and also tried to use the changeversion tool. None seem to work.

‎10-02-2023

This is so cool. Thanks!

‎09-25-2023

Thanks! Always good to have somebody cleanup my code. Much appreciated.

‎09-25-2023

Better code - Again Thanks ! // Get map number from mapindex polygon layer var fsMapIndex = FeatureSetByName($datastore,"MapIndex",["MapNumber","ORMapNum","County"]) var fsIntersectMap = Intersects(fsMapIndex,$feature) if (fsIntersectMap == null) return {"errorMessage": "No Map Index Feature Found"} var MapNumber = "None" var ORMAPNum = "None" var County = 99 var intersectarea = 0 for (var f in fsIntersectMap){ var newintersectarea = Area(Intersection($feature,f)) if (newintersectarea > intersectarea){ var MapNumber = f.MapNumber var ORMAPNum = f.ORMAPNum var County = f.County intersectarea = newintersectarea} } return { "result": { "attributes" :{ "MapNumber" : MapNumber, "ORMapNum" : ORMAPNum, "County" : County } } }

‎09-25-2023

Thanks - that makes sense. Built this off of old code and was just pretty focused on making the area check work.

Online Status	Offline
Date Last Visited	3 weeks ago

My Ideas

Latest Contributions by DeanAnderson2

Re: Exporting a feature class with a related table not saving attributes (feature or bug?)

Re: Exporting a feature class with a related table not saving attributes (feature or bug?)

Exporting a feature class with a related table not saving attributes (feature or bug?)

Re: Validation problem with checking domains compliance

Re: Validation problem with checking domains compliance

Validation problem with checking domains compliance

Re: Inconsistent Default Versions with ArcPro 32

Inconsistent Default Versions with ArcPro 32

Re: Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version

Re: Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version

Problems with Arcp3.2 Parcel Fabric Using ArcPy to Change the Version

Re: Provide methods to select and manipulate a parcel fabric record using Python or Model Builder.

Re: Arcade within() actually queries the feature it is within

Re: Arcade within() actually queries the feature it is within

Re: Arcade within() actually queries the feature it is within

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

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

Exporting a feature class with a related table not...

Problem using scripts to calculate fields in ArcPr...

Re: Validation problem with checking domains compl...

Web AppBuilder Custom Widgets