Latest Contributions by RPGIS

Hi @clt_cabq, So the groupby function returns a different featureset and that featureset doesn't include the geometry. To return a featureset with the geometry you'll need to configure it to match the example below.  var featfields = [{name:"A", alias:"alias", type:"esrifieldType"}] var attvalues = [{attributes: { "A" : "a" }, geometry: "the feature geometry or intersection of feature geometries"}] var egeometrytype =  "esrigeometryType[Polygon,Point,Polyline,etc.."] var fs = { "fields": featfields, "geometry":egeometrytype, "values":attvalues } return Text(Featureset(fs)) ... View more

Hi @clt_cabq, Is your data able to be filters correctly based on the list. If it is able to filter but not zoom then one thing you can try is to create a new featureset in the data expression and use that to filter. ... View more

Hi @CodyPatterson, Try these options: Close out of pro and reopen your project. Sometimes pro will randomly put locks on features for reasons unknown and that will impact some workflows. Try publishing a new service and see if the copy allows for changes. If the copy allows for changes then it might have something to do with the service definition which will require it to be overwritten. Try making a complete copy of the data and see if publishing it works. if that works then it might indicate that the service is probably corrupted. ... View more

Hi @clt_cabq, What map actions have you set on the list. If you set it to filter by the same field and also set it to zoom in then it should zoom in. There could be the possibility that there could be an error in one of the addresses which might also affect the filter and zoom. ... View more

Hi @DeanAnderson2, The workflow you are showcasing is a bit odd. Not saying that it is a bad workflow but it seems like you are updating a table with an ID to only delete the same ID. Is the ID of any value or what is the ultimate reason for updating the table of retired IDs? ... View more

Hi @KatieQuantrell, Have you tried looking into the data expressions for Dashboards. With the data expressions you can create features from other features, like the featuresetbyportalitem. In addition to that, regarding the description vs the code, then you are correct about using the DomainName to get the actual description rather than the code for a domain. var DayFields = ['Sunday','Monday','Tuesday','Wednesday','Thursday','Friday','Saturday'] var infoFields = [] for( var d in DayFields ){ Push( infoFields, { 'name' : DayFields[d] , 'type' : 'esriFieldTypeString' , length: 6 } ) } var D = DateAdd( Today() , -Weekday(Today()) , 'days' ) var Values = {} for( var i in DayFields ){ Values[ DayFields[ i ] ] = Text( D , 'MMM D' ) D = DateAdd( D , 1 , 'days' ) } /* for multiple values in the feature modify the example below var ListofValues = [] for( var i in ListofValues ){ Push( ListofValues, { attributes: {'A':a, 'B':b, 'C',c },geometry: {shape} } ) } var MultipleRecords = FeatureSet(Text({ 'fields': Fieldlist, 'geometryType': 'Polygon', 'features' : ListofValues })) */ var DOW = FeatureSet(Text({ 'fields': infoFields, 'geometryType':'', 'features' : [{'attributes': Values }] })) return DOW You can also modify the code above to have the geometry of either all features or ones that only match the values. Just be mindful that if you want the geometry that pertains to all of the unique values then you will need to merge all of the geometries but if you want the unique geometries then you will need to append multiple records for the new feature. ... View more

With that information it makes it easier to help you get to what your after. So there are a couple of ways to go about it.  Modify the code to only update the table when a field is changed to whatever value to indicate which parcel is deprecated to trigger the update to the table and then merge the two layers afterward. Modifying the same code above but set it to filter the featureset( $featureset ). If the count for the filtered result is zero then set to update using the original ID and whichever values you specify.  ... View more

Hi @DeanAnderson2, A couple of things. You have a missing double quotes in the feature class name but here is a more simplified version of your code. Please use the    when adding code so it makes is easier for others to see what your code is supposed to look like.   var Taxlot = $feature.MapTaxlot var fsTaxlot = FeatureSetByName($datastore, "Taxlot", ['MapTaxlot','RetiredByRecord','CreatedByRecord'],false) var where = Concatenate(["MapTaxlot = @Taxlot AND RetiredByRecord is Null"]) var fsTaxlotFilter = First(filter(fsTaxlot,where)) if (TypeOf(fsTaxlotFilter) == 'Feature'){ return { "edit": [{ "className": "CancelledNumbers", "adds": [{ 'attributes': { "Taxlot": $feature.Taxlot, "MapNumber":$feature.MapNumber } }] }] } }   ... View more

Hi @marksm_macomb, I am assuming that the feature services are the same geometry/feature type, in which case you can try the following. Creating a new blank feature Publish a new feature service schema of the other feature services or at least one that can be appended to with a schema that will work for all fields. Append the data from all features to the new feature. Create an attribute rule/python script to automatically make updates to this feature service whenever the other feature services are updated (Optional) Schedule a geoprocessing tool Run a geoprocessing tool that will combine all of the layers into a single service. Publish the results as a service Schedule a geoprocessing tool to truncate and append the records to the feature service. Filter and publish the feature service as its own service Bring all of the layers into a single map, apply any filters deemed necessary Publish the layers as a service which will ultimately group them accordingly There is some additional information that is missing but I am assuming that these services are hosted. If not, then the other options should work but these options should work for most, if not all, for what you are trying to achieve. ... View more

Hi @AllieAnn3, One thing I would suggest trying is the following. var FieldMap = {Address:'Address','<IncomeField>':'Ave Household Income','etc...':'etc...'} var Values = [] Expects( $feature, '*') for( var f in $feature ){ var N = $feature[f] if( HasKey( FieldMap, f ) && !IsEmpty( N ){ if( F == ''){ N = Text( N, '##.##%' )} //else if..... Push( Values, Dictionary( FieldMap[f] , N ) ) } } return Concatenate( Values, '\n' ) /* Note: Any value in text that you want to represent as a placeholder for a number can use '#' to indicate the position or how many digits of the number to represent. Whole numbers use '0' as representation. You can add any other characters to the front or back to show percentages or any other value. */ I use code similar to this for more complex popups just to keep things simple. The 'Expects' may not work so you can optionally create a dictionary of matching fields and values to mimic something akin to this. ... View more

Thanks Amanda. ... View more

Just out of curiosity, what is the overall direction for esri regarding web editing capabilities? For as long as I can remember, web editing started out: The classic web map, Geoform, and a couple of others which I can vaguely remember.  Web App Builder, when it came out, has( or had) the editing widget which made it easier to configure editing using a simple web app like UI Map Viewer replaced by the classic web map by which Web App Builder had support and enabled editing Experience Builder is replacing Web App Builder and allows for web editing using a similar UI to Web App Builder. Floor Plan Editor for Enterprise Portal (11.2 - Current) also enables web editing.   So I just a few questions. Is the purpose of this new web app designed to be a friendlier UI in terms of editing in the web, and what would the potential road map look like considering it could potentially replace several other web maps that also have editing capabilities? Will arcade be supported by this new web app or will that capability exist only in field maps or as attribute rules? ... View more

Great. If it is alright with you I will go ahead and mark my response as the solution. ... View more

Hi @Amanda__Huber, Were you able to get this resolved. I am simply checking because it has been a while and I just wanted to follow up. ... View more

HI @EthanGibbens, If you want only specific fields to show from another table then a join makes the most sense. Relates only correlates one field to another field based on matching values. If you want the join table to join to each matching record but only include specific fields then you can try the following. Export and join option Try exporting the table to only have the fields that you want plus the join field Create the join and it should only have the fields you exported shown. Join then toggle fields Join both tables Click on the feature and select the "data" tab in the ribbon. In the data tab click on fields. Toggle the fields you only want to show/export (Optional) Export the joined table as a table of matching results.   ... View more