Latest Contributions by LucasScharenbroich

I have a python ETL script that published a shapefile as Feature Collection and then adds two CSV files as tables and establishes a one-to-many relationship between the spatial layer and the tables.  The first related table works as expected -- features are returned via the `queryRelatedRecords` endpoint and I can configure popups with related record information in the Map Viewer. The second related table always returns "No records found" when queried, even though it does contain related data. Both tables use the same field in the relationship with the spatial layer and both are published using the same script code. I've attached screenshots of the service directory information for the service and the relationship details for each layer.  Also, I show the results of running the queryRelatedRecords for both relationship IDs which illustrates that only the first relationship (id: 0) returns values.  A final screenshot shows the results of querying the related table directly to demonstrate that it does have records that match the district values. Looking for suggestions on what I may have done wrong when creating the relationships via the Python APi, or if there are any additional ways to introspect the hosted services to find out why the second relationship is not working as expected. def create_one_to_many(layer, table, parent_name, parent_key, child_name, child_key): table_id = table.properties.id layer_id = layer.properties.id layer_relationship_count = len(layer.properties.relationships) table_relationship_count = len(table.properties.relationships) # Create the relationship between the layer and the table on the District field layer_rel = { "id": layer_relationship_count, "name": f"{parent_name}_to_{child_name}", "relatedTableId": int(table_id), "cardinality": "esriRelCardinalityOneToMany", "role": "esriRelRoleOrigin", "keyField": parent_key } table_rel = { "id": table_relationship_count, "name": f"{child_name}_to_{parent_name}", "relatedTableId": int(layer_id), "cardinality": "esriRelCardinalityOneToOne", "role": "esriRelRoleDestination", "keyField": child_key } print(f"Layer Relationship added to {layer.properties.name}:", layer_rel) res = layer.manager.add_to_definition({"relationships": [layer_rel]}) print(res) if not res['success']: print(f"Failed to add relationship to layer: {res.error}") exit(0) print(f"Table Relationship added to {table.properties.name}:", table_rel) res = table.manager.add_to_definition({"relationships": [table_rel]}) print(res) if not res['success']: print(f"Failed to add relationship to table: {res.error}") exit(0)   ... View more

Using the latest 4.23 release, I am trying to override the snappingOptions of the Sketch widget in order to only show a limited number of layers to the user to select for snapping.  With a regular esri/Map object, I can successfully set the featureSources as desired.  However, if I load a WebMap, then setting the featureSources property on the snappingOptions has no effect and the FeatureLayers defined in the WebMap appear to always be used. Trying to clear the featureSource later (via sketch.snappingOptions.featureSources.removeAll()) appears to have no effect, either. Looking for a recommendation on how to work around this issue. Codepen demonstrating the issue: https://codepen.io/lscharen/pen/oNppGdj ... View more

I recently updated an internal application from JSAPI 4.16 to 4.22 to evaluate the memory and performance improvements in the Feature Layers.  After the update, the application first off over 2,000 requests to the various Feature Layers, which results in a load time of over 3 minutes. The volume of services requests results in several hundred returning `ERR_INSUFFICIENT_RESOURCES` from the ArcGIS Server, too. Our application loads a Webmap by ID from ArcGIS Online and creates about 20 stand-alone FeatureLayer objects that are used for querying that are not added to the map during start up. It appears that many of the requests are for the gridded query strategy (different, sequential bounding boxes) of the Feature Layers, which I can understand, but didn't expect the volume of queries or such different startup behavior from 4.16. Looking for advice on what approach I can take to isolate and control the amount of queries made by the FeatureLayer class and if there are any specific behaviors of the FeatureLayer that we should be aware of in the jump from 4.16 to 4.22 that might be exacerbating this issue. Note: I have reviewed the Breaking Changes information and the Release Notes in general, but did not pick up any anything specific from those sources. ... View more

I have a pre-existing, custom routing services that has been used successfully with the JSAPI 3.x for a couple of years.  We are in the process of updating to JSAPI 4.x and have run into a behavior issue where the built-in Directions widget is passing parameters to the `route` endpoint that are causing an error to be returned. Specifically, the 3.x API includes   "simplificationTolerance":null, "simplificationToleranceUnits":"esriUnknownUnits"   with the travelMode argument which the 4.x API does not.  These parameters do not appear to be exposed in the RouteParameters object, which required more .... invasive ... methods to override. Without these travelMode parameters set, we get the following error response the the "solve" endpoint   { "error": { "code":400, "message":"Invalid or missing input parameters.", "details":["The following travel mode is invalid: ..."] } }     Any recommendations on how to finess/configure the Direction widget to work around this issue; or perhaps even change how the Network Analyst service is published to make it friendlier to the JSAPI 4.x conventions?   Version Details * ArcGIS Server 10.5.1 * Network Analyst Extension 10.5.1 ... View more

In support of Ideas like Version Control for WebMaps in ArcGIS Online and in conjunction with the coming support of Jupyter Notebooks as Portal Items, it would be extremely powerful if users could register Jupyter Notebooks to be used as callback hooks for a limited subset of the ArcGIS REST API. As a specific example, getting a callback from Add Item and Update Item callbacks would allow updates to a Web Map to be intercepted and automatically pushed to a git repository or similar version control system, thus opening up the ability for organizations to roll back to previous versions for critical, production items. Intercepting the Add Relationship API could allow for organization-specific security policies to be put in place beyond what is offered by the existing Role Capabilities. Tools like nbparameterise have established conventions for passing parameters into a notebook which could be leveraged in this scenario. ... View more