Hi, does anybody if Glide apps API is accessible on a Business Trial? We’re not able to add rows and wonder if it has something to do with this. Thank you
I think you should be able to add rows on a Business Trial. Can you show us how you’re configuring your API call and what response did you receive?
1 Like
I have a team that’s on a Business Trial, and I just tested an API Add Row call to ensure that it works. It does, as expected.
As @ThinhDinh mentioned, if you can share a bit more information, we can help you troubleshoot.
1 Like
this is the request I’m sending - I triple checked all the parameters and it all checks out. The response I get back are two row ids ([{“rowID”:“cwi9UbBVQkyEb3I-Ex20.g”},{“rowID”:“4p5Tyqg2Q1G6oo5UYVh.Hw”}]), but no records are created. When I try to send a longer body, it returns the error “bad request”
.
btw I tried with both using the table ID and name
{
"appID": "Rx2SzMgtpFlYsxTzqoOe",
"mutations": [{
"kind": "add-row-to-table",
"tableName": "Library Accounts",
"columnValues": {
"Name": "samcutlerkreutz",
"lRbv3": "31641477",
"GkqUZ": "directed"
}
}, {
"kind": "add-row-to-table",
"tableName": "Library Accounts",
"columnValues": {
"Name": "jonathanrichetts",
"lRbv3": "31641477",
"GkqUZ": "starring"
}
}]
}
And what response do you get? (never mind, I see you updated your post with the response).
Question: are you posting to a regular Glide Table, or a Big Table?
Big Table
they do, wow 
thank you!!
well actually, there’s a second problem - the two added rows were tests to troubleshoot why I was getting “Bad Request” with my original body. It’s long, but it says Glide can do up to 500 mutations in a single request, so I’m stumped on what’s going on.
the request looks like this
{
"appID": "Rx2SzMgtpFlYsxTzqoOe",
"mutations": [{
"kind": "add-row-to-table",
"tableName": "native-table-8444d1d2-3b4e-442f-90b2-ed712f9d7232",
"columnValues": {
"Name": "samcutlerkreutz",
"lRbv3": "31641477",
"GkqUZ": "directed"
}
}, ... (126x times){
"kind": "add-row-to-table",
"tableName": "native-table-8444d1d2-3b4e-442f-90b2-ed712f9d7232",
"columnValues": {
"Name": "beard_of_noise",
"lRbv3": "27641218",
"GkqUZ": "additional sound mix"
}
}]
}
Copy/paste your entire JSON payload into a JSON Validator and see what you get.
It’s valid
Okay, that’s interesting.
If it works with 2 mutations then there is no reason why it shouldn’t work with 500, as long as the JSON is well formed.
You’re 100% certain that the structure of the request is identical in both cases, yes? (including the appID)
Where are you sending the request from, and how are you preparing the JSON?
Yea 100% certain it’s the same, using a Call API step in Actions in both cases (test and this one).
I’m using a lookup to get the mutations. Then I make the array unique using unique elements. then I use a joined list to comma separate the arrays. Then I use a template to create the final body with appid
I also tried using just the joined list without the steps before but get the same error
hmmm, I wonder…
How are you generating the column values for each row - with a JSON Object column?
I have seen the odd occasion where this will fail when used with a Call API or Trigger Webhook action, and I’m wondering if you may have bumped into one of these cases.
If you are using a JSON Object column, try replacing it with a template column and see if that makes any difference. It probably won’t, but is worth a shot.
I guess the other thing to check would be Row Owners - are any of the tables involved using them?
One thing you could do is modify your action so that it writes the JSON Payload to a column somewhere immediately before or after the Call API step. Then you could check exactly what was sent.
Other than that, I’m not sure, sorry. It really should work when setup as you’ve described.
I manually copied the body request to a single text field and used that to trigger the API response which worked. When I try to copy the body over to the text field in a separate automation step, it fails to do so. Does it have something to do with the fact I’m using user specific columns to generate the body? (not using row owners however, except on the Users table where I am creating the final payload)
If the source data is in user specific columns, then that could potentially result in an empty set of mutations, depending on which user you were triggering the action as.
That certainly suggests that something isn’t right somewhere.
At this point, I’m not really sure. I think I’d need to see this in front of me to be able to troubleshoot further.
@Airbid just now I’m working with the api to add rows. I think there is kind of a bug when you get the API info for the table to grab the column ids. It looks like you use the default column ‘name’. I just deleted that column and created it again and then the column gets a real id