Latest Contributions by RyanUthoff

I believe I've seen this before, and it has something to do with the size of the browser window (which may or may not be affected by your monitor size and/or resolution.  Basically, if your browser window is too small, then the web map is not able to fully open the pop-up like in your first example, therefore causing it to be "minimized" in your second example, unless you open the pop-up full screen. ... View more

For the flashing capability, I'm not sure if there is a way to make it flash straight from the table itself. I'm not seeing a way to do that when looking at it. However, an alternative method could be adding a "List" widget. It will require a little bit of extra configuration to make it look like a table, but you can configure it so when you select it, it will flash in the map. Regarding the defect data, I think your best bet for it is to turn that table into a related table. That way, when someone clicks on the pipe, it will give them an option to show all of the related records associated with it. In this case, it would be your defects. That way, you won't have two tables that are not associated with each other, even though logically, they are. Edit: Another alternative would be to create an Experience Builder app. It will give you a LOT more flexibility as far as what you can create and do, but it has a much steeper learning curve. ... View more

Would you be able to provide an example of what you're trying to achieve? Like are you wanting the upstream and downstream manhole in the sewer line attribute data? ... View more

The issue @RachaelHarbes mentioned reminded me of an issue we experienced. In our case, we had a mix of dedicated and shared instances, but the System/DynamicMappingHost.MapServer kept crashing (which also crashed the entire server). Luckily for us, we saw error logs specific to one other feature service as well, so we started troubleshooting with it. Once we switched it to dedicated, the System/DynamicMappingHost.MapServer no longer crashed. BUT.....the feature service itself continued to crash, but it only crashed the feature service itself and not the entire server. We isolated the issue to a view that is in the feature service, but still don't know why that specific view is causing it to crash (we can replicate the issue in two different ArcGIS Enterprise environments). I'm assuming you've done this already, but it might be worth looking for other errors referencing specific feature services as well. ... View more

I believe this post will address your concerns. https://community.esri.com/t5/arcgis-enterprise-questions/apache-tomcat-vulnerability-cve-2024-50379/m-p/1574838/highlight/true#M41383 The very last comment references the CVE you are concerned about (although you'll need to read the entire thread for the full explanation). ... View more

In my experience, you have to manually define the relationship in the Map Viewer (which was not the case with the Classic Map Viewer). Select the parent table in the layers menu and then click the Pop-ups button on the right side. From there, click Add content, and then click Related records. After doing that, it will detect your relationship class and include it in the pop-up in the map viewer. I'm not sure if that's something you've tried or not, but thought I'd post it in case it helps.     ... View more

Do you have other maps containing data from other feature services and databases in Portal? And if so, are they going slow as well? Basically, what you will need to do is isolate the problem. Either narrow it down to a specific feature service or a specific component of ArcGIS Enterprise environment. If the issue is isolated to only this one feature service, then it's possible that there is something wrong with the underlying data. Such as spatial/attribute indexes needing to be reindexed.  If everything is slow, then it could be a problem with your enterprise environment. Perhaps security software is slowing it down, or something is misconfigured elsewhere. In that case, you'd probably need to work with your IT department to troubleshoot that further. ... View more

Does the map load slow if you directly view the map in the map viewer (outside of the dashboard)? Or is it slow only when accessing it through the dashboard? ... View more

For what it's worth, I took your csv and it worked fine for me in both AGOL and our dev portal. So I don't think there is anything wrong with your CSV itself. A quick search for that error message brought up some other geonet posts that suggested it could be a problem with the Data Store or some sort of connectivity issue. Are your other hosted feature service currently working? Any issues when validating the ArcGIS Data Store through Server Manager or any issues validating your federated server site through Portal? ... View more

Here is the Esri support article for this method describing the workflow: https://support.esri.com/en-us/knowledge-base/how-to-create-the-fieldworker-view-for-surveys-publishe-000020413   ... View more

There are probably a handful of ways you could implement a solution for this, but I'll share what I think might be the easiest solution. Create your Survey123 form and publish it like normal. Then, lock down the hosted feature service. Of course, you will still need to share the hosted feature service to those who need to submit surveys, but you can lock it down from the settings page to where users can only see the features they create (or none at all). See screenshot below. After you do that, you can create a View Layer from your hosted feature service and specify the fields you want visible to your admins or anyone else that needs access. Upon creating the view, the default behavior is that editing is disabled and that all data is visible (meaning that people can see all the features, even if they didn't create them). But, you can enable editing if necessary. ... View more

Since the spatial layer and the related table (repeat) are two separate tables, then that means the Dashboard will also treat it as two separate layers and I don't believe there is a way to combine them within the Dashboard itself. However, what you might be able to do is create a View Layer of the data to get it all in one view that the Dashboard can reference.  In AGOL/Portal, go to the Survey123 feature layer page and then click Create View Layer > Joined View Layer. This page will allow you to create a joined view consisting of joined tables from the feature service. I attached a screenshot of what it will look like. So, you would set your Target/Join fields and in your case, you would select a One to Many relationship since you can have multiple violations in your survey. After you do that, it will create a feature layer view that you can use in your Dashboards. However, one thing to keep in mind is that it will essentially "duplicate" your parent table with however many related records (violations) you have. For example, let's say you have one record in your parent table, but three associated violations. You will have three records in your view, one for each violation. The spatial/attribute data from your parent record will be "duplicated", but the violation data will be unique. ... View more

Your local support team is correct. This issue with ArcGIS Enterprise started AFTER Esri already ended support for it. Therefore, Esri is not going to release a patch for it. This is standard in the software industry where companies do not support software after it has reached end of life. The only "real" solution is to upgrade or use Firefox. ... View more