Latest Contributions by DavidSolari

One thing you can try is publishing a big rectangular polygon as a vector tile service, then using that as your basemap, that should make the downloads much smaller. Would be nice if that came with Enterprise deployments like the sample world cities do. ... View more

This is partially correct. You can't use cursors on direct database connections, but you can use them on feature service layers without bringing in the Python API. Obviously there's performance implications with this but it's possible. ... View more

That looks like a great tool, thanks Scott! That said, if I have several dozen tiny gaps to clean up, it'd be a bit faster to use something like my proposal from the Error Inspector pane as opposed to jumping to an area and switching tools each time. ... View more

Oddly enough this workflow is still in Pro, but it's part of the topology workflow actions. Having this as a choice for regular merges would be useful. ... View more

As mentioned in the docs, if you ask for an intersecting polygon using pulldata it'll grab whatever comes back first. If you want to ensure you only get one possible choice back you'll have to keep your polygons nice and tidy. ... View more

Security-wise, branch versioning hoists the main barrier to access from the database to ArcGIS Server and by extension your Enterprise setup. You publish the services out using database connections that use the data owner's authentication and then your portal's sharing options handles the rest. This is either a trivial change or a massive headache depending on how heavily your org uses Enterprise but as you've implied, ESRI is trying to make Enterprise the central hub for all remote GIS access so the sooner you bite the bullet the better. Performance is where it gets tricky. Edits to branch versioned data are supposed to be more database friendly in the long term due to only having one table that doesn't need compression, although I haven't benchmarked anything myself. You also get an archive built up of edits to DEFAULT which has none of the headaches of doing versioning + archiving in the old model. The catch is all edits have to be made through a feature service, so your overall performance drops compared to direct connection edits unless you run your servers on some very powerful hardware. The one escape hatch is if you're the "owner" of the data, you can make direct connection edits using the append, calculate field & delete features/records tools; there might be others but this is your minimum CRUD set. I say "owner" because I can never tell if you need the database owner or if your Portal authentication plays a part somehow but either way you have an avenue for doing large updates without bogging down the servers. I can't speak to DB replication, hopefully someone else can step in here. ... View more

You can plug answers into a "where" parameter as detailed in the docs. For the first question, if your label is the department branch and your name is the id, it'll show all the names to the user but it'll pull the ID so you can feed that into the second question. If you get errors when there's no department selected, try adding a hidden question the replaces a blank department with a valid but obviously incorrect value (e.g. coalesce(${manual_department_name},-1)) and then plug that into your second question. As for the second part, you can dig into the @pulldata functions to run a second query that returns just a count, then use that for your "relevant" check. ... View more

The "body::esri:visible" column should behave like the relevant column, but hiding and showing data with this column shouldn't clear out data. Give that a try and let us know how it goes, I've only seen this in the docs and never in practice. ... View more

Do the domains work if you use the Copy Data options to create a hosted feature service? Do you have a registered folder with file geodatabases that already works? If so does replicating steps 1 to 4 into one of those geodatabases work? ... View more

There's currently no way to have a service with zero feature layers. If you can add your query layer to an existing service that's ideal. If not, you can use your database's geometry functions to add an extra column to make it spatial. An example for SQL Server: SELECT a.*, geometry::STGeomFromText('POINT (0 0)', 3857) [Shape] FROM [user].[table] a   ... View more

Try publishing the form without the links to your registered services so it creates a brand new hosted service. You can compare this service to your registered service to see what changes have to be made. ... View more

Blindly calling First on a FeatureSet causes issues during rule validation -- even if the FeatureSet has data -- so do a if (Count(locid) == 0) return before you grab the first feature to avoid issues. ... View more