Latest Contributions by BrianFausel

This might be a bug that was introduced in the 9/29 AGOL update: We weren't having problems earlier this week and we started seeing issues yesterday. I am curious if anyone else encounters this problem. Our workflow is uploading various Excel files to become a hosted feature layer or tables. We have a dashboard where users upload daily Excel files that come from an outside source. I'm not sure if data formats beyond Excel have the same problem. These Excel tables that have less-than-ideal attribute column header names that start with "bad" characters: some start with leading space, some with _ and some with numbers 0-9. Generally not good database design. Prior to 9/29 these uploaded fine and worked with the web maps and apps. If there was a space AGOL automatically added an underscore to the hosted feature layer name. All other ones did not give us errors. Starting today, AGOL is automatically adding an "F" character before these characters. This causes the web maps and apps to break because they can no longer find the original column names. We decided to change our column names prior to publication to remove the spaces and numbers and have adjusted our apps. But I can see the leading number example being a particular problem for some users. Also, it is possible there are other bad characters that will cause this problem. Attached are 2 picture examples of the column names with the added "F" in our REST services. Note that the "F" is not added to the alias, only the column name. ... View more

Hello everyone, I have a distributed collaboration scenario and I want to make sure that I am on the right track in understanding the limitations correctly. Question 1: It appears to me that when you have a feature layer that is published for collaboration you can only enable editing on the side where you initially publish it. Is that correct? So if you publish to ArcGIS Enterprise, you enable editing there and cannot enable editing in AGOL, and vice-versa. Question 2: Is it true that you cannot have a “hosted” feature layer in AGOL sync to a “user managed” ArcGIS Enterprise feature service with data residing in SQL? You can only sync to an “ArcGIS managed” feature layer in Portal? Details My preferred workflow will not work for what I am trying to accomplish: Publish a “user-managed” feature service with data referenced in a SQL geodatabase into a federated ArcGIS Enterprise Portal. Using distributed collaboration, have that data sync to a “hosted” feature layer on AGOL. My editing requirements are one-way, but I want the editing to be done on the destination “hosted” feature layer in AGOL, not on the initially-published Enterprise SQL feature service. When I set this up, the data synched from Enterprise to AGOL, but then I was not able to enable editing on the “hosted” feature layer in AGOL. The only thing I could do is disable editing in Enterprise. Alternate workflow: Publish a “hosted” feature layer directly to AGOL and enable editing. Using distributed collaboration, have that data sync to a “user-managed” feature service with data referenced in SQL. This feature service does not need to have editing enabled, it can be read-only. The Esri distributed collaboration Q&A suggests this workflow is not possible. Question: Can I copy data from ArcGIS Online into my enterprise geodatabase? Answer: No. Destination layers within a collaboration must be hosted layers from ArcGIS Online or ArcGIS Enterprise. As I understand that answer: the sync must be to an “ArcGIS managed” hosted feature layer in Portal. It cannot be a “user managed” feature service with data in SQL. Software used: ArcGIS Online, ArcGIS Pro and ArcGIS Enterprise 10.7.1. I would greatly appreciate any feedback! Hilary Curtis‌ ... View more