Latest Contributions by DavidSolari

The result of Intersects is a feature set of all intersecting features, if you know there's only 1 intersecting feature you can use the First function to quickly grab a feature. You also have to grab a field from the feature for the comparison, and I think passing false for the geometry parameter in FeatureSetByName will cause problems. Therefore: var tap = First(Intersects(FilterBySubtypeCode(FeatureSetByName($datastore, "WaterLine", ["DIAMETER"], true), 2), $feature)); return tap.tapSize == $feature.FITTING_SIZE I haven't tested this but it should get you going in the right direction. ... View more

Handling date field out of the box would be great, but if not his is another good use case for this other idea for Arcade expressions in the map series options. Right now the workaround is to calculate some fields and use those to drive the map series, which is a pain to maintain if you're constantly tweaking or rerendering a layout. ... View more

This would be a handy Connect feature, but as a workaround you can make the label <span /> and it should render as blank without triggering a warning. ... View more

The query looks correct at first glance. Two things you can try: Wrap the CURRENT_DATE - 365 part in parenthesis to guarantee the order of operations. Check the dates going into that field, if they're null or malformed that could cause the query to fail. ... View more

It sounds like you want to use Survey123 to add and edit records in a related table to the hydrant points. This blog post can get you started on linking a survey form to an existing table. You will have to build the table yourself but as long as you pay attention to the field names and data types this should be fine. You can then use app links like I mentioned above to give Field Maps users a quick link to Survey123. ... View more

I'm unclear what your exact workflow is, but you can link to an existing survey form from a popup using an Arcade expression like this: "https://survey123.arcgis.app?itemID=<your survey item id here>&action=view&q:globalId=" + Lower(Mid($feature.GlobalID, 1, 36)) For more info on what types of URL parameters you can include check out the docs. You can either add this to the related table's pop-up or use some more arcade to find the most recent survey entry and link to that from the hydrants, lots of options to play around with. ... View more

The field names are greyed out in the field view which implies they're set to read-only at the database level. Try accessing the Fields pane through the feature class in the Catalog instead of the map and see if you can change it there. You might also want to check for calculation attribute rules that disable editing on those fields. If all else fails: back up the data, delete those two fields, add them again, overwrite the service and update the data. ... View more

Unless someone comes along with some really clever symbology tricks this isn't possible as the ArcGIS renderer can't distinguish between lines that intersect midspan vs lines that intersect at an endpoint. But if the data changes infrequently then you can do this: Run Feature Vertices to Points in BOTH_ENDS mode. If you don't have an Advanced license you'll need to dive into arcpy and write your own tool. Run Pairwise Intersect with an output type of POINT. Select the intersect output using the feature vertices to points output, then delete the selected features. You're now left with only true intersections. Replace all the data in an "Intersections" point feature service you created with this new data. The service can be added on top of the lines to clearly highlight the intersections. Optional: enable symbol layer drawing so the lines have nice joints. This won't work with every type of service. Kinda clunky but it clearly indicates the intersections for your user(s). ... View more

I haven't worked with custom basemaps in a while, but I think the layer has to be some sort of cached layer (vector tiles would work best in your case) and it has to be shared to your org's custom basemap gallery. Once you do that all layers added to that map should be projected on the fly to the basemap's coordinate system. You should also be able to pick that from the basemap gallery in Pro and any web maps you share should work. ... View more

I swapped out the toolbox parameter for a feature layer input and got it down to this 2-line reproduction: import arcpy arcpy.cartography.ConvertLabelsToGraphics( arcpy.mp.ArcGISProject("CURRENT").activeMap, 20000, 'SINGLE_LAYER', arcpy.GetParameterAsText(0), 'Graphics', 'MAXOF', 'GRAPHICS_LAYER_PER_FEATURE_LAYER', 'ONLY_PLACED', 'GroupGraphics' ) I get the same issue as you in Pro 3.4.0, no changes are made to the map. I think the next move is to contact your support team to see if they can replicate it, hopefully this leads to a bug fix or a workaround. ... View more

I'm not sure you can do that at the Workforce level but a calculation attribute rule can translate the GUIDs to the proper name provided the data you need for the lookup is present in the same EGDB before the data is ingested. If that isn't true or if you're using a hosted layer then you'd have to look into something like webhooks or a custom ETL process. ... View more

Answering off the top of my head: You can pick the starting number when you create the sequence. If you're using a sequence then assume each sequence pull will generate a new largest number, if you have to check the table every time to find the previous largest number then you'll run into performance issues, and at that point you don't need a sequence to bump a number up by 1 anyways. The Arcade Text function has a second parameter for number formatting that includes 0 padding. Non-null fields are always preferable for record IDs, just make sure it has a sensible default as fields with calculation rules are inserted in their initial state before the rule updates things Disallowing edits through the calculation rule is the safest move, otherwise it's trivial to break the identity. Worst case you can hop into the database and tweak an ID without ArcGIS. You should be able to pop a unique index on the field straight through Pro's Manage dialog. Worst case you add a non-unique index which will still be a big performance boost if you need to query by ID. No issues with relationship classes, I have a 1-m relationship where the parent uses unique IDs and there's been no issues on that front. There's no special consideration with sequences and deleting rows, just keep in mind it'll lead to fragmented IDs over time. One last tip: try adding a short prefix to the IDs like "DB" or "GIS" or something, that way if you need to work with IDs that come from other sources you don't have to worry about numeric collisions. ... View more

If you have access to the new "Timestamp Offset" field type give that a try, it should preserve some time zone info. If that doesn't work, see if you can set a more meaningful default time for the incoming dates, or add a field that checks what the data source is so you can compensate for the bad dates somehow (such as an Arcade expression that subs in a better time) ... View more