Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About JillHalchin
JillHalchin
Frequent Contributor
since
07-04-2014
11-07-2025
125
Posts created
167
Kudos given
3
Solutions
135
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(6 Idea Submissions)Latest Contributions by JillHalchin
|
POST
|
Dan, Are you saying that the tile layer must contain all levels, even though I only need a few of the higher ones for use in a small area? The whole idea of a basemap with only a few levels is that it saves credits, so I'd rather not have to use 0-19 when I need only 12-19. Is this just something that isn't supported yet?
... View more
03-30-2017
09:41 AM
|
0
|
11
|
1902
|
|
POST
|
I just spent a couple of hours fighting with field order in Pro 1.4.1. I’ve decided that it’s best to set up popups as much as possible in Pro before publishing to AGOL or Portal. Today map has lot of layers, so that was a lot of popups to check and fix. It isn’t possible to manually reorder the fields in the Popup setup window. So I tried to reorder them in the Fields View, but they won’t budge in v1.4. That worked with 1.3. Next I tested reordering in the Attributes Table. That worked and the order stayed, except for one problem. If I tried to move the first field (leftmost), crash. Other fields moved without problems. Once I had reordered in the Attributes and saved the project, the change was usually reflected in the Field view. Not always, but usually. On to the Popups. In the popup setup field list, the field order didn’t change sometimes. Sometimes the field order changed, but the popup itself still showed the wrong order. Rechecked the order in the Fields view and Attribute tables. All OK. I tried toggling random popup fields on and off to see if that would get Pro to refresh. I discovered that changes like that will “take” only if I return to the initial Popup setup view (top left arrow). That behavior is in the documentation, but certainly not intuitive. There should be a save/apply button. However, that trick didn’t help with the field order problem. After checking the popups of other layers and several Saves, I rechecked the reluctant popups. They were finally showing the way I wanted. I’m pretty sure that this isn’t a case of me suddenly doing something different that finally fixed the problems. It may be a problem with the popup configuration not refreshing quickly. But it cost me far too much time.
... View more
02-16-2017
08:24 AM
|
0
|
0
|
2512
|
|
POST
|
Katie, I thought that I had replied to you, but don't see it now, so I'll try again. Yes, I'm the owner. I don't know for certain about the role, but I think it's a standard publisher role. Jill
... View more
02-02-2017
06:21 AM
|
0
|
0
|
924
|
|
POST
|
A colleague and I are seeing problems with the Query Widget and we'd like to find out whether we're doing something wrong or if the widget needs to be fixed or enhanced. The behavior that we see will be confusing for the end users of the app. 1. Missing related records: When the widget is set up to query a table or layer that has a relationship, the Query Results includes the related table or layer at the bottom. However, clicking on the layer doesn't consistently provide the linked records. It's blank. Back up and try again and that produces the records. This may be a slow server response issue, but it's a problem, even with an test map that has only 5 features and an handful of related records. 2. Once you finally get the related features to show up, clicking on one of them will zoom the map, but the selected feature isn't highlighted. Most users would expect that to happen. Any suggestions, or is this just how the WAB is working now?
... View more
12-19-2016
08:25 AM
|
0
|
0
|
982
|
|
POST
|
The results with a file GDB were mixed, so I did some additional testing this morning. Originally, to get the data into the Pro default GDB, I exported from the map. But to put the data into a new FGDB, I used import. I also used import to put it into SDE. (By the way, I'm copying entire feature classes, not features to existing feature classes.) So, I wondered if the different results were due to export vs. import? This morning, I created a new FGDB. Then, in ArcCatalog, I exported from SDE to file GDB. When I publish from the new FGDB, everything shows up. Then I exported from the SDE to a different SDE. That publishes fine, too. Maybe there's something else uncontrolled that I'm overlooking, but for now I'd say that export and import aren't exactly reverse operations. I'll stick to export.
... View more
12-12-2016
06:52 AM
|
0
|
0
|
1430
|
|
POST
|
I'm having the same issue with two layers in a service, publishing through Pro from and SDE geodatabase. Other layers in the map from another SDE publish just fine. The problem is with AGOL. All features show up when publishing from the same map to Portal. After trying a new SDE and a FGDB, I finally resorted to exporting the errant layers to the GDB maintained by Pro for the project. That publishes correctly. Will be a pain to maintain because edits will have to be copied to the Pro GDB every time in order to keep the public app up to date.
... View more
12-07-2016
09:53 AM
|
0
|
2
|
1439
|
|
POST
|
I was glad to see that sharing information had been added to the newly revised Details Page, however, it doesn't work correctly. If the item is public, then the page shows "Shared with: Everyone (public)." However, items that are shared with groups show "Shared with: The item is not shared." Not useful.
... View more
10-17-2016
09:22 AM
|
0
|
4
|
1458
|
|
IDEA
|
Todd, As Melissa said, this is a bug with Portal 10.3 and 10.4 and probably AGOL. After talking with our agency specialist and Esri support, I found that the best workaround is to use ArcGIS Pro for publishing. Of course, Pro won't work with ArcGIS Server (hopefully that's coming.)
... View more
09-29-2016
07:46 AM
|
1
|
0
|
1516
|
|
POST
|
If you can get ArcGIS Pro, do it. It is 64-bit and was born to do web. It's still a toddler in many ways, awkward for day to day data managment and digitizing, but it can publish! Fast. Consistently. You can overwrite services that were published from ArcMap in many cases. The only caveat is a bug that I just ran into: if you keep hosted services in an AGOL folder with spaces in the folder name, overwriting will fail. So be sure that your folder names don't have spaces. Seriously, even if you don't to anything else with Pro, try it for publishing.
... View more
08-18-2016
06:28 AM
|
0
|
0
|
1250
|