Latest Contributions by EricPescatore

Good Afternoon Nick, interesting that 2 years later I have also encountered a scenario where the "Default" editing tracking fields created by Geoprocessing Function and AGO have cause a project additional care to resolve the mismatched naming conventions.  While there is currently an NIM098898 "The editor tracking fields for hosted feature services should be named the same as those for editor tracking in a geodatabase."   that is currently Review and NOT in the Product plan. (This is by Design).  I don't believe this accurately describes the proposed "standardization" scenario outlined. A Editing tracking field created in a Geoprocessing Toolbox, Those created now (w/o a geoprocessing) within ArcPro and the names created in AGO are different.   PRO (enable editing tracking)  created_user (255 length) created_date last_edit_user (255 length) last_edit_date   AGO (track the last edited) CreationDate Creator (128 length) EditDate Editor (128 length) Futhermore the two platforms flip the Field order creation (In Pro CREATOR then DATE, in AGO its DATE then USER).  We understand that the Tracking fields should not be held to a specific name, but if default values are generated those should be consistent between the various platforms. Until AGO will allow for the easy reconfiguration of the TRACKING FIELDS used, the need for standardization of default values should be done. ... View more

ESRI support has associated my case with an already Existing BUG-000129250. It is in the current product plan according to ESRI to get fixed (I hope that means next Beta release of pro?). As for the inconsistent FIELD naming convention will likely be logged as an ENHANCEMENT reuqest. ... View more

Agreed the accountability insures that a Case, Bug or enhancement request is logged. Typically through geonet even though we have interaction with ESRI staff, its not 100% guarantee that an issue documented will make it into their list of bugs. It also another way for customers to ensure their voices are heard. As for my other comment about the inconcistancy in Editing Tracking field names. This would also be something to bring to the attention of ESRI via a case as a requested feature enhancement. Though you could bring it up on the idea board, its very important to cross pollinate your ideas to ESRI.  ... View more

You are correct there the Preserve Editing tracking currently does not work in my testing publishing from pro and viewing in AGO. All of the edit/create dates are changed to the date/user who published the data. This is currently a critical bug. Additionally ArcGIS Pro and AGO are inconsistent in their default fields for editing tracking PRO (enable editing tracking)  created_user (255 length) created_date last_edit_user (255 length) last_edit_date AGO (track the last edited) CreationDate Creator (128 length) EditDate Editor (128 length) To add salt to the wound, it also flips the field order around for those with OCD. (Date first, then user in AGO, user then date in arcpro) If you haven't already i would recommend opening a case with ESRI to report the bug. I'm doing so now. ... View more

If it is a duplicate could you provide the CASE Reference or Enhancement Request Number so i can escalate it from my ESRI Support. As I do currently have an request to push this as an Enhancement.  It looks as though the original Request is in the Product Plan and targeting a ArcPro 2.7 for the release. Note that we are on ArcPro 2.5.1 for reference.  ... View more

Correct i think its essentially talking about the same function of being able to define the symbology except from a Polygon vs Point perspective. The original request from 2018 should at the very least cover both the original request highlighting Symbology for Polygons and Points and Lines. Though what is currently being displayed with point features is a little different than a Polygon Fill pattern. So the request would need to make sure to Cover both Point, Line and Polygons. As the "Selection" setting in ArcMap does understand what geometry the Settings are looking at. We would need to have this option to set the Symbology for each geometry type We should also add a toggle for "override" with custom selection symbology. As I do really think its cute that the selection for point, line and poly are essentially filling in the symbology space and not exceeding its limits. ... View more

I am taken aback that 2 years later this hasn't gotten any traction. The alternatives using terrible export tables of the attachment data then doing a JOIN in map to display "locations' with attachment just doesn't cut it. Bonus round: Add the ability to at least SORT the COLUMN. SUPER BONUS: Give us the full attachment table visible in WebMap/App/DataPage and inside the "services". ... View more

I've noticed a few loopholes on the Survey Update notification and there are quite a few scenarios where a user will never see the message and will continue to submit records with an outdated form. This has caused a problem for my 20 field workers and subs who don't regularly check for updates and utilize the Collector > Survey123 relationship. They also do not "close" or kill Survey123 to revisit the "My survey" page. We have to resort to using Version Check command to pass a "version # in Collector/Explorer/Webapp to the Survey e.g. 1 = 1 to display a relevant question telling the user their form is out of date. Here are a few examples of this that i could find. This is not all inclusive and is just quick notes   When a user is already in the Form and creates a new Survey. They will never see the Your form is out of date message. They need to "hit back" and see the My Surveys page on the device for it to do the "Search" and see that there is an update. If the user is in the form "Details page" were the outbox, sent, drafts etc" the page will not prompt a user to update the form. If the user is Opening Survey123 from outside the application using a Custom URL link Collector/Web map. it will not prompt the user to update the form. it will directly initialize the form before the "form version" is checked. Typically after submitting a record when Survey123 was not currently active in the iOS aka not loaded in memory. it bumps back out to the main Select a survey page because it doesn't remember what form it was in. if the user was already on the form page and clicks Collect, then initializes the form from outside of Survey123 (collector/weblink) it will prompt the user to open the page.  If the user clicks to quickly when Survey123 opens up the Check will not be performed and they will continue to collect using outdated forms. This is that brief period of time where Survey123 is authenticating to either AGOL or Enterprise login. Since a user is able to continue to collect data w/o being signed in or having internet. There is a brief 1 to 2 second delay before it begins the search. Clicking Continued without Update, doesn't remind the user again that their form is out of date unless a specific scenario above is triggered or they go back to the main page. This isn't necessarily bad but could be if prolonged use of Survey123 app. Its my assumption that the Form Notification Search only occurs on the "My Survey" page or if the application is closed and reopened. Many of the loopholes can be solved by simply "closing" and reopening the application on the iOS. But there still the chance a user can by-pass before the login is complete. There is of course having our field crews just actively go to the DOWNLOAD FORMS page every day and hit refresh... but thats never going to happen This testing was done on an iPhone 11 Pro Max iOS  13.4.1 using Survey for iOS Version 3.9.148, using both AGOL and ArcGIS Portal published data and accounts. I have opened a case with ESRI Support here 02555878 Case number. If others who like to request bug/enhancements please submit your own, you could reference the case above. ... View more

Alas nothing at the moment, in fact i just noticed i don't have it is a Bug/Enhancement request inside my organization MYESRI. So I guess I will need to put it on the war path. Also be weary of using WATERMARKS using Survey123. They resample the image and downgrade their overall quality to be that similar to a thumbnail or the resolution of the image on the device its taken. Not the resolution of the photo.  Watermarks create low quality attached imagery in Survey123  ... View more

Thanks when I can find some time I'll travel to the Ideas page and write something up. I will also put it in as an enhancement request tied to our ESRI Customer number etc. ... View more

Thanks I will open a Bug report now to document it. I do remember hearing about this EXIF data a few years back, it just hasn't come up till now with me thumbing around camera settings. ... View more