nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

After Update to ArcGIs Pro 3.4.2: Blank map frames when exporting Layouts created in 3.3.0

StefanWrubel

Hello everybody,

I have tons of maps created in ArcGISPro Version 3.3.0. Recently, I updated to ArcGISPro Version 3.4.2 (German interface). It would be a lot of unnecessary work to rebuild everything in 3.4.2 from scratch. So naturally, I continue using the maps and layouts I created in 3.3.0.

Today I created a new project (3.4.2), then by copy-paste inserted an existing layout (from a project created in 3.3.0) and several symbolized feature classes (from a geodatabase created in 3.3.0). The link to the geodatabase is properly enabled. On screen everything looks fine.

When exporting the layout to pdf, all map frames in the layout stay blank, also the legend is empty.

I re-started the app and pc several times, I tried export to .png, to .jpeg etc., I emptied the cache, finally I tried exporting without background wms layers, it all did not help.

My colleague still has Version 3.3.0 on his pc, export took some time, he lowered the resolution to 200 dpi, it worked out fine.

Could the Export Error I experience possibly be a bug due to the update?

Encontre mais publicações marcadas com

Accepted answers

StefanWrubel

Thank you for your feedback. @AubreyKinghorn: Yes, it's the known BUG-000173108. But how could I possibly delete the empty frames? On screen they are not empty, and I would not like to rebuild all maps just due to an esri update.

The best solution to my problem was to downgrade back to Version 3.3.2 and ignore the update notifications.

After contacting esri support, they told me, they've already fixed the bug, but won't release a patch for it. The problem will be fixed in Version 3.5 which is scheduled for summer. The german interface will be available a couple of months later. Since I can't wait for this long, I'd just skip the update 3.4.2.

Why did I not downgrade to 3.3.5? Because esri couldn't confirm that my problem could be resolved in Version 3.3.5., but they replied in version 3.3.2 it works fine.

All comments

DanPatterson

If you intend to reuse maps everytime you start a project, I would consider using a template.

Create a project template—ArcGIS Pro | Documentation

If this is a one-shot effort, I would consider creating a "map package" in the old project to use in the new project.

Generally Share a map package—ArcGIS Pro | Documentation

specifically Package Map (Data Management)—ArcGIS Pro | Documentation

copy paste seems to be a shortcut which probably doesn't handle all the intricacies that the tool would.

Lon_Franson

I'm having a similar problem. I opened a pre-3.4 project. Initially, I could export the two layouts in the project to PDF just fine. But after I duplicated one of the layouts in the Catalog and edited it, now all the layouts print with the map frames blank with empty legends. It doesn't matter if I am exporting to PDF, exporting to an image, or printing straight to a printer.

AubriOtis

It sounds like you are running into BUG-000173108 . The workaround is to delete any empty map frames you might have on the page. That usually solves the problem in the export.

danielri

Instead of using Export and Save to a PDF, Print to PDF instead (you do have a PDF driver installed, such as Microsoft Print to PDF?) and compare the results. This will confirm if it is an issue with invisible data frames as discussed by Aubri

Lon_Franson

I tried printing to a physical printer and was getting the same result as exporting or printing to PDF.

I couldn't find any empty map frames in my project. But your suggestion prompted me to save the layouts as layout files, delete the layouts from the project, and import the layout files back int. This worked for me.

StefanWrubel

The best solution to my problem was to downgrade back to Version 3.3.2 and ignore the update notifications.

Why did I not downgrade to 3.3.5? Because esri couldn't confirm that my problem could be resolved in Version 3.3.5., but they replied in version 3.3.2 it works fine.

Marco_C

If they fixed it in V3.5, why are they waiting until summer to release it?

This is an acceptable bug for me. I don't think ESRI understands how expensive this program is.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.