I am trying to add a backend filter to a Data Collection that is trying to pull records from a SmartSuite table that has thousands of rows - but I only need about 100 of those rows for my current purpose.
I have set out my process below in hope someone can tell me I am doing it wrong!
I created the collection, selected my table and then went Continue - this worked in that it seemed to pull in all the rows - and it also seems to get the data structures of the table into WeWeb to give me a starting point for working out my backend filter.
I used the AI tool to create my formula and ended up with the following
…which I thought was looking pretty good. It seemed to be just pulling in the records I expected - but maybe they are not an array?
I then hit Continue again but this is when I get an error
So I am not sure if I am just doing it wrong or if the formula I have used for my filter has incorrect logic.
Any advice much appreciated
I think the formula you are using can work as a frontend filter only. If the backend filter (the “native filter” field) follows the docs of smartsuite about filter syntaxt it should be a json object, not a javascript function. since it looks like the smartsuite plugin code is not on weweb’s github account I suppose you need to ask weweb’s support about the use of the “native filter” field.
1 Like
Thanks for the feedback. I have done a bit more research - I think to follow your approach I would need to revert to the REST API connection approach. I am currently using what I understand to be a custom data connection to SmartSuite - but given I can’t get it working I don;t have much evidence for that - 99% likelihood it will be user error though. There are some videos but they all use front end filtering which is fine if you have 10 records but I don;t think will work for me.
I will keep on bashing - it may be that Softr is more the place for us!
I am actually starting to wonder if the Back End filtering via SmartSuite connection even works. There are a couple of filter and sort buttons in the interface but if you click on them they don’t even open properly in the WeWeb interface - they ony half fit on the screen and can’t be closed suggesting there may still be some kinks to work out. It would be great to hear from someone who has managed to get back end filtering working in this way
I have made a tiny bit of progress and a tiny bit more understanding of how this all works - but still not getting it to work…
I have connected to a table that only has 18 records so is a bit more manageable. I can use the SmartSuite data connector to connect to it and this pulls through all 18 records. I then go back and create a formula as seen in the screen shot below - this pulls through just 10 of the 18 records (as expected) and these are visible in the little preview window. So all looks good at that stage. However then I click the blue Continue button and I get the same error message as before.
If I look in the browser console I see that the URL has returned a 403 Error and a message about chunk.vendors.(?) There are also a couple of warning messages about some items being deprecated.
I am wondering if my issue might be more on the SmartSuite end… I am using the custom SmartSuite connector which I assume they built or signed off so I am surprised if the formula I built within the connector (and which seemed to be giving the right results) doesn’t work - it would be great to know if someone out there is actually successfully using the connector?
