Latest Contributions by DrewFlater

@Michael_VanHatten I have not been able to look at this case further to see if I can reproduce the problems when adding the Add Join step and using feature services. I am getting some help from a teammate to keep looking into this. I would say that tech support would be more able to give live troubleshooting help for an involved problem like this. The BUG you mentioned about was specifically about Select Layer By Attribute, and that error has been resolved in Pro 3.0 (confirmed by some other commenters in the other threads). Since you are encountering more problems, we want to understand and resolve them. Thank you for your patience and help to understand the problem.  ... View more

Also @Michael_VanHatten , I forgot to respond to your statements... 1. The error messages you indicate don't have anything to do with data lock. Data lock was the problem I described previously that was responsible for the error I pictured, but doesn't have anything to do with your case(s). 2. The capabilities of the feature services shouldn't impact this case. Yes to run Calculate Field you'll need the Edit capability like you mentioned. But the error messages indicate that the failure is before any calculation is even attempted, when the tool is adding a field to perform a calculation into. This might either be your choice or there is a bug causing the tool to interpret the field you chose as a new field, either due to the data source, the join, and/or both.  ... View more

@Michael_VanHatten  Regarding Facility Layer Inspection Update pictured error, this error is coming from the server side when using your data with the AddJoin tool. Can you confirm the model runs from within Pro? Do you have credentials to access those services saved for your account from within Pro? I can imagine a scenario where this error is raised because the external Python process that runs the scheduled model cannot gain access to those services, as it is a headless operation that does not prompt for credentials. When you add those services to a map, or when making a server or portal connection to access those items, make sure the option is checked to Save User/Password or "Sign in automatically" since those are the only ways to make sure the Python process can access secure data sources.  Regarding the other capture.png with Error 000852, this is an error that occurs when you have specified that Calculate Field should add a new field to perform the calculation into, in this case it looks like you have specified as the input field: "L1Facilities_View_2022_Score.condition_rating_2022". Is this intentional that the calculation should be into a new field? Or you got that field by selecting from the input field choice list? There might be a bug happening here with Calculate Field with a joined feature service causing this problem. I will test this scenario while you are responding.  ... View more

@Michael_VanHatten the model looks fine. Scheduled tools support any data format/location, but there are gotchas when working with remote data, covered here: https://pro.arcgis.com/en/pro-app/latest/help/analysis/geoprocessing/basics/schedule-geoprocessing-tools.htm#ESRI_SECTION1_ABC4323E12B04D0C90F07B16B3ABE894 If you can screenshot the error messages from the failed task run of your scheduled tool, it will help to know what tool or process is failing and why (like in my failed task that I pictured and described above, you can hover on that and pop-out the messages window to look at the detailed errors/warnings). ... View more

@Michael_VanHatten while I am not the employee who said in the forum your problem would be fixed in 3.0, I am the one that tested and verified BUG-000131693 is working in Pro 3.0.  Can you please give more details about the errors you are experiencing?  I just retested a scenario like what you described, using a ModelBuilder tool to select some features and calculate a field, run on a schedule. This is completing successfully for me, as long as I do not have the layer/table open in Pro, since that would cause a schema lock with the external scheduled process which is trying to update the data out in Python. You should also double check that if you are using a layer as input to the selection tool, that the project is saved with that layer, otherwise again the external process will not be able to locate what you want to use as input (there are warnings about this in the scheduling UI button, and in the documentation).  So here is what is working for me. I have a dataset, which has 10 or so STATENAME values. I want to select and calculate a field only for those with STATENAME=Wisconsin. So I perform the selection against the data path, then send the result to Calculate Field. The calculation I perform is some basic text, WI, plus a timestamp so I can definitely see that the calculation is being performed at the time that the scheduled process ran.      You can see in the History >Geoprocessing > Scheduled section I have one time that the scheduled process failed. That was for the schema lock that I mentioned before, as I had the data open in Pro, and it could not perform the calculation while the data is locked for use in Pro.  ... View more

This development was attempted, but caused problems with focus and drag and drop of other elements on a geoprocessing tool. Commands to move up and down are available by right clicking the handle for each value/row in the list, so drag and drop will not be attempted for now.  I reviewed the Extract Multi Values to Points tool in ArcMap, and the multi value control used on that tool also only supports use of up and down arrows to move items, there is no drag and drop.   ... View more

@JessicaIEMA  I have uploaded this as a geoprocessing sample https://www.arcgis.com/home/item.html?id=a8e491cfc8bb4e31a8726eae11c12a6c  ... View more

The Pro Charts team will be working on this enhancement in the near term. The work can be tracked through this tech support enhancement as well: ENH-000132130 ... View more

We have issues with drag and drop using multivalues, so for now there is no plan to implement this. As an alternative, just right-click on the field and you have options to move the items. Right-clicking is not so discoverable, but across the Pro app has a lot of useful and timesaving contextual features.    ... View more

Just want to mention this can currently be done as a two step process. It is likely Select By Attributes will remain a SQL query implementation only. But you can easily run Calculate Field using a Python expression to flag or create new values which can easily be queried. From the example of selecting records that have curves, do this: arcpy.management.CalculateField("YourLayer", "HasCurvesField", "!Shape.hasCurves!", "PYTHON3", '', "SHORT") arcpy.management.SelectLayerByAttribute("YourLayer", "NEW_SELECTION", "HasCurvesField = 1") ... View more

The enhancement will be integrated to the Generate Points Along Lines tool in ArcGIS Pro in the near term.  ... View more

Thank you for submitting this idea. It is under consideration by the Pro Charts development team. ... View more