Very cool to hear you’re using DynaWeb with the Airtable API.
It would be really useful if you could post/send me the DYN graph to help with debugging. If you’d be happy to contribute, we could also add it to DynaWeb samples folder for others to easily find and enjoy.
If you do plan to share, don’t forget to delete any API key strings or secrets in there).
To answer your questions :
1. Fields order
Though i haven’t used it before, a quick google or two lead me to believe Airtable API returns fields in a sorted order, with the ability for you to specify the field that is used for sorting.
Others with same issue : https://community.airtable.com/t/api-returning-fields-in-differrent-order/2299
Ordering records (& fields via in-page link) : https://support.airtable.com/hc/en-us/articles/223247187-How-do-I-sort-filter-or-retrieve-ordered-records-in-the-API-
I’d recommend using the JSON-to-dictionary node in the DynaWeb utilities in the meantime, since it will allow you to ignore the order of fields and retrieve the ones you’re interested in. YMMV though.
2. DynaWeb updates in realtime
This has to do with Dynamo caching the results (outputs) of nodes when executing. So if you run your graph and get stuff from Airtable, Dynamo won’t run that web request node again since it considers it executed (and hence no need to run again.)
This is something i’m aware of but i’ve not yet put any time towards making a built-in workaround in DynaWeb (requires messing with NodeModels).
To get around it today, you have a few options :
Unplug and re-plug your request/web client node from the node that executes the web request. You shouldn’t need to restart all of Dynamo, but let me know if this doesn’t work.
Use the ProRuBIM package’s
force children eval node : this forces all nodes after it to always execute, bypassing Dynamo caching.
I suggest option 2
Let me know how you get on.