I’ve just had my first play with the new chart component. It’s seriously impressive. I built a pretty killer four chart dashboard in about 5 minutes. Great start.
Just got it running in our sandbox and did a test pass on our existing pages (including in our Community, which has extensive snippets and customization) and nothing appears to have broken! Just started looking at the new features - and playing with queues with drawers with queues. Very cool...
Then I added a table so that I could make real time data changes and have them reflected in the charts. It’s not just great eye candy (although it is certainly that), but it’s great for scenario modelling because the charts reanimate without having to commit to a save.
Now it seems churlish to already start asking for more … but it’ll be great when we can template the tooltips.
Would love to see how people are using the charting. I did a simple 2 chart with table page looking at client demographics but would love to see other people’s ideas. I agree with Glenn - great eye candy.
From our sandbox with some Game of Thrones/Simpsons clients:
Would love if the sorting of the categories would match SFDC sort order. Example: Title level should start with Executives, then go to VP, Director, Manager. I’m not sure how it’s sorted here but why not match how regular SFDC sorting is set based on the field? Product code should be alphabetical. Makes things easier to read if it wasn’t so random.
Joe, your sort order idea is a good one. For Picklist fields this is how things should work. We may need to end up implementing some secondary sort capabilities within the visualization code. Having the table and the charts listening to the same models is super powerful, but often you want them sorted in different ways.
I have the order of the Title Level set in the setup but it doesn’t appear that way on the chart. I’m not sure where the “Values” and “other” options come from either.
Well, we don’t consider the package to be completely clean yet, so you may get some unexpected resultls. But if you are willing to accept the risk, and play along as we release patch versions (keeping your org updated), we’d say “Go ahead”
Our reccomendation would be to install in a sandbox first, and spin through your pages to make sure core functionality is working before upgrading your production instance. But as small as you guys are, you may not have a sandbox…
We went for it … and our now live in production with RC3. So far, so good - my testing so far shows it’s working great on our Community site (a customer support portal in our case), and our internal pages (support and sales). But of course, tomorrow will be our first live day with everybody using it, so fingers crossed…!