Latest Contributions by JonDeRose

Hermien Bijker‌ Based on the items you have already attempted I would suggest reviewing the following topics within the UN Package Tools FAQ.   I've shared this with Python‌ for visibility as this is more of a core python issue. I need to install the untools on a machine that is disconnected from the Internet. Can I install the tools? Frequently asked questions—Get Started | ArcGIS Solutions  I followed the steps above and still cannot see the untools. What should I do? Frequently asked questions—Get Started | ArcGIS Solutions  ... View more

Hi Joshua, A similar question was posed over in ArcGIS Pro which I would recommend checking out.  While subtypes aren't a requirement for using contingent values, in the blog,  I used the example of speed limit values to illustrate how contingent values could be used to provide additional logic to constrain the available picklist values in the domain by subtype.  Contingent values also have the added benefit of providing a level of data validation to ensure errant values aren't entered into the database. Like subtypes, contingent values allow for abstraction at the domain level; however, contingent values take this abstraction much further by restricting the options available within the picklist. Envision a scenario where you have a feature class of city streets categorized using three subtypes for local, collector, and arterial streets.  The subtype is valuable to provide one level of abstraction and define different default values for speed limit (such as 25 miles per hour for local streets); however, there is nothing that would prevent an editor from choosing a value other than the default (perhaps setting this to 70 miles per hour). While other values may be technically allowed within the domain, they would be invalid in actual usage for this road type.  Applying contingent values in this scenario improves upon the logic to constrain the options available for the subtype’s speed limit and prevent edits such as this from occurring.  Additionally, validation is present during data entry to alert the editor to the presence of invalid values, which highlights impacted fields and disables the option to save. ... View more

Hi Michael, Thank you for the feedback.  We are all excited about the possibility of leveraging contingent values within Collector and other Runtime clients in a future release.  Please add your voice to this Idea to bring support for contingent values to ArcGIS Online. ... View more

Hi Bob, As Marc mentioned above:  currently, editing contingent values is only supported in ArcGIS Pro.  The Runtime work to support these in other clients such as Collector is planned for a future release. ... View more

Contingent values are currently supported within ArcGIS Pro alone.  Please review this related idea to add your vote or voice for this functionality: https://community.esri.com/ideas/16708  ... View more

Bal Atwal Currently, ArcGIS Pro is the only client aware of contingent values and able to consume them. There are plans to expose contingent values through Runtime in a future release which should then pave the way for expanded usage beyond ArcGIS Pro. An Idea has been created with a similar request which you can use to track this capability. ... View more

Hi Andrew - From your description of your database config it sounds as though you are using a DBO schema geodatabase and have assigned users to a AD group that has db_datareader/writer assigned along with db_owner. While this will enable your users to have data ownership permissions within the SQL Server geodatabase, they would not be able to perform the role of data owners from within ArcGIS. The information outlined in the link: "User permissions for geodatabases in SQL Server" is correct in that data creators only require 'CREATE TABLE' and 'CREATE PROCEDURE' it also references that "User names for any user accounts that own data must have the same name as their default schema."  If using a DBO schema geodatabase, only users, or groups which assign user's sysadmin rights within the SQL Server instance will be able to create data.   While the db_owner role does enable elevated permissions within a database it is not synonymous with being a sysadmin (dbo). The following link provide some additional information on the dbo ownership of geodatabase ownership: A comparison of geodatabase owners in SQL Server Adding Windows-authenticated logins or groups to a SQL Server database - Jon ... View more

Hi Jason - Error 000655 is a rather general error; however, when described in conjunction with the text " Parameters are not valid" makes it sound as though the externally run Python script cannot gain access to a spatial database connection or other parameter necessary to complete the synchronization. While you appear to be able to run this within ArcGIS Desktop from your description using ArcCatalog] > [Edit Model] > [Validate] > [Run], can you also simply double-click this model within the toolbox and run it successfully? Would it be possible to provide a copy of the model and or script being used to take a closer look?  Have you tried to hard-code the database connection and replica path for the model's replica parameter? - Jon ... View more

Hi Bertrand: Can you provide some additional information on your configuration and the steps you have taken to this point?  The (-450) error is stating that the ArcSDE binaries are not compatible with the geodatabase release. The error you are displaying states that the database has not been upgraded and thus the system tables it is looking for (ie. GDB_ITEMS, etc.) are not found. Verify that this geodatabase has in fact been upgraded from 9.3.1 to 10.0 as you stated.  Connect to the geodatabase from ArcCatalog using a direct-connection and right-click the connection.  Go to "Properties and check the "Upgrade Geodatabase" button for information on the status of the ArcGIS client and ArcSDE geodatabase compatibility.  Also, verify that the ArcSDE release that you have installed is consistent with the database version that you have upgraded to.  This should be consistent with the ArcGIS client that was used to perform the upgrade. - Jon ... View more

Nathan, 'sdelayer -o load_only_io' does much the same thing as the arcpy.management.RemoveSpatialIndex().  Either would improve the performance when loading objects as you would not have the index to navigate.  Load_only_io goes a bit further than the arcpy function however and places a flag on the feature class metadata that will only enable store and replace I/O operations.  In other words, while dropping the spatial index alone will not prevent editing within ArcGIS, setting a feature class to load_only_io will.  Hope that helps. - Jon ... View more