CODEWITHSUNDEEP
google-apps-scriptlooker-studio
Justin
Justin

Reputation: 3039

How to debug system error in google data studio?

I'm working on a community connector, my fields are getting pulled in properly, but trying to use it in a report I get the following error below.

I'm less concerned about the specific error, but more concerned how I even figure out what is going on or breaking on the server.

Anyone figure out good ways to debug these errors?

enter image description here

enter image description here

Upvotes: 2

Views: 8326

Answers (2)

Diogo Schuarz
Diogo Schuarz

Reputation: 11

Sharing my discover here just in case, I was with the same case, but in my case this problem was occurring in a Pie Chart, but the same Metric combined with another segmentation didn't appear this problem.

After some test I found which case generates the problem, my problem was happening because this metric, in a specific segmentation, generates a total value negative, what Pie Charts have problems to show.

My field has string and numeric values too, but this is not a problem (until now at least). To solve my problem I create a new field where negative values are replaced by 0 (this doesn't make impacts at insight I need, because this values I don't need to track or show them in a Pie Chart).

So my suggestion here is try to understand if it is happening with a specific segmentation, or all time. With this segmentation, try to create filters and display each segment only, if this problem occurs you will discover which segment creates the error. Try to check the field you are making of sum, mean, or anything else, if he have negative values. If it happens, Pie Chart is not a possibility to show that, or you need to filter, replace, make any rule.

Upvotes: 1

Justin
Justin

Reputation: 3039

After a lot of research on this and digging around. I found that it came down to an invalid schema. ugh. I noticed that the getData, wasn't even being ran when trying to use data from a report. This made me think it was failing elsewhere.

In my case I was a prebuilt json object, and passing that to the schema field for data studio. Unfortunately google provides no feedback for mis-configured JSON schemas.

:sigh:

I simplified the schema and found the issue was a incorrect data type. Once I fixed this all worked :)

This method is mentioned here, and even google data studio says its hard to debug. https://developers.google.com/datastudio/connector/semantics

Its nice to have the schema seperate from code, but careful that the schema is correct otherwise you'll run into this very generic issue. Until they add more logging in this area.

Hope this helps someone!

Upvotes: 3

Related Questions