Latest Contributions by TomBole

Hello GISTeam4,  I believe you are running into BUG-000136770 REGRESSION - A Page Query on a stand alone table stopped working. We are hoping to have a fix for this out soon. You can use the link to track the progress of the bug/fix by clicking the link.  You can also search for support issues from this site - https://support.esri.com/en/Search. Hope this helps,  Tom ... View more

Thanks Lindsay. I can reproduce the issue you describe and have created an internal issue. Once the the support issue gets to the development queue I'll link the two. Having a support issue helps us prioritize our bug fixes. Thanks for taking the time to do this. Tom ... View more

Hi Jessica,  For layer symbols with offsets try increasing the legend item patch size to accommodate the symbol offset.  Column management has been a bit tricky with legends, especially the algorithms used to flow items across columns, and it is not the most intuitive experience for many.  You are not doing anything wrong. If you want more control over the columns try using the "Adjust font size" strategy.  At version 2.7 we have cleaned this up a bit with the introduction of the "Manual Columns" fitting strategy and other changes that hopefully will make working with Pro legends easier. The following topic may provide more info that you might be interested in - Tips and Tricks for Working with Legends in ArcGIS Pro. Hope this helps, Tom ... View more

Hi Lindsay,  This may be a bug.  What version of Pro are you using?  Did this work in a previous version? Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support. Tom   ... View more

Hi Sander, Thanks for the good news on ArcGIS Pro 2.7.1!  This was a very tricky issue.  Your help was vital. Tom ... View more

Thanks for the screenshot and bringing this issue to our attention!  I'm able to reproduce this and will enter an internal bug and hopefully we can address this with the next release (2.8). Tom ... View more

Hi Alexander,  You may be running into a bug specific to attribute property connections. I'm not aware of any Layout Legend issues with attribute property connections.   Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support. Thanks,  Tom ... View more

Hi Huanglei,  Sorry that you are running into this serious issue. As Steinþór states one possible solution "... is to add English  to the Preferred languages in Windows Language settings."  However, based on Steinþór"s experience it may not work in all cases. This has been an exceedingly difficult bug to reproduce - unfortunately we do not have test environments that replicate all possible OS configurations. We are working hard to fully understand what went wrong so we can address this in our testing so we can catch issues like this before the software is released. In situations like this it is vital that we get information from people experiencing the problem. We believe we have fix and hope to have it out with the next service patch. However, it is hard to validate a fix if you could not reproduce the problem in the first place. This is extremely frustrating for everyone!   The more information Technical support and the development team get the better we'll understand the problem and the better the fix will be. If possible please contact Support. They can be contacted at https://support.esri.com/en/contact-tech-support. The issue is BUG-000136460.  If you have already contacted them - thanks! Tom ... View more

Hi Vinestone,  Unfortunately, there is is nothing currently in the UI that would allows a multiline label. I think Robert (thanks, Robert!) provided the best workaround outside of using python to create your own legend.  Tom ... View more

Hi Kit,  My name is Tom Bole. I'm a Product Engineer on the Layout team. I'm one of those responsible for testing this area of the software. I'm also a big fan of sarcasm. Ask anyone who knows or works with me. I appreciate the frustration over this issue. I'll use my sarcastic voice here - "Whose the genius that made all the lines disappear?! When did Penn & Teller start working for esri development? What do they put in the water in Redlands? Dumb-juice? What an evil set of bozos!!!"  That felt good. Now that I've gotten that out of my system... The key here is not all linework is dropped. Only specific graphics are being dropped. Unfortunately, we did not have any examples in our testing harness. The issue was also not discovered through the beta program where we catch some of the oversights by the testing team (that's me and I'd be glad to go over the dumb mistakes and assumptions I've made over the last 20 years). This was an unknown bug that went out with the release. It happens. We're not omniscient. Once customers posted the issue on GeoNet and brought to our attention we thought, and I'll paraphrase, "How the heck did we miss this?" Something so basic. We checked our tests. All good. The linework appears in all the supported output types.  These lines were created in various versions of Pro and also imported from various versions of ArcMap. What's going on?  We second guessed ourselves and wracked our collective brains trying to get a repro case - much of it over the holidays - to no avail. Then one day we got lucky with a ArcMap file a customer sent to us for a different issue. Lines dropped from the exported file. One of our developers could now reproduce the bug and inspect the code. Seems a change was made deep in the code that had an unintended consequence for specific geometries on a layout.  Unintended consequences of changes in the code. That's what bugs are. They are not something we plan out on a white board or present as bulleted items in a PowerPoint presentation. They are things we have to find, though our automated testing, through manual testing within the team, through functional and  holistic testing, and through testing by people outside the team (to get a view from outside the "bubble"). We do not find everything. Sometimes we miss something big like this. But this issue is on our radar now, its a priority, and we are working on it. Tom   ... View more

Hi Marie,  Your description of the issue sounds like there may be a Page Query set on your lot layer. For example, in the screenshot below I have a map series based on the layer U.S. States (Generalized). There is also a Map Series Page Filter (Page Query) set on this layer. Notice that in the map view only 1 state is shown. This is expected behavior since the Page Query is a layer property and the current state of this property (set by the current page of the map series) is set for any instance of this layer.  If you wish to see all the features of the index layer you will need to either remove the Page Query from the index layer or create a separate layer (a copy of the index without the Page Query). All this is assuming that you have set a Page Query. I'm a bit concerned with your comment "Since I uploaded arcgis pro 2.7.0, I have this issue".  Does that mean that you were seeing different behavior in a previous release? If that is the case more investigation is warranted.  Can you contact Esri Support? They are better equipped to handle troubleshooting steps and gather bug data. They can be contacted at https://support.esri.com/en/contact-tech-support. Hope this helps, Tom ... View more