Latest Contributions by TomBole

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

All,  There are 2 current 2.7 Layout issues that I would like to update everyone on. Issue 1: Pro Crashes We believe this issue has to do with a combination of non-English OS and Spell checking enabled. We also believe that a possible work-around is to disable Spell checking. Here is the relevant help topic - https://pro.arcgis.com/en/pro-app/latest/get-started/proofing-options.htm. Though we are still working on getting a dependable reproducible case, and need one to validate any fix, we are fairly confident based on the crash dump information that the work-around can help. This also covered in the following thread: https://community.esri.com/t5/arcgis-pro-questions/pro-crashes-after-adding-text-to-layout-and-annoying-amp-quot/m-p/1013116#M35586 Issue 2: Failure to open Layout View The following message appears when opening a layout view. We are trying to get a reproducible case to investigate this further. It may be related to Spell Check and for those running into this issue it may be worth it to disable Spell Checking.  As we have been unable to reproduce the issue we cannot confirm the work-around.  Please let us know if this works or does not work. Hopefully this new information can help some of you get around this issue until we have a fix. Thanks to all of you that have submitted crash dumps - it has really helped us get started on a fix. I'd also like to thank those of you who have logged an issue with Support. Being able to reproduce an issue is the most important thing to understanding the issue and engineering the proper fix. Thanks for your patience. Tom ... View more

All We are very interested in identifying the issue regarding the inability to open layout or table views when on Windows 10. We are currently unable to find consistent reproducible steps/data in which developers can track down the issue and offer a solution. Anyone running into this issue, please contact 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. Once you log an issue with support please add the case number to this thread. Thanks for your help, Tom ... View more

Hi Tim,  I believe the issue you seeing is the same as those reported at https://community.esri.com/t5/arcgis-pro-questions/exported-map-missing-lines-version-pro-v2-7/td-p/1011329 There has been a bug logged with Esri support - BUG-000136364.  This is a high priority item that we are currently investigating.  Tom   ... View more

Hi Christian,  Thanks for the screenshot and the layer file.  This is a legend patch scaling BUG SPECIFIC to how the layer is symbolized and not a general issue with this functionality as was addressed with BUG-000132025.  You have highlighted a different symbol configuration that the fix to does not address. ArcMap is handling this particular symbology in the allotted legend item patch space more accurately than ArcGIS Pro. As you stated earlier the likely issue is with the shape marker set along the outline. I'll enter an issue, however, at the same time, I suggest that you enter an issue with Esri Support. They can be contacted at https://support.esri.com/en/contact-tech-support. This allows for other users to attach to the bug and allow. It also helps us prioritize our work. Thanks, Tom ... View more

Hi Michael,  Thanks for contacting support. Having an official BUG number help! It also helps track the issue since its status automatically changes as the issue goes through the system. As of now we don't know the prevalence of this issue.  Our testing and certification of Pro 2.7 did not undercover any issues like this and we have many test cases with line work on layouts that get exported to all the supported formats.  However, enough people are reporting this issue that we consider this a HIGH PRIORITY item. We "lucked" into a test case that reproduces the issue and that gives the developers something to work with. Recreating these items is NOT acceptable. We understand this and offer the python work-around as something to work with until we have a solution. Unfortunately, it is the only option at this point. Hopefully, the examples provided at the links can help "code adverse" GISers a little help to overcome any hurdles. Tom ... View more

All,  Currently, we believe that the lines are getting dropped during the exporting process through the UI.  This is being investigated as we have found a single case where this is occurring. We've also have discovered, with this specific case, that exporting the layout via python (ArcPy.mp) includes the expected lines as expected in the exported file. This may provide a workaround until we have identified the bug and engineered a solution. You can open the Python window from the View tab on the ribbon. The following code, when pasted into the Python window and run, will export every layout in the project to a PDF file in C:\temp. For map series in the project, only a single page will be exported. ##Export to PDF aprx = arcpy.mp.ArcGISProject("CURRENT") aprx.listLayouts() for lyt in aprx.listLayouts(): #Parameters: output name, resolution, image quality, compress vector graphics, image compression, embed fonts, layer attributes, georeference, jpeg compression, clip to elements, output as image, embed color profile #Image quality: "BEST", "BETTER", "NORMAL", "FASTER", "FASTEST" #Image compression: "ADAPTIVE", "DEFLATE", "JPEG", "LZW", "NONE", "RLE" #Layer attributes: "LAYERS_ONLY", "LAYERS_AND_ATTRIBUTES", "NONE" lyt.exportToPDF(f"C:\Temp\{lyt.name}.pdf", 150, "BEST", True, "ADAPTIVE", True, "LAYERS_ONLY", True, 80, False, False, False) print("Done")  For more information on ArcPy please see - https://pro.arcgis.com/en/pro-app/latest/arcpy/mapping/tutorial-getting-started-with-arcpy-mp.htm At the bottom of this topic is a section on exporting to PDF. Sorry for the inconvenience and I hope this work around helps. Tom   ... View more