Create a dashboard reporting component
How-to Guide
Changed on:
6 Feb 2024
Key Points
[Warning: empty required content area]Steps
problem is, that the Boutique name is stored as an attribute against the order11:02the partner has asked for the source code of the List component11:02but I am not sure if this would be the right approach?11:08Cameron Johns Does the current list not support what they're trying to achieve? I can see that we don't do clustered columns like the image but apart from that I'm curious how it differs11:15Christopher Tse i think it’s the data collection that is unique. this would have to collate the number of orders per status per attribute value11:17they can probably use the list in the sdk to display the data, and have a custom component that fetches the data outside to do the data analysis11:17this would be a great use case for the new list interface idea i proposed @ben.harrison11:31Cameron Johns If they're trying to collate data for results greater than a page won't that hit complexity limits?11:31Christopher Tse yeah, they’d have to send multiple queries to get all the pages11:41Cameron Johns DataProvider can go to 1000 items11:42Christopher Tse Hasn’t been released yet in the sdk11:44Cameron Johns True, but I believe it would be configurable via manifest11:45Christopher Tse Yeah that’s an option. They can put their component inside of a data provider and have it process the data from that instead of writing up the whole thing again
