Latest Contributions by RyanUthoff

I'm not sure what is going on with S123 last week and this week, but we had that exact same issue on multiple devices, including Windows and Android. In Windows, try resetting the app. Also, this geonet post has some good information as well. ... View more

Yeah, your records aren't truly null. It looks like it is just an empty string, or a value of a single space or something. If it was truly null, it would look like this: RyanUthoff_2-1747686255604.png   So your Arcade expression is working correctly, you'll just need to either correct the data to make the values truly null, or you'll need to account for empty strings/spaces in your Arcade expression. ... View more

The Arcade expression below might work. I think you'll need double equal signs. And the syntax for "IN" is a little different in Arcade. https://developers.arcgis.com/arcade/function-reference/array_functions/#includes $feature.Field1 == 'Open' && $feature.Field2 == 'LP' && Includes([10, 11, 12, 13, 14], $feature.Field3)   ... View more

If the ArcGIS Server machine is down, Portal and all applications on Portal (WAB, ExB, etc.) will continue to function, but the underlying services that the apps are consuming will not work. So in your case, your WAB/ExB apps will still open, but there will be no data inside of it (because the underlying feature services the apps are using aren't online because the ArcGIS Server is down). You'll get an error message something along the lines of "layer name failed to load." If Portal is down, then you won't be able to access WAB/ExB at all. It depends on what exactly is down, but if your web adaptor is online but Portal is offline, then you will get an error message like this. RyanUthoff_0-1747671816336.png If Portal and web adaptor are down, then your browser just won't load anything and will eventually time out. If both Portal and Server are down, then you'll most likely notice something wrong with Portal first because you won't be able to load the Portal site. But that doesn't mean something isn't wrong with ArcGIS Server as well. I'm not sure what you mean by "supporting snapshots", but as far as documentation, Esri's ArcGIS Enterprise documentation might provide some insight as well as Esri's training courses might help as well. ... View more

If you're okay with using Python outside of ArcPy, then I will give you a couple of scripts that can be used to determine the tables and views. Of course, you'll still need to modify the scripts to forward them to your views/items DB, but it should at least give you a starting point. You'd still be able to run this as a script tool in ArcGIS Pro. It uses Python to directly connect to a MS SQL database. #Output Tables import pyodbc def list_tables_mssql(server, database, username, password): try: # Connection string conn_str = ( f"DRIVER={{ODBC Driver 17 for SQL Server}};" f"SERVER={server};" f"DATABASE={database};" f"UID={username};" f"PWD={password}" ) # Connect to SQL Server conn = pyodbc.connect(conn_str) cursor = conn.cursor() # Query to get all user-defined tables cursor.execute(""" SELECT TABLE_SCHEMA, TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_TYPE = 'BASE TABLE' """) tables = cursor.fetchall() if tables: print("Tables in the SQL Server database:") for schema, name in tables: print(f" - {schema}.{name}") else: print("No tables found in the database.") except pyodbc.Error as e: print(f"SQL Server error: {e}") finally: if conn: conn.close() # Example usage if __name__ == "__main__": list_tables_mssql( server="localhost\\SQLEXPRESS", database="YourDatabaseName", username="YourUsername", password="YourPassword" )      #Output Views import pyodbc def list_views_mssql(server, database, username, password): try: # Connection string conn_str = ( f"DRIVER={{ODBC Driver 17 for SQL Server}};" f"SERVER={server};" f"DATABASE={database};" f"UID={username};" f"PWD={password}" ) # Connect to the SQL Server conn = pyodbc.connect(conn_str) cursor = conn.cursor() # Query to get all views in the database cursor.execute(""" SELECT TABLE_SCHEMA, TABLE_NAME FROM INFORMATION_SCHEMA.VIEWS """) views = cursor.fetchall() if views: print("Views in the SQL Server database:") for schema, name in views: print(f" - {schema}.{name}") else: print("No views found in the database.") except pyodbc.Error as e: print(f"SQL Server error: {e}") finally: if conn: conn.close() # Example usage if __name__ == "__main__": list_views_mssql( server="localhost\\SQLEXPRESS", database="YourDatabaseName", username="YourUsername", password="YourPassword" )   ... View more

This Esri documentation has some really good information on what settings are inherited in the view from the hosted feature layer that can and cannot be changed on the view. Per the documentation, edit settings can be configured independently on the views from the hosted feature layers they are created from. Meaning that you should be able to allow editing on the view, with it still disabled on the hosted feature layer. (Note that some additional edit settings, such as editor tracking, must be made at the hosted feature layer level. But the enable/disable editing setting itself can be changed independently on the view). This is something that I just tested with my own hosted feature layer/view in AGOL and it works fine for me. Editing is disabled in the hosted feature layer, but enabled on the view and I can add new data as well as edit existing data. Your "applyedits" response in the network traffic indicates a different problem. It appears that it is trying to add a record with the same key, which is not possible to do. For example, if ObjectID is your key field and you have a record with an ObjectID of 1. And then you try to add a new record with an ObjectID of 1, it will fail because a key with that value already exists. I've never really heard of that being a problem in AGOL though. If it's possible, it might be worth trying to enable editing on your hosted feature layer and see if you are able to add new records to it, or if you receive the same error. If you don't receive any errors, it might be worth trying to delete and re-create the view again. And if you do receive errors in the feature layer itself, then I think you have a different problem that needs to be resolved. ... View more