Changed on:
6 Feb 2024
problem is, that the Boutique name is stored as an attribute against the order
11:02
the partner has asked for the source code of the List component
11:02
but I am not sure if this would be the right approach?
11:08
Cameron 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 differs
11:15
Christopher Tse
i think it’s the data collection that is unique. this would have to collate the number of orders per status per attribute value
11:17
they 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 analysis
11:17
this would be a great use case for the new list interface idea i proposed
@ben.harrison
11:31
Cameron Johns
If they're trying to collate data for results greater than a page won't that hit complexity limits?
11:31
Christopher Tse
yeah, they’d have to send multiple queries to get all the pages
11:41
Cameron Johns
DataProvider can go to 1000 items
11:42
Christopher Tse
Hasn’t been released yet in the sdk
11:44
Cameron Johns
True, but I believe it would be configurable via manifest
11:45
Christopher 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
Copyright © 2024 Fluent Retail Pty Ltd (trading as Fluent Commerce). All rights reserved. No materials on this docs.fluentcommerce.com site may be used in any way and/or for any purpose without prior written authorisation from Fluent Commerce. Current customers and partners shall use these materials strictly in accordance with the terms and conditions of their written agreements with Fluent Commerce or its affiliates.