Latest Contributions by MDB_GIS

‎10-02-2024

Thankfully I was able to resolve the issue! Apparently using the 'Replace Service URL's' tool in AGO Assistant did an incomplete job. It did not replace all the required URL and itemIds in the JSON file, so it was still secretly referencing the old service, which still had security enabled, even though it appeared to be referencing the new service. I copied the JSON code into a text editor and then used find and replace to find all instances of the outdated itemId and URL and updated them to the new one. Once I did that, it worked like a charm!

‎10-02-2024

Here is a link to the map: <Redacted> The link will take you to the overview page, which loads without issue. But then when you open the map, the map appears to briefly try and load before a login screen pops up. I have tried going through the developer console but I don't see anything indicating what is responsible for the login screen.

‎10-02-2024

That's odd. Done numerous tests with others, including ESRI and they are all getting prompted to login. What a mess!

‎10-02-2024

I used my browser's diagnostic tools (specifically networking) to look for requests that were coming back with authentication failures

‎10-02-2024

That is where I was looking. Using that link do you see any? I am unable to see any. The map will even pop up very briefly before the login screen pops up.

‎10-02-2024

How did you track down that error message? I am having the same problem with this map: https://arcg.is/1aL85.

‎10-02-2024

Ok! Made some progress! I updated the code to this based on your suggestion: //This expression checks to see if the geometry of a feature has changed. If it has, then it compares the deeded acreage to the calculated acreage. If there is a discrepancy larger then 10%, it will flag that feature with an error in the attribute table. Otherwise it will flag it as "Ok". var QAQC_Eval = iif(abs($feature.ERROR_ACRES) > ($feature.StatedArea * 0.10), "Acreage mismatch. Deeded acres and calculated acres do not fall within OCGIS tolerance.","Acreage ok. Deeded acres and calculated acres fall within OCGIS tolerance."); //If the absolute value of error acres is greater than 10%, then report mismatch. Otherwise, report that it is acceptable. if (Geometry($originalFeature) != Geometry($feature)){ return QAQC_Eval; } else { return $feature.QAQC_Status; } //This expression checks to see if the geometry of a feature has changed. If it has, then it compares the deeded acreage to the calculated acreage. If there is a discrepancy larger then 10%, it will flag that feature with an error in the attribute table. Otherwise it will flag it as "Ok". That at least produces the attribute edits. But it seems to be ignoring the check to see if the geometry changes. Even if I only edit the attributes without touching the geometry, the rule always fires. I need to be able to prevent it from making changes unless there has been a geometry update. Any ideas?

‎10-02-2024

Thanks for your response! The problem was indeed in the JSON. Using the "Update URLs of services in a web map" option did indeed update the URL, but there was an "itemID" parameter that also pointed back to the original layer that was not updated. This was the problem. I manually edited the JSON to replace that with the new feature class and it seems to have resolved it. AGO Assistant should either replace that item ID or at the very least warn you that it is not doing to full job.

‎10-02-2024

I have created an attribute rule that that seeks to do a few things. First, it checks to see if the geometry of the feature has changed from it's initial state. If it has, then it compares two values, the legal acreage from a plat and the calculated acreage from the geometry. If there is a difference of 10% of the legal acreage, then it is supposed to flag it as an error for review. If not not, then it flags it as ok. If the geometry of the original feature has not changed, however, then it simply returns the same value so that no changes are produced. My code: var origGeometry = $originalFeature['Shape_Area']; var newGeometry = $feature['Shape_Area']; var QAQC_Eval = iif(abs($feature.ERROR_ACRES) > ($feature.StatedArea * 0.10), "Acreage mismatch. Deeded acres and calculated acres do not fall within OCGIS tolerance.","Acreage ok. Deeded acres and calculated acres fall within OCGIS tolerance."); //If the absolute value of error acres is greater than 10% of the stated acres, then report mismatch. Otherwise, report that it is acceptable. if(origGeometry != newGeometry){ return QAQC_Eval; } else { return $feature.QAQC_Status; } //This expression checks to see if the geometry of a feature has changed. If it has, then it compares the deeded acreage to the calculated acreage. If there is a discrepancy larger then 10%, it will flag that feature with an error in the attribute table. Otherwise it will flag it as "Ok". The expression says it is valid, but when editing the layer to test the conditions, no changes are ever made. I can intentionally create a feature that should return an error but nothing happens. I can't even tell if the rule is running or not. Is there something in the above code that I have missed? Any pointers?

‎10-02-2024

Long out of date, but thanks to you and @JoshuaSharp-Heward for mentioning IIF statements. I was able to greatly streamline some of my attribute rules using this newfound knowledge!

‎10-02-2024

Tossing my vote in here for this as well. I'm trying to create a QAQC layer for our parcel fabric. I have an attribute that is acting as an error flag where if the stated area and calculated area are not within 10% of each other, it is flagged for review. In some instances, it can be redrawn and corrected, but in others, there may not be a better plat available, so the flag is cleared since it can't be improved. But with the way attribute rules currently work, if that parcel gets an attribute update, then it would add that error flag back since the it was technically updated even though the geometry didn't change.

‎10-02-2024

I have recently started studying and implementing a few attribute rules in our data but I don't quite understand the purpose of the "Delete" trigger as it seems superfluous. If a feature is being deleted, then why would you need to update the attributes on it? What are the use cases for it? I'm assuming it is more useful on the constraint and validation rules? I haven't dove into those yet so I'm having a hard time envisioning how to use the delete Trigger.

‎10-01-2024

We have a webmap that currently contains a feature service for water meters. That feature service has editing enabled on it. We also have a view layer that was created from that feature service that has editing disabled. I want to replace that original editable feature service with the URL for the view only feature service. First, I tried to do this using AGO assistant. I updated the URL to the new view layer that has editing disabled and saved it. I can see on the AGO assistant that it is now using the view feature service URL. However, if I go to the webmap itself and open it up I can still edit the feature class. If I go to the item properties to open the item detail page, it is still pointing to the the original feature service that has editing disabled despite the fact that AGO assistant says it is not. Hoping that it was a bug, I decided to try the same thing in ArcGIS Pro. I opened the web map in arcgis pro, and updated the data source to the feature class view that has editing disabled using the "Set Data Source" option in properties. Same story, it appears to be pointing to the correct source, but after saving the web map and opening it again in AGOL, it is still pointing to the original feature service that has editing enabled. What gives? I am currently working through an ESRI support case on this, but the rep I am talking to now just said that she thinks this is an expected behavior. I couldn't really follow her reasoning. She said that since it is just a view of the original feature service, everything is going to reflect back to that. While I understand that the view is essentially just a copy of the original feature class, I still thought the view was supposed to honor different share settings. Am I misinformed? If not, then what is the point of a view layer? I'm quite confused here.

‎09-12-2024

I want to add a new field to the parcel fabric but I'm not sure what's steps are needed in order to do so. Do I just need to stop the service, add the field in the enterprise geodatabase version, and then republish? Is that it?

‎09-03-2024

Glad to hear it!

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by MDB_GIS

Re: Web Application asking for Login when all Layers are Public

Being asked to sign in to web map where all features are shared publicly and anonymous access is enabled at org level.

Re: Web Application asking for Login when all Layers are Public

Re: Web Application asking for Login when all Layers are Public

Re: Web Application asking for Login when all Layers are Public

Re: Web Application asking for Login when all Layers are Public

Re: Help diagnose why attribute rule is producing no changes in data?

Re: Replacing a feature service URL in AGOL web map with a view layer URL is not working. (Using AGO Assistant and ArcGIS Pro)

Help diagnose why attribute rule is producing no changes in data?

Re: arcade if, else (do nothing)

Re: Attribute Rules: Update only on geometry change

When would you use the "Delete" trigger for attribute rules?

Replacing a feature service URL in AGOL web map with a view layer URL is not working. (Using AGO Assistant and ArcGIS Pro)

Is there a workflow documented for adding a field to an already published parcel fabric?

Re: I think resampling for tiled layers is either bugged or broken. Tiled layer will not draw outside of the tiled extents that it was published with.

Re: How to maintain Natural Boundaries?

The Save As option should create a local folder an...

Re: Replacing a feature service URL in AGOL web ma...

How to get an attribute rule to calculate XY in De...

Re: What format does the Cogo reader require?