Latest Contributions by ChelseaRozek

@SubaKrishnan They are non-reporting layers on the map for reference and are map server layers not hosted on ArcGIS Online. The app is here. If you zoom in (try bottom right corner), orange hatching and blue drain lines will appear. They should have very simple popups, but unfortunately everything is seen, like OBJECTID. Here's how it looks in the webmap, just 5 attributes with no OBJECTID on the orange hatching:    ... View more

Hi @SubaKrishnan ,  thanks for pointing that out to me, I appreciate it. I tried it out and can see popups now, however they don't adhere to the settings from the webmap. I have popups turned off on a layer, but they still show up in the Reporter app. I have only two fields showing in another layer's popup, but I can see them all in the Reporter app. I tried making a new Reporter app from the same webmap, and I see the same behavior. It's the same layers as before: a map service published to our own ArcGIS server. Let me know if you'd like some screenshots. ... View more

The documentation says "the selection layer is only useful as a temporary working dataset, for example, as an input into a geoprocessing model. It lists the FeatureIDs (FIDs) or ObjectIDs (OIDs) of the selected features. These are invalidated when the original data source is updated or changed." So I think your best bet is to make a more robust definition query or filter that you can use that won't change if the features are reconstructed. You may need to add attributes to your feature class with "regions" or whatever is applicable to your dataset. Then in the webmap you can bring in the layer multiple times and apply different filters to each instance. If you can make the data a hosted feature layer (like you're not trying to publish it from your own ArcGIS Server), you can create views of that hosted feature layer which would do the same thing except the end users can't turn the filters off to potentially edit outside of their region. ... View more

Looks like that bug is fixed, but you still can't sort tables alphabetically. Still hoping for that functionality... ... View more

Same here, I just got an alert that our "AGO Service Account" used up all its credits. I would love to know who used them all! Luckily, I had only allocated it a limited portion, but I would like to reach out to that user to chat about what they're trying to accomplish and what their best options might be. Right now, all I can go off is who signed in today and has the appropriate permission to do this, but it's still multiple people to go through. ... View more

@DougBrowning thank you so much for your comment! I've been combing through the field lengths, default values, and calculations for my huge survey without success. "wrong data type" made me think about the attributes I'm pulling from other layers. While the field lengths were fine, a few intersecting polygons had null values and THAT is what was causing this error in my survey. so happy to finally resolve this! ... View more

@mkaburis Yeah, that's the issue I'm running into. We have different enterprise geodatabases for different departments so they have full control over the layers they're the subject matter experts of. Thanks for confirming that it's not supported.  ... View more

@Jake_S , @ToddW_stl the view workaround would only work for immediate attribute rules traditionally versioned, right? We have branch versioning set up for the full benefit of attribute rules, which seems incompatible with this workaround as the view would need to be included in the published service to be referenced by the rule, which isn't allowed. ... View more

@ArmstKP Even though we edited the JSON of our webmap to use the ObjectID, it didn't change what it field it says is searchable in the webmap's settings page, though it does work to search by the ObjectID. To make sure you have the correct layer ID string, I would first set another field on that layer to be searchable via the settings page and then just tweak the JSON to say ObjectID instead of that field's name and change the type to esriFieldTypeOid. ... View more

I believe this is a duplicate of this idea, please upvote! ... View more

Was just trying to do this with ArcGIS Assistant and was bummed that it's still not possible. This idea would be very helpful for my organization. It will be such a hassle to make new layers and update all the webmaps and apps. ... View more

I tried dissolving my roads based on name and a few other fields we use to label. I tried adding in "text-repeat-distance" in the Vector Tile Style Editor's JSON editing (after confirming I was on the right label class by changing the text color). Neither helped. I wouldn't think it's a tile issue as I'm only looking at an 800 ft driveway. ... View more

@ChrisWesson I bumped up the Minimum Interval and republished to ArcGIS Online but I'm still getting the duplicate road labels as seen in my screenshot earlier in this thread. ... View more

Would definitely use this a lot. Currently have duplicate accounts for testing, but with the move to named user licensing, it would indeed be a "dummy" account if we're paying for two accounts and potentially two Pro licenses for the same Administrator. The testing I need to do is just having a subset of my full permissions for a while, so it's not asking for anything more than the Administrator account would already have. Having another administrator temporarily downgrade us is a hassle. I imagine you'd have to reassign all your items to another user if you went all the way down to Viewer too. ... View more