Latest Contributions by DavidColey

Thanks for the reply @ShanaBritt  Yes sadly, I thought I had recreated 2 of 3 locators but in fact 2 were still 10.x (*.loc, *.loc.xml, *.lox). After re-creating the locators as 2.9 (*.loc, *.loz) style locators in the same file location and with the same name, the project at 3.0 will open without the 'Invalid Locator' message. However, even after removing the updated file-based locators from the 3.0 project, upon a locator 'refresh' from the catalog pane, the file-based locators are re-added to the project, suggesting to me they are never actually removed from the aprx.  As you note, they would have had to have been removed at 2.9.  Maybe a 3.1 patch will fix this.  For me, I am using this as an opportunity to re-create new, clean 3.0 pro projects in a new directory location and then migrating data, folders, styles, etc.  I am isolating my pro project used to create my address locators in an entirely separate location (separate from the home location). - hopefully this will keep  things cleaner. ... View more

Hi @ShanaBritt  - I can confirm this is still an issue at 3.  Here's a post I put up yesterday: https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-3-0-won-t-remove-locators-from-project/m-p/1199409#M58176 It does turn out I do have 2 10.x address locator services being referenced in the project and I am working to delete those from enterprise and server.  We'll see how it goes.  @JoeBorgione  @EricAnderson17  ... View more

update Our EIT security disabled github access for administrative accounts.  since I always work using my admin account, the client install could not access any of the node_modules.  switching to a non-admin account and re-running the client npm ci then did complete it's install, albeit with the same visual studio dependency errors.... ... View more

So I know this is frustrating bringing this back up, but at version 1.9 client install problems still exist.  For me, the entire /client/node_modules directory did not install with the npm ci, as with version 1.8. I am copying my node_modules directory from my 1.7 install.  Then we'll see what fails I suppose. @esride-nik  @RobertScheitlin__GISP  @babarsac    ... View more

Thank you for this @ChristopherPawlyszyn  - I had thought I had seen this documentation but some missed it again.... ... View more

I believe I read in the documentation from a few releases ago that 16 map pages was a limit....  - David ... View more

Hello @Anonymous User  - I realize this topic is a bit dated, but when you say "we are a few weeks away from releasing a draft publishing flow in Hub Sites" - can you direct me to that resource?  I can't seem to locate a "draft publishing flow" such that I too can clone our site without having to configure a new core team and content groups.   We send a lot of data to our site via distributed collaborations and this will be a real time saver. @ChaseBarnard  Thanks, David ... View more

Thank you for the feedback @ShengdiZhang . Sorry for the late reply on this. Yes, I am able to return the same popup info result into a feature info widget from a feature layer source within the same map.  I believe what I was missing was the Search action trigger for 'Data Filtering Changes' so I can zoom and pan to the feature in my map.  This works fine for a single-source feature layer and a single feature info widget to hold the results. Still, I suppose what I am asking is the capability or flexibility for the Search to interact with the webmap popup.  In this way, more feature layer sources can be added to the Search without having to define separate Feature Info widgets as containers to hold the popup info results.  Much like the current Web Application Builder does now.   ... View more

Thanks for the reply @TonghuiMing . Yes for me this issue still exists.  My eb is using a list widget and feature info widget with a hosted feature layer that contains 2464 polygons (a zoning layer).  My published version is here: https://experience.arcgis.com/experience/4a523b8a772b48af921d793b6b9c9563/page/Zoning/ and is working as expected. That is, the list, feature info, and map popup info all display the same information when clicked or selected, or sorted and selected etc. Unfortunately, when I went in to the eb to explore some different filtering on this map, something became corrupted and I cannot duplicate the behavior.  The following details may or may not help: For the list widget, the Default source is set to sort on object ID by default because the map layer sorts on ObjectID by default.  I am using then using an additional sort-by-type option so the users can sort the list. For the feature info widget, I tried setting up a view to sort to use the same sort-by-type sort as the list widget.  That way, the list selection and feature info selection remain in sync when a user selects an item from the list, or pages through a feature info item. But now, the problem is that I cannot re-build this behavior in the configuration editor.  When I click the map, the popup displays the correct info and the list displays the correct item, but the feature info displays a random selection, because it is using a view as its source and not the same 'Default' source that the map and list are using. Other than setting the Feature Info to display the 'Selected' and not the Default seems to be the only way I can all three to display the same info correctly.  I suspect this behavior is so tricky because I am working with more than 2000 records.  I am not experiencing the same difficulty on pages (maps) in the experience that use less records.    ... View more

I think something is going on with the Online EB configuration environment or with Online itself.  I too have been having trouble with my list widgets and interactions with a feature Info widget that I normally don't see.   ... View more

Yes it does, thanks Derek ... View more