Issues with Custom Grids

ccowin_odfw

Hello,

Was hoping to get some tips on how to make the custom grid actually usable. Right now it works incredibly inconsistently

1. I'll click to activate or turn a side vertical and nothing happens.
   1. Sometimes the check box will reflect the change sometimes it wont.
2. Sometimes it will switch over and then the changes will just be lost and it'll revert back
3. Sometimes changes are saved and sometimes they aren't

It is so incredibly frustrating that this just doesn't seem to work with any level of consistency. It also freaks out when I select the feature it should be using and getting the field names.

How does anyone get this thing to work?

Here is a screenshot you can see where I have the range disabled, but it doesn't do away! Like what else is that suppose to do?

 

TomBole

Hi @CynthiaCebrian, 

I appreciate your frustration. The fix for the specific bug mention above - BUG-000141980 - was installed in 3.1 which was released 02/23/2023.  You can see the status for the issue here. I found it with a google search on "esri BUG-000141980". I tested the scenario described in this bug with version 3.4 and found no regression.

Since you are still seeing issues with 3.3 I think it safe to assume that you are running into a separate issue.  Here are the outstanding custom grid issues that I am aware of. The last 3, without bug numbers, are issues discovered by esri staff.

• BUG-000169960 No option to select placement of grid labels when using clipped layers
• Adding a definition query to the custom grids layer doesn't refresh the custom grid
• Custom grid does not completely draw when the map frame is rotated more than 23 degrees
• UI sync issue when changing the vertical properties for 2 different label components within a single custom grid

What kind of issue are you running into?  Are you getting the wrong results?  Is it a UI issue? If so, can you describe the issue?  What your steps?  We did do some work in the last few releases trying to improve the custom grid UI. 

Not knowing the specifics of the issue you are running into there is no way I can say whether or not it is fixed in 3.4. This is one of the main reasons we encourage people to contact support and log a bug, even if it might be a duplicate of an existing bug. Only by having actual data/steps can we validate the fix for the specific problem someone is reporting. Otherwise, we are validating the fix against our data/steps and understanding of the problem. Sometimes this matches bugs not reported, sometime it doesn't.

I highly encourage you to take your specific issue to 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.

Tom