Select to view content in your preferred language

ArcGIS Pro 3.4 Bug: Page Query, Map Series, and Long Domain Conflict

256
2
Jump to solution
03-19-2025 07:07 AM
Labels (1)
SMauri
by
Frequent Contributor

Hi everyone,

I wanted to report a bug I've found in ArcGIS Pro 3.4, and it seems to still be present even after the latest patch.

The issue occurs in a print layout where the Map Series property is enabled. Specifically, the problem arises when the "Page Query" property is activated on map layers. This allows for a filter to be applied that matches (or doesn't match) the "Name Field" set at the Map Series level.

However, the bug only appears if the field set for the "Name Field" has a "Long" domain type associated with it, and the value set for the "code" doesn't match the value in "Description".

I've created a test project to replicate and verify this issue, and I'm attaching it as a Project Package for your reference.

Has anyone else encountered this issue? I'd be happy to provide more details or examples if needed.

Thanks!

0 Kudos
1 Solution

Accepted Solutions
Robert_LeClair
Esri Esteemed Contributor

This appears to be BUG-000174266 - "Spatial Map Series Filter does not show features in ArcGIS Pro 3.4, when a domain field is used for the filter and the coded value and the description are different values." 

The workaround is to include a domain where the coded value and the description match, or use ArcGIS Pro 3.3.

The bug status is "in review" at the moment.

View solution in original post

0 Kudos
2 Replies
DanPatterson
MVP Esteemed Contributor

What is the bug number? 

Was it reported as a bug on Esri Support | ArcGIS Technical Support

If it wasn't reported, Tech Support is the best place to do so since it can be tracked by others


... sort of retired...
0 Kudos
Robert_LeClair
Esri Esteemed Contributor

This appears to be BUG-000174266 - "Spatial Map Series Filter does not show features in ArcGIS Pro 3.4, when a domain field is used for the filter and the coded value and the description are different values." 

The workaround is to include a domain where the coded value and the description match, or use ArcGIS Pro 3.3.

The bug status is "in review" at the moment.

0 Kudos