I have two problems that I am wondering if they are related…
Problem #1 is that in one of my apps that I am developing, when I submit updates they do not go into the correct column in my data source (but it used too).
Problem #2 is that in a different app, updating is not sending the information to the data source. The first part of the block runs, and the last blocks (not in picture) do as well (as long as they’re alone)…but once I add the update data source block, then it fails during this step.
Sorry, I misspoke in my post. For both of these apps, this is the creation point for the data. It should enter into a new Row, but export the data into the correct column.
@jns.paramedic I recreated your blocks above, and the only time I can replicate your issue, is if I leave a create row argument empty. If I pass an empty string the values are added to the row correctly.
Regarding the issue with updating the data source, I would try passing the empty strings where you have missing arguments in the create row blocks and see if that fixes your issue.
If not, I would try debugging the rowId you expect to update. In one of my tests, I received A 502 Bad Gateway error, which indicates a communication error between the web servers.
If that’s happening to you, I would try the Live app and see how it handles the data tranfer.
The first cell is an equation in Excel, so I can’t insert a blank…but I used a join text block to remake the equation within Thunkable. That way an actual item is imported and the rest of the inputs line up. Thank you!
I’ve never thought to do this - great idea @jns.paramedic
Did you get this working? I would suggest having the create row block inside your get current location block so that you’re passing the right lat/lng values
