cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Discussions

Solve problems, and share tips and tricks with other JMP users.
Choose Language Hide Translation Bar
JMP_Users
Level II

Issue with X-Axis Label Formatting in Control Chart Builder – JMP Version 19

JMP_Users_0-1760414587040.png

JMP_Users_1-1760414605879.png

Hi JMP Users,
I'm encountering an issue in JMP version 19 that wasn't present in version 18. In the Control Chart Builder, the X-axis label formatting used to display intervals correctly in version 18. However, in version 19, the labels are repeating instead of showing the expected interval format.
I've attached comparison graphs from both versions for your reference to highlight the difference.
If there's a workaround or a setting that can resolve this issue in version 19, please let me know.

 

1 ACCEPTED SOLUTION

Accepted Solutions
JMP_Users
Level II

Re: Issue with X-Axis Label Formatting in Control Chart Builder – JMP Version 19

JMP_Users_0-1760520291806.png

Thanks Ben...!

     Got it.

     By clicking "Sort by Subgroup" Option.

View solution in original post

3 REPLIES 3

Re: Issue with X-Axis Label Formatting in Control Chart Builder – JMP Version 19

Hi @JMP_Users ,

 

This appears to be a change in v19, I haven't managed to find a way around this - I would suggest you email support@jmp.com to let them know and they can help/log the issue.


Thanks,

Ben

“All models are wrong, but some are useful”
JMP_Users
Level II

Re: Issue with X-Axis Label Formatting in Control Chart Builder – JMP Version 19

JMP_Users_0-1760520291806.png

Thanks Ben...!

     Got it.

     By clicking "Sort by Subgroup" Option.

Re: Issue with X-Axis Label Formatting in Control Chart Builder – JMP Version 19

As mentioned above, this behavior is due to the fact that Sort by Subgroup is no longer turned on by default in Control Chart Builder in JMP 19.


This changes the default order of the horizontal axis when there is a subgroup variable.

If you have concerns with this new default behavior, you could certainly post to the JMP Wishlist to ask for the default behavior to be reverted in a future version of JMP.

Recommended Articles