Latest Contributions by DavidSolari

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

Hit up the Web Editor Ideas Page and add this as an idea, this seems like the sort of feature that the Web Editor team can easily add to the app. ... View more

This is a common issue for my org when we have to tweak long-running services. We have to assess which services touch the required datasets, stop them, make the updates and start them back up, only to then interrupt the services again for republishing jobs; it's a bit much at times. Disabling the schema lock on the services causes more problems than it solves as it's trivial to create fatal differences between the new schema and the old service definition. Leigh's idea of a one-click option to enable DDL operations would save a ton of headaches as we could flip the switch, make our changes and then republish the services (if needed) with minimal interruptions before flipping it back. Making this an official ArcGIS thing that the server can inspect and make adjustments for is far more elegant than relying on service stoppages or arbitrary lock breaking. ... View more

You can try using an array of objects for your statistics, that way you can include the iconPath field. But I don't know if there's a statistics mode that will work for strings. An alternative is to use Distinct to get a list of unique iconPaths with the corresponding RecType, then you can turn that into a dictionary and grab the iconPath as you build the final table. ... View more

This is a longstanding design quirk of ArcGIS workflows: if your data is too heavily normalized there's rarely a good way for users to edit it without diving in and out of endless popup chains. The best workaround my org's found is to store assets as a single feature class per type (or use subtypes if you have a bunch of similar types) then use Arcade expressions in the feature pop-ups to generate links to Survey123 which wrap around the other tables. By passing a unique ID for the asset (the GlobalID is a good choice) through the URL the new survey now has a link back to the asset. You can then let users work with a reasonably normalized table set by using repeats in the survey. Glue everything together with relationship classes and you've got something! You do have to train users to jump between both apps, there'll be some limitations viewing new data if they're offline, and you might still have limitations viewing attachments in Field Maps but it's about as good as you'll get for field work. If your org has some money burning a hole in their pocket you can use the JavaScript SDK to build custom web apps that can handle fancier data structures but if you want the built-in stuff you'll hit these limits often. ... View more

Another way to chain two scripts together is to write two script tools, then chain them together in Modelbuilder. ArcGIS does some checks and cleanup between tools so that might be enough to fix your bug. ... View more

Joins can't transform the data during the join process so you'll have to create another field on one side of the join and then populate it with the right format. ... View more

Is this different from what Jackson did in their listing? ... View more

I tried your code with a cut down expression in 3.4 and it worked on my test data. Try a simpler expression and then slowly build it up until you find the subexpression that breaks it. ... View more

Have you tried building a Field Map link? ... View more