-
My goal: let App builder do the work on paginated queries
-
Issue: I have tried it but it failed
-
Steps I've taken to troubleshoot: instructed better
best
Hi @mascaritas, Assist still has some areas where it can improve for sure. I've tried this myself and while it configures a query with a limit and offset based on the table's current page, the API doesn't seem to be able to implement Add-ons (not just pagination, but the summary row as well) for the table component.
We've noted this to be fixed but for now you'll have to manually implement pagination, which we have a demo for here!
Hello, Mike. Thanks. A lot for your. Reply. I noticed I have sent off some dictation mismatch. But I want to iterate or update on what I have achieved. Actually. I was able to build a whole app with REST API based pagination and agent built it for me. As a charm.
The thing where I really struggle is to understand how can the agent build such a well crafted implementation with a Badly documented REST API, but if I connect it to the Shopify Graphql which is of course self introspection and all. It fails miserably. After. Two prompts every time. I'm wondering if anyone else has this observation. Does it not like Shopify?
Assist currently works best with some of our most commonly used resources (Retool DB, Postgres, REST API, etc) but we definitely appreciate any and all feedback on issues with other APIs. I see your other thread on the Shopify GraphQL resource so I can continue with you there!
Anyway, it was able to build a patinated query which I could never do manually just by prompting at it. This is already worth a lot.
Also, it was able to build batch processing, meaning I can select multiple instances in a list and let a query run over it
—> all built by the app Gen function , this is huge for me