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

778154_en-US

liliconcom

JMP Live Best Practices

Hello SE's from across the seas,

JMP Live is obviously different from desktop JMP. I've notice some "janky-ness" when publishing some reports, & am trying to compile a list for best practices to make reports look nicer & have better interactivity.

MY question is: What are some of your best practices for putting reports/data on JMP Live to improve interactivity/functionality/visual aesthetic?

here are a few that I've encountered

1) Make the report to your visual appealing before publishing. Once published, you can't change report aesthetically

2) The docking drop zones on your dashboards might shift after publishing: Discovered this issue during a live event with Jeff Upton. We found that some docking positions will show the data better on live, & it's a good to experiment this before a demo.

3) Time series forecast with multiple time series is best published using column switcher to switch between time series, vs the normal way of viewing all the time series in the TSF platform. When publishing to live, only the method with column switcher is interactive. (solution found out by Peng Liu)

Re: JMP Live Best Practices

Great idea @Lovy_Singh ! Maybe somebody knows a good place to have all these easily available, so we can all browse them when needed.

What I recently learned (thanks @Alex_Lippincott For publishing dashboards, the probability of having maximum interactivity is higher when the dashboard is created with Dashboard builder, as opposed to custom/scripted dashboards.

Best

Florian

Re: JMP Live Best Practices

Hi Lovy,

we started compiling a list with publishing best practices and have it documented here on confluence.

The list is nowhere near complete, because there are so many different ways a report can be designed. A simple, but quick test on how a published report might look like is to red triangle -> Save the script of your report to the Script window and run that. You will see changes to the layout immediately