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

Interactive HTML & JMP report: different behavior, different values

RonB

Created simple bar chart with filters.

When applying filter:

1-JMP report adjust bars and recalculates percentages - OK

2-HTML removes bar - whole or part of - and doesn't recalculate percentages - NOT OK

3-Intial values on HTML differ from JMP - 20.5% vs 21% - NOT OK, implies different rounding

Side question:

Created filter columns grouped as AND. When saving JMP changes to OR

Accepted answers

josh_markwordt

The fading of the lines was an experimental new type of rendering that we were trying out for the Interactive HTML crowd, hoping it would provide greater insight into the data, but it has proved unpopular and confusing since it differs from JMP, so it has been removed from Interactive HTML and JMP Live in JMP 16 which is currently under development and will be available in March. Going forward, we are matching JMP. Interactive HTML is a publishing capability that provides some level of interactivity for the web for a subset of JMP’s platforms and features, but without the power of JMP we are unable to reproduce all of the statistical calculations JMP is capable of, and excluding and including data with the data filter is a feature that we reserve for JMP Live. Selection and hiding of data are two filtering modes that we provide for the web at no extra cost with a regular JMP license. We realize this can be a little confusing so in JMP 16 the data filter will be disabled in Interactive HTML if you have the Include box checked when you export to make it clear that you cannot filter by including and excluding data in Interactive HTML:

All comments

josh_markwordt

#2 - In an Interactive HTML report, we are not including/excluding rows and recalculating the report when you filter but instead are hiding/showing with the data that is reported in the original report. If you'd like to be able to filter by excluding rows, that is a feature of JMP Live which requires talking to a JMP server to perform more advanced calculations.

#3 - This could just be a difference in formatting. Interactive HTML tries to match JMP, but sometimes we have differences that we would like to resolve. If you could provide a dataset/script to reproduce this specific case, we can open a defect to track it.

RonB

Thanks. That confirms what I thought. You need computing engine for proper filtering.

Furthermore, on interactive HTML the "filter" doesn't seem to merely hide/show data, at least on line graphs. Unselected data is kinda fades out yet still visible on graph. See attached.

Thus, one can't "sell" interactive HTML as something having a real filter. If we deploy jmp results to non-JMP users, say management, they'll have hard time accepting such idiosyncrasy, and may promptly demand Excel

josh_markwordt