Latest Contributions by CVWDGIS

Same here. Publishing a feature layer as referenced data from a registered SQL database, and I am not able to use the contingent values functionality on our enterprise portal. Editing the service in Pro does allow for the utilization of the contingent values check through. So if you've got users accessing the published data through Pro, it seems like contingent value checks are an option, just not through a web based interface on portal. Portal version 10.8.1. Upgrading soon to 11.2, so I'll let you know if anything changes.   ... View more

Hi all, I am also having this issue and the easiest fix I've found is to convert the legend to graphics. Right click the legend object and 'Convert to Graphics.' Be sure that the legend is finalized, as you'll not be able to make any further adjustments after it is converted. This allows you to maintain the 'Only show features visible in the map extent' setting. Still need to fix the bug, but this is a solid work-around.  ... View more

Kylie - I made a series of "How to..." word documents covering;  ...Add New Asset, ...Edit and Delete Assets, ...Install, ...Login, and ... Reload a Map.  For me it's important to know your audience, meaning these guys don't know GIS, they use it as a tool to do their job more productively.  I use plenty of screen captures with red arrows walking them through a workflow in my 'How to...' documents and I try to avoid GIS terms.  I feel using the screen captures it's as if I'm there showing them step by step how to do an activity. Tom ... View more

We ran into a similar issue today; we have a feature layer setup for editing and we wanted to add the ability to support photo attachments.  This should be a trivial task by enabling attachments through the AGOL UI.  However when we tested this we got the "Update Failed 1 attachment could not be sent" error message.  After hours of troubleshooting I finally googled the error message and it lead me here.  Republishing the service seemed like a solution for some.  As we investigated this we noticed that Extent, within the rest end point, had a mixture of lat/long and state plane coordinate values. Leading us to believe that the data got corrupted somehow.  We had other issues when trying to export the data but we were finally able to export it.  We now host the data in our Portal so we have better control over it.  But in the end we did have to republish the service and everything is working as expected.  I hope this helps someone. ... View more