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; } } }

Cannot select visible edges for labelling in a custom map grid

MartinJacquet

Hello, I'm working with a custom grid and I want to display labels on only one edge.

As you can see on the screenshot, the selection tool is unavailable, when I click on "Selected" that cause arcgis to freeze for a moment and then it switch back to "All". It works perfectly for the ticks, I have no problem to use the "selected" option in this case.

Any tips that could solve the problem ?

Thanks.

Find more posts tagged with

Accepted answers

All comments

amarcz_cc

Thank you so much!

TomDuncanGIS

Yeah, Thank you!!!

I've been stumbling around in ArcPro and web searches for an hour and you solved my problem 🙂 🙂 🙂

WaterBoutYe

I was demented with this yesterday and after 1 hr of randomly clicking, cursing and thinking it was a bug I figured out that it's not. It's just doesn't work in the way you are expecting it to.

Controlling the edges you want your labels to display on is not determined by the selection of the 1-2-3-4 buttons. You need to select each edge number individually then check or uncheck the "Visible" check box below to determine if the labels appear on that edge.

In the example below I want my column labels to appear at the top (1) and the bottom (3). So I pick "Selected", then click on 1 and ensure "Visible" is checked.

1 Screenshot 2024-09-27 090721.png

I then select 2 and ensure that visible is not checked.

2 - Screenshot 2024-09-27 090951.png

I then select 3 and ensure visible is checked...

3- Screenshot 2024-09-27 091036.png

and finally 4 unchecked...

4Screenshot 2024-09-27 091638.png

For my row labels I do the same but with 1 - unchecked, 2 - checked, 3 - unchecked, 4 - checked.

Hopefully someone finds this when having the same problem and it saves them a lot of swearing!

Aubri Otis

Hi,

I'm so sorry you are all experiencing this behavior. This should not be happening, it looks like there is a bug somewhere. We've addressed bugs like this in past releases, but something is still off.

Unfortunately, I can't reproduce with my own in-house data. There must be something slightly different either in your projects or workflows that I can't reproduce and wasn't found during the development testing.

If possible, I recommend reaching out to technical support. They can look at the workflow and data and design a reproducible case for the development team so this can be debugged and fixed. Again, I'm sorry you are still experiencing this issue.

ebarr_indepmo

The issue persists in 3.3

AndrewKinlock

I too am seeing this issue in 3.2.2 where you can select the edges and it reverts back to All.

JamesMarok1

Is this going to be fixed? Is a huge pain to not be able to do a custom grid since the edge selections don't work.

NW-AllyBuccanero-GISS

I'm seeing this behavior today in 3.2.1. The edge selection option is available, and you can select one more edges, but it's as if there's no save action happening, just reverts back to All. I've never had this problem in previous Pro versions.

BrendanCalhoun

Is there an updated bug link? The one shared previously said the issue was addressed in 2.7.2

amarcz_cc

ArcPro 2.8.0 also still does not accept this as fixed. The 'Selected' is still immediately reverting back to 'All'.

Edit: Also upgrade ArcPro to 2.9 and am still experiencing the same issue.

Edit: Upgraded to 3.1 and it still persists.. any other bugs to check?

danretired

Subscribe ... on the link and you will get notified

GaryHoaglund

Having the same issue when working with a map series. Works fine out of a map series in a single layout. Does anyone know if a fix was issued?

MartinJacquet

Update : the bug doesn't occurs when I set my grid parameters before creating the map series.

danretired

BUG-000137542: Unable to select individual edge components when for.. (esri.com)

If this is the case, you should "Subscribe" to it to get notification and push up the issue count

MartinJacquet

Yeah I found another post where the same issue was reported right after posting mine, it was indeed suggested that it's probably a bug. I contacted the support.

I'm working with 2.8.3

Aubri Otis

That looks like it might be a bug. What version of Pro are you using?

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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