Latest Contributions by TomBole

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

Hi Michael,  Thanks for adding to the thread.  We have many automated tests for ArcGIS Pro that import MXDs (of various versions) that contain graphics elements such as lines and rectangles. These tests all pass.  Debugging the issue points to the inclusion of properties for Z and M in the graphic elements in the Layout files provided by customers submitting the bug. We are highly confident that graphics created through the UI (ArcMap and Pro) provide a different property set and that the problematic graphics were created through code (such as through an add-in). At Pro 2.7 very low level geometry changes were that invalidated graphics with specific Z and M property values. Unfortunately, we do not have many test cases of graphics created by add-ins and missed the bug. Tom  ... View more

Hi Lindsay,  We are aware that this affects lines.  We believe that graphics created programmatically, probably using an add-in, are the problem.  Graphics created via the UI are not. That is why the re-create and copy/paste work-arounds succeed. Thanks for the communication! Tom ... View more

Hi Lindsay,  Looks like the search engine is not working.  Thanks for reporting the problem with search. This bug is currently being worked on. Hopefully we can get it out with the first service pack - but I cannot make any promises. @KoryKramer  -  This link brought up the correct result Monday. Today... basically useless.  https://support.esri.com/en/Search-Results#search?q=BUG-000136364 Who do we contact to look into this? Thanks,  Tom ... View more

Hi Marta,  I believe you can use the Save As Default command off the legend item context menu (circled in green on the screenshot below). By default, the Feature Display Options are not checked. Once you have checked either of these options (or made other legend item changes such font color) for a specific legend item (in the screenshot above I'm doing this with "World Cities") you then right-click this legend item in the Contents pane and click Save as Default. After this any new legend item added to THIS legend element, including new items added to the legend when switching the source data frame, will inherit the applicable properties of the legend item you set as the default.  For more information please see the help topic - Work with a legend item.  Note that this only works for the legend items within the legend. Currently, we do not have a way to save the properties of the legend itself.  There are some threads on the idea site that you may be interested. Default Legend Item Properties - https://community.esri.com/t5/arcgis-pro-ideas/default-legend-item-properties/idi-p/932758 ArcGIS Pro Legend Options - https://community.esri.com/t5/arcgis-pro-ideas/arcgis-pro-legend-options/idi-p/926445 Table frames should only show rows for visible features, if applicable (table frames based off of standalone tables cannot be filtered spatially, by default. Hope this helps,  Tom  ... View more

Hi Logan,  This thread is specifically about line graphics getting dropped in the exported file.  I see that you are having a separate issue with legends.  I can answer a few questions - however, I think if you want a back and forth a new legend-specific thread should be created. A new legend fitting type was added at 2.7 - Manual Columns. This type was added because we found that the the legend item option "New Column" created a number of difficult issues with a few of the Legend fitting strategies. Whenever we make changes to the legend we work hard to not change existing legends. Unfortunately, our test suite is but a sample of the vast number of possible legend combinations. It is possible that your "enlarged" legend is a bug. Not knowing the details of your legend (layers, size, properties, etc...) I can only guess.  You are welcome to log an issue with 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.  Please refer to https://pro.arcgis.com/en/pro-app/latest/help/layouts/layout-fitting-strategies.htm for more information. Thanks, Tom ... View more

HI Tanya,  You should be able to see the status of a bug on the support site - https://support.esri.com/en/Search-Results#search?q=BUG-000136364 Tom ... View more

All, Thanks to Sander and Steinþór for confirming that the crash (Issue 1) can be avoided by disabling Spell Checking and for confirming that disabling Spell Checking does not affect the inability to open a layout (Issue 2). Sander makes an interesting point that layouts WITHOUT text do open in 2.7. We are still trying to reproduce issue 2. Has anyone entered a bug with support specific to issue 2 - the inability to open the layout?  I would recommend all who can to contact support with data/steps/OS details (English vs non-English)/locale settings concerning this issue. GeoNet is not the forum to gather such information. Even if a bug is already entered, additional information is always helpful. Thanks,  Tom ... View more