I noticed that some of my appsheet connection were broken on Looker Studio, while not making any changes on the report.
I first tried to update the fields, but it said that there weren’t any new fields (which is false).
The new fields appeared only after I connected again .
This is an issue as I don’t know why this happened. Maybe an appsheet / looker update ? I noticed that a new ‘region’ field appeared when selecting appsheet as database.
Please take a look at the last but one post (second last) in the post thread below.
We observed the same issue with our ongoing Looker Studio Project which is connected with AppSheet as data sources. Unfortunately, there was no caution nor guide were given by Google team as usual before the exsting/working product is made not-runnable.
It was few weeks back when we initially noticed the Looker Studio Project started to throw error while the project is using AppSheet as data sources.
What we did is to RE-CONNECT to AppSheet as data source for those projects one by one. Then issue was gone.
It looks like there was new process was introduced to select AppSheet as data source for Looker Studio. Before it was not asked but now we have to select “REGION” either “AppSheet” or “AppSheet EU”. This additional process seems to be a root cause to break up our existing AppSheet/Looker Studio project.
If so, why your team is not proactive to give us a caution or guide before the break down does happen to our services???
Im completely at a lose why Google not give us any notice or guide before you make some changes to the platform… This always happens though, even after I claims hundreds of times.
At this point, we haven’t seen any reports that suggest the similar issue. But we are taking a look into this internally anyway. Please stay tuned!
The other post might be a different problem with Looker partner connector. Also, could you please share a screenshot on what you see from your end (e.g. error message)?
I have fixed all the Looker Studio projects which were affected, so I can not share any screenshot and short-movies for now.
However, the gist of the problem and how it was fixed was ; -
The Looker Studio project which connected to AppSheet as data source all the sudden in error. (not correctly display data inside dashboard.
Checked the data source from each project and re-connected to the AppSheet manually.
At the point of that time, we are asked to select “project” either AppSheet or AppSheet EU", which have never being asked for before.
We are PAC region, so selected “AppSheet”.
Then the dashboard get back to normal.
We had to do this process for all the Looker Studio project which have AppSheet app as data source.
Hope this helps.
This is exactly what happened to me and exactly how I solved it.
Also, I am located in France so I first selected AppSheet EU, but my tables were not available (no items).
So I quite don’t understand what is it linked to. @devingu can you provide insight about this ?
I consider myself lucky as I don’t have much tables to re-connect (only one). But this can be annoying if you have multiples tables and you don’t know when it’ll happen.
I can confirm that I had to reconnect Appsheet Data Sources and discovered the new Region setting for data sources. It wasn’t a huge pain to do this, but it would have been nice to have had an announcement or warning that this would need to be done. It’s fine for me as I only had 5 or so Appsheet sources…which by the way is an awesome feature.
I apologise on behalf of the European Union for their annoying interjections into the world’s data flows!
Thanks this is really helpful! I am forwarding this to the Eng team and they will take a look into this shortly!
I made an update to the Looker Connector in a way I had thought wouldn’t cause things to disconnect which seems not to have been accurate. I will try to get a fix in but unfortunately the process to release new versions of the connector is a lot slower than usual AppSheet releases, so recreating them might be faster. Sorry about the pain here.
In regards to the Appsheet EU confusion (which is very fair), AppSheet EU is referencing those users who connect to eu.appsheet.com as opposed to appsheet.com, I will update the language there to try to indicate this more clearly (what I was trying to do in the first place was make it so that our eu customers could use our Looker Connector too).
Hi @benhare the AppSheet connector is flaky & unusable. Can you look into this as a matter of urgency please? Date is 2025/05/24 - yesterday the connector was completely broken. Then we were informed it was fixed, today you can connect your data source BUT you cannot use it. System Error for every metric you try to configure.
Can you raise a support ticket for this? I’m not seeing in our metrics what you’re seeing, and my own dashboards have been working (they broke during the outage yesterday) so we’d need some more information.
@benhare I tried to raise a support ticket yesterday & AppSheet support told me to go & raise this with Looker Studio support. You cannot raise a support ticket on the free access of Looker Studio. I guess AppSheet support felt bad! and 8 hours later sent me a follow up email telling me everything was fixed. I have responded to that telling them it is not fixed. You can connect your data but cannot use it!@ I sent them the screenshot, I reported the issue on Looker system reporting (not a ticket but a system report) & here we are!
by the way I can use the table/tab when I connect Google Sheets. So the issue lies squarely with the AppSheet connector in my opinion.
do you have a case id i can look into?
