Latest Contributions by RPGIS

Hi @dsinha. It is recommended should the desired result not be what you want. It could help you troubleshoot where there are issues in your code. ... View more

Hi @dsinha, Have you used the Console() function to see if there is any result for the feature? You can also verify that there are records by using the Count() function in conjunction with the Console() to see if there are any records that are returned by your query. It could be that either the query is resulting in no records returning or that there is something else going on. Did you double check that the field name(s) exist and you are filtering for the correct data? Ex. ("ParcelPin = '1000000'") vs (ParcelPin = 1000000"). If you use the console then it should help troubleshoot the issue. ... View more

I believe @AustinAverill was just an example. You might need to change your Portal and portal item to whatever your data specifies using the structure provided. ... View more

Hi @ErinHoover, What have you checked in order to identify the issue: Is the data source a hosted or reference feature service from a .sde database? Is the table from a data expression that has the source ID incorrect? Is the dashboard created with data that is no longer shared to a group that once had access? If you add the data to a new dashboard, do you see the same kinds of errors? Please let us know so it can help us further identify where the issue lies. Sometimes these are multifaceted issues so there could be a number of causes. Some ranging from just pointing to the right data to not having access to the data or how the dashboard was created. ... View more

There is a way to mimic the ability. The ability for arcade to do dynamic calculations exist as a data expression but otherwise, if you mean to enable custom popup expressions, then it does not. There might be limitations regarding the overall JavaScript capability when compared to using a custom data expression. You can still modify the values and the prefixes if you want something simple but otherwise the data expression might be your only option for the time being. ... View more

There is a way to do this and there are two ways, at least to my knowledge, that can work to achieve this. Using the List method: Use @AustinAverill suggestion to create a new dataset as a data expression. Once the data expression is created, add the list to the dashboard. Once the look and feel of the list, set your layer action to filter that specific list using that common attribute Using the Category Selector in the header: Step 1: Add the header to your dashboard Once added, select configure (upper left hand corner of the header) and select the category selector In the category configuration, select grouped values. Select the parent table Select the field that has the relational information in both the parent and child table(s) Step 2: After completing step one, follow the same steps as Step 1 but for the child table Apply a filter to the child table based on your specific criteria Set the field to which value you want the layer to be filtered/selected Step 3:  Once the category selector is configured, go back to the first category In the Actions tab select the filter option Set to filter the child category selector. Step 4 (Optional): Configure the child category select Action to filter other tables(s) if applicable. Note: For the category selectors, it is best to name each item in the general tab under selector options, so you know which item to filter.   ... View more

The other thing to keep in mind also is the risk that you may end up loading far too many values that it could potentially cause editing issues. The issues could likely stem from having too many values that it may overwhelm your editors. The way we go about it is we simply have set domains for suffixes, prefixes, road types, and street names. By keeping the fields separate with their own unique domain lists keeps the dropdowns smaller and allows for additional updates without needing to update the entire address. This is something else to consider also. Then, if you wanted to, you could add another field to concatenate all the addressing fields into a single address. I rarely do anything with python now since finding out how useful arcade and attributes are at keeping the integrity of our data. If you want to go the python route then @RhettZufelt solution would be the way to go. ... View more

Hi @Crystal_Cowardin, So there are several ways to go about this but it depends on the type of feature (hosted vs reference). For hosted service using fields calculation: You can create a field calculation to automatically pull in the closest address point upon an update. For Enterprise FS: similar to the field map calculation, create an attribute rule that populates the closest address point. For Both you can use python to modify lookup values. This can be done by either populating a table of values and then running the table to domain tool or directly updating the domain codes and values. ... View more

Hi @offi24, Given the complexity of your question, the only things that I can recommend are as follows: Create a copy of the polyline and edit the copied line by dividing it into equal distances or parts Use/Create an attribute rule or arcade calculation to create points in another feature at set distances and then label those features. Add fields for starting kilometer distances and label them so that the labels are positioned along the line at set distances. Try linear referencing and seeing what tools may work best for you. Despite those I don't think you will be able to click anywhere on a line and get the distance along that line unless you use linear referencing.  ... View more

Hi @SaraJL, Another option you can try is: Dissolve the line features by a common field value to create a single line/multi-part feature. Create a point feature using the centroid of the line. Spatial join the point feature to the polygon. Join the spatial joined point back the line feature using the IDs of the line feature. This would be my recommendation but there are other ways to tackle this problem. ... View more

Seems like an expression issue on the server side. It is probably something that a recent update may have caused a java handeling error. The purpose of the $originalfeature is coded to look at the original record before any changes. For some of the codes it seems like it might be referencing a record that possibly doesnt exist on the first place. Its common in attribute rules to reference a nonexisting record. ... View more

Try taking ownership of the feature layer, with permission of course, create the view and then try giving ownership back and see if that works ... View more

Hi @DataOfficer, So the closest recommendation that I can offer is to create a new featureset from a data expression. This would give you something akin to creating a new featureset from existing data and is populated to your output. Here is an small example on how to construct a separate featureset as a datasource in Dashboards. var customfields = [ { 'name' : 'fieldsA' , 'type' : 'esriFieldTypeSmallInteger' }, { 'name' : 'fieldsB' , 'type' : 'esriFieldTypeDouble' }, { 'name' : 'fieldsC' , 'type' : 'esriFieldTypeString', Length:7 } ] var Values = { 'attributes': {} } var Geometry = '' var FS = FeatureSet(Text({ 'fields': customfields, 'geometryType':Geometry, 'features' : Values })) return FeatureSet() ... View more

Hi @mhaley_stone_env, Not me but a simple CoPilot answer. Yes, it is possible to create a view layer from a shared update content group, but there are some important considerations: Ownership Matters: Only the owner of the original hosted feature layer typically has the ability to create a view layer. Even if you are part of a shared update content group, you may not have the necessary permissions unless explicitly granted. Administrative Privileges: If you need to create a view layer and are not the owner, your organization's administrator can adjust your role or permissions. They can either: Assign you a custom role with the privilege to create view layers. Transfer ownership of the hosted feature layer to you. Shared Update Group Limitations: While shared update groups allow members to edit and manage content collaboratively, creating a view layer is often restricted to the item's owner unless specific permissions are configured. If you're encountering issues, you may need to contact your administrator to ensure your role includes the necessary privileges or to discuss transferring ownership of the layer. In regards to the answer above, I can say for certain that if you have administrative privileges or have the owner temporarily transfer ownership then it should be possible.  ... View more