Latest Contributions by Joshua-Young

I do agree that ArcGIS Enterprise is in need of some better QA/QC for both platform releases and patch releases, but Esri's release cadence is usually only two releases a year for ArcGIS Enterprise. The odd minor releases (11.3, 11.5, 12.1, etc.) are long term releases that are supported for a longer period of time if you do not want to upgrade more often. ... View more

FYI, the issue is caused by the attribute rule templates Generate ID and Symbol Rotation. Those rules use an Arcade function call FeatureInFilter that is causing the error only in ArcGIS Field Maps. The function should be supported in ArcGIS Pro 3.5+, ArcGIS Enterprise 11.5+, and Field Maps 25.2+. Esri has a bug number for the issue that is "Under Consideration". Current workarounds are to use map services instead of feature services if no editing or offline is required. Otherwise, those attribute rule templates need to be modified to not use the FeatureInFilter function. ... View more

The Map Image is being rendered on ArcGIS Server and an image is passed to the client. It supports all the symbology and labeling as the client that published the service. The Feature Service on the other hand has its data passed to the client and is downgraded to what the client supports. If you open the Feature Service in ArcGIS Pro it should look like the Map Image, but if you open the Feature Service in Map Viewer you are limited to what Map Viewer supports for symbology and labeling. Symbology in Map Viewer has come a long way and most of the time it will match what you would see in ArcGIS Pro. Labeling in Map Viewer is very simplistic compared to ArcGIS Pro, especially the Maplex Labeling engine. You will run into similar limitations viewing the Feature Service in other clients like ArcGIS Field Maps. Also, I noticed that you are on ArcGIS Pro 3.7 and ArcGIS Enterprise 12.0. The matching version of ArcGIS Pro for ArcGIS Enterprise 12.0 is ArcGIS Pro 3.6. I have run into odd issues when using a version of ArcGIS Pro that is higher than the matching version of ArcGIS Enterprise. If you can, you may want to try to republish the service using ArcGIS Pro 3.6 and see if the issue still happens. ... View more

With SQL Server the account hierarchy is the SQL Administrator account (can create databases), then the database owner account (can manage the database), and then user accounts (create, edit, or just view tables depending on permissions). Those can all be the same account but that is not the best practice. This is what I usually do in our environment using SDE schema. My admin Windows account is in the SQL admin group so it can create an enterprise geodatabase (EGDB). For simplicity, I use the Create Enterprise Geodatabase tool to create the EGDB and we use SDE owned schema instead of DBO. Create a database connection to the new EGDB using my admin Windows account (if the accounts already exists in SQL Server, I think this can just be the SDE account instead) Use the database connection in Step 2 to run the Create Database User to create an account to load the data into the EGDB. I use SQL Server Management Studio to create the "regular" user accounts and add them to the EGDB. These accounts can view or edit data but cannot modify or add feature classes or tables. You cannot use the Create Database User tool for this because it gives too many privileges. Create another database connection for the new EGDB using the data loading account Use the database connection in Step 5 to load data into the EGDB After the data is loaded into the EGDB, use the database connection in Step 5 to run the Change Privileges tool. The Change Privileges tool can process multiple feature classes and tables by default. If any of the users have the exact same privileges, you can run Change Privileges in batch mode with the User parameter as the batch parameter. You will have to run the Change Privileges tools each time different privileges are required for different users. Here is an example: John and Jane both view table 1 (Input Dataset: table 1; Users: John, Jane; View: Grant) John only views table 2 (Input Dataset: table 2; Users: John; View: Grant) Jane edits table 2 (Input Dataset: table 2; Users: Jane; View: Grant; Edit: Grant) Now your users can create database connections to the new EGDB and see what has been shared to them. This is probably a bit excessive, but I like having the separation of account duties for security and quality control. I am the only one that has access to the data loading account, and I only use that account to load and manage feature classes and tables. I do not use it for regular access or editing. ... View more

I agree with what has been said except un-sharing the archived user's content. ArcGIS Online and ArcGIS Enterprise need a separate way to archive items (Add the ability to archive items, AGO - Archive content). Archiving a user does not necessarily mean their content needs to be archived as well. Items that are not going to change could stay associated with the archived account and items that will need changes made could be transferred to a new owner with some kind of lineage of who the previous owner was. Really all that has been mentioned so far could be applied to the existing "Disabled" account classification.   ... View more

I hope that is not the case, but it is what it is. This is what I get when I try to view the bug on Esri Support. I know I will not be trying another upgrade off of 11.5 until at least a workaround, if not a patch, is posted. ... View more

Another example that comes to mind is the Special Event Operations solution from ArcGIS Solutions. We recently deployed this solution and in the solution there is one service, one map, and one app for people to edit what is happening with an event. After showing the solution to Fire, Parks, Police, and Public Works they pointed out that are different aspects that each department is responsible for and they were concerned with accidentally modifying some other departments edits. Currently, I will have to recreate the solution by making copies of the service, map, and app for each department so that each department can edit what they need to but still see what the other departments are doing for overall operational context. It would save so much time to be able to even at just the service level control edits and views for different groups and that propagates up through the map and app. Then I have just one service, map, and app to manage special event operations but different controls for the different groups accessing it. ... View more

Based on what I am seeing on Esri Community, I expect it is more of an issue with the ArcGIS Online update than the deployment of the solution. If you have not already done so, I would recommend opening a case with Esri Support for the issue so they can start working on a fix. ... View more

Did you deploy the solution to ArcGIS Online or ArcGIS Enterprise? I believe ArcGIS Online was updated just yesterday. Either way, I would try signing out and then delete the site cookie for ArcGIS Online or Enterprise and your browser cache. I have not seen those specific errors before, but it looks like something is either unavailable or is being looked for in the wrong location which old cookies or cache could cause. ... View more

@CordulaGöke in ArcGIS Pro 3.5.7 I just used model builder to select some points in a geopackage and ran the Calculate Field tool on that selection putting the results in a new field. The process was: Make Feature Layer - input was the point feature class in the geopackage Select Layer by Attribute Calculate Field - typed in a new field name to store the results I tried the Multi Values to Points tool but it would not let me use point feature class in a geopackage as the input. Doing so generated an error that the file was not supported. I tried to get around that by using Make Feature Layer first. The Multi Values to Points did run after that but failed with an error and the point feature class was deleted from the geopackage. I also tried Extract Values to Points but if I try to put the output in a geopackage it keeps appending ".shp" to the end of the output name and there is no way to remove it. Running the tool obviously generates an error. Running the Extract Values to Points tool with the input points coming from a geopackage and the results being stored in a file geodatabase works. I would recommend opening a support ticket for the Multi Values to Points and Extract Values to Points tools failing to output data to a geopackage. The Multi Values to Points tool overwrites the input points file, so if it is trying to save the new points as a shapefile inside a geopackage that would explain the table being deleted. ... View more