nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Utility and Pipeline Data Model (UPDM) Arcade error: Field not found

JacobBlankenship1

I am having a issue with Arcade code not being able to find field in the featureclass(Pipeline Line), when trying to do calculate geometry on a field. I use to be able to do this fine as of week ago but know it wont work at all. I updated my ArcGIS pro to 2.9.2 and added some domains to the pressure sensor pipe since than. I for a fact that the field "material" is in the table and spelled correctly and matched the arcade expression in the attribute rules.

I attached a Blank GDB for reference to replicate the issue

Anyone have any ideas?

UPDM_UtilityNetwork_Site_Blank.gdb.zip

radimbachb_0-1720025359635.png

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

JacobBlankenship1

I attached a Blank GDB for reference to replicate the issue

Anyone have any ideas?

UPDM_UtilityNetwork_Site_Blank.gdb.zip

NathanEasley

Hi Jacob,

I'd suggest posting this to the Utility Network community as that's where most of the arcade and attribute rule topics have been answered. https://community.esri.com/t5/arcgis-utility-network/ct-p/arcgis-utility-network

JacobBlankenship1

Thank you, will do

MikeMillerGIS

There is an issue when you use a cursor on a class with attribute rules. You need to make sure all the fields in the AR are in the fields list for the cursor.

JacobBlankenship1

AR?

Shouldn't the "Calculate Geometry" include all the fields when running the cursor.

MikeMillerGIS

AR = Attribute Rule, sorry for the abbreviation

Looking at the script, it does not. Only fields it is updating. The core script would need to be modified.

JacobBlankenship1

Ok, I guess I am confused as to why it just stopped working this week and was fine last week. It seems more likely that the issues is something with Arcade expressions or the network.

Also have had this issue, (which was also working last week as well) The project map is set to a state plane.

MikeMillerGIS

I did find a bug for the issue if you want to follow https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDE0NTc2MA==

JacobBlankenship1

Thanks you,

Any ideas about symbol rotation error? (maybe just another bug)

MikeMillerGIS

If you have an active edit session, it should work. When there is an active edit session, the backend logic pulls all the fields.

MikeMillerGIS

The rule is calling Angle, I am testing to see if angle ever worked on a geographic system.

MikeMillerGIS

I narrowed it down to Buffer, not angle. This worked on my 2.8.4 machine, but did not work on my 2.9.2 machine. I will post an update if I learn more.

MikeMillerGIS

I have recreated that rule to not use buffer. There are disabled rules, the Auto_Contain_By_Rules that also will not work now. I have rewrote them to not use buffer, but found that Distance is now blocked on projected systems. If you need these rules, I will look at how to rewrite distance for you.

ForGeographic.zip

JacobBlankenship1

I will check this out, I am going to try and revert back to the older version of ArcGIS pro and see if that will fix the issues.

Thank you,

I will post again to give a update once I found something.

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.