|
POST
|
The item is missing on the feature service page itself, however. Not just the web map. I need the feature layer to update because this service is being passed through to AGOL via URL with stored credentials. So if it won't show up on the feature service, there is no way to get it to show up in AGOL.
... View more
02-18-2025
09:34 AM
|
0
|
0
|
580
|
|
POST
|
I know the update was successful because I can see the symbology changes that I made in the map. I can also see the new feature class that was added to the service on the REST service page. I made sure that the Layer IDs were correct and not conflicting before publishing so I know that there is no issue there. Any ideas on how to get the layer to show up? A few screenshots below: An additional test was I just republished a test layer from scratch containing all 8 layers. When done that way, it shows up as expected with correct symbology. Using this is not ideal, however, as we have numerous maps and applications that are dependent upon this service so I really do not want to have to go and reconfigure every single map that utilizes these layers.
... View more
02-18-2025
08:11 AM
|
0
|
2
|
595
|
|
POST
|
Really annoying to see that this is unanswered two years later.
... View more
02-18-2025
06:59 AM
|
0
|
0
|
863
|
|
POST
|
I know it's been 5 years, but I had to say thank you. I was having this problem and this fixed it for me! Amazing that ESRI doesn't have any kind of warnings or anything about that!
... View more
02-17-2025
02:31 PM
|
0
|
0
|
317
|
|
POST
|
I have created a zoning viewer that I want to be searchable by parcel number. In the instant app, I have the search configured as follows: If I use the search field, however, it does appear to search the layers as it auto suggests a few parcels, but it suggests parcels that don't make sense. For instance, if I search 'B 02' it will show the following suggestions: These are all valid options and it will zoom to them as expected. However, I am trying to search for parcel 'B 02 041.' It will never show up as a suggestion, however, no matter how much you type. In the screenshot below, you will see that I have entered the full parcel number in the search box, but it does not suggest it. Despite the parcel literally being on the screen (red parcel highlighted in blue). To further complicate this, the search works just fine in the web map that is powering the instant app. See below: I've been trying to figure out what is causing this for several hours to no avail so I would greatly appreciate any advice!
... View more
02-13-2025
02:37 PM
|
0
|
5
|
1004
|
|
POST
|
Thank you for sharing this solution. I have been recreating my map from scratch when it happens, despite how much it pains me to do it. I am going to make sure to try the trick with the topology layer next time.
... View more
01-30-2025
12:30 PM
|
0
|
1
|
1262
|
|
POST
|
It was a conflicting rule... Good grief! I'm ashamed to admit how much time this oversight cost me. Lol
... View more
12-17-2024
04:40 AM
|
0
|
0
|
941
|
|
POST
|
Sorry to say that I did not. I ended up recreating the map from scratch.
... View more
12-11-2024
02:21 PM
|
0
|
0
|
813
|
|
POST
|
I'm fairly new to playing around with attribute rules. I am looking to have a rule that automatically nulls out two fields that store x and y geometry when a feature's geometry is changed. The reason for this is so that I can then run a GP tool later that automatically selects all features with a NULL value and calculates the new geometry for them in decimal degrees. I only want this rule to fire when the geometry of a feature is changed. Here is how I have configured the rule: Here is my expression: if (!IsEmpty($feature.Lat)){
return null;
} If I'm correct, that statement essentially says "If $feature.Lat is NOT empty, then make it Null" However the rule does nothing. If I go in and edit a point's geometry, the geometry is never set to null. Am I missing something?
... View more
12-11-2024
10:59 AM
|
0
|
2
|
1010
|
|
POST
|
I maintain addressing data for our county and we have to maintain the data in two standards. The 'new' NENA 911 standard, and the old legacy standard that works with our 911 CAD system. The fundamental difference between the two is that the new standard fully spells everything out and is in proper case whereas the old CAD standard uses abbreviations and is in all caps. So for instance: Road = RD Street = St Alley = ALLEY Bend = BEND I would like to set it up so that when I populate the 'New' standard's field, it automatically translates that to the correct value for the old standard. The challenge with this is that there are over 100 possible values, and thus more than 100 translations that would need to occur. I was considering two ways. The first was an attribute rule with a very long if/else statement that translated everything. I haven't tried this yet mostly because of the tediousness of writing it as well as concerns about the performance impact of such a long attribute calculation. The second was with conditional values. I've actually been testing this but I keep getting an error. I have a field group set up that contains both fields. I have Bend and BEND paired, but for some reason, when I actually edit the field to assign the "Bend" domain, I get an error message on the attribute window saying: This doesn't make sense, however, because as you can see, it IS a member of that domain. Probably something that I'm not understanding but I have yet to get it to work correctly. All that being said, I'm hoping someone here can tell me the easiest way to accomplish this.
... View more
12-06-2024
08:29 AM
|
0
|
2
|
503
|
|
POST
|
I am trying to write an attribute rule that compares a parcel's calculated area to the stated (deeded area) and if it is off by more than 10% of the total acreage to flag an attribute field for it. This rule does that: //If the absolute value of error acres is greater than 10% of the stated acres, then report mismatch. Otherwise, report that it is acceptable.
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.")
return QAQC_Eval; The problem I am having is that there are sometimes exceptions where I need to be able to manually clear the flag and mark it as an exception (like in cases where I have looked at the issue but can't correct it due to insufficient information or some other problem). I would have thought that if I had checked the "Editable" box in the attribute rule configuration, that this would allow me to manually change this value if required. Unfortunately, that doesn't seem to be the case because when I manually change that field, I get an error message saying "Edit Operation failed - no edits producing database changes were found." Here is the current rule configuration panel: Ideally, this rule will only fire off if the geometry is changed, which is why I only have the "Shape" field set to active. Would really appreciate some help with this as this could really improve the QAQC process for our parcel data!
... View more
11-18-2024
02:18 PM
|
0
|
4
|
664
|
|
POST
|
@EmilyGeo I have resolved my issue. It was apparently a weird bug. Despite having the search set up to utilize multiple attributes, certain searches would not work. For instance, I had configured search to look for an address in a field containing address data. Ever record had an address, but whenever I searched, nothing would show up. I ended up resolving the problem by deleting and re-indexing the fields on that feature class.
... View more
11-07-2024
12:22 PM
|
0
|
0
|
1236
|
|
POST
|
Is this still an issue? I am having the same problem. Layer is configured in the search setting but no results are showing.
... View more
10-24-2024
08:22 AM
|
0
|
0
|
1265
|
|
POST
|
Great examples and very interesting use cases. Thank you both!
... View more
10-03-2024
04:17 AM
|
1
|
0
|
878
|
|
POST
|
Thankfully I was able to resolve the issue. The problem was a result of AGO assistant doing an incomplete job of 'replacing service URLs.' For some reason despite clearly reflecting in the AGO UI that the service URL was correct, it had only actually updated one of the 7 copies of the water meter layer. All of the other references were still to the original layer, which had security enabled. I copied the JSON out to a text editor, found and replaced all of the incorrect references, and then updated the JSON in AGO Assistant. That fixed the issue! Regarding the instant app, yes, that is the plan! This was just a quick and dirty map trying to diagnose the problem before proceeding any further.
... View more
10-02-2024
02:44 PM
|
0
|
0
|
940
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 5 | 4 weeks ago | |
| 1 | 10-02-2024 07:04 AM | |
| 1 | 05-23-2024 02:54 PM | |
| 1 | 07-29-2025 01:09 PM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|