Are you getting an INTERNAL_SERVICE_ERROR while trying to add a new data set to Quick Suite?

As much as QuickSuite promises, its error handling for importing data sets is severely lacking.

Instead of telling you why they can’t process your data, they just present you with an INTERNAL_SERVICE_ERROR , and when you look up what that means it simply states An internal service error occurred. (No duh…).

As it turns out Quick Suite really doesn't like glue Map fields, and I am assuming any other field that isn’t just flat data that you would put in an old-fashion excel sheet.

So what do you do if you want to import nested data?

I was able to hack around this by adjusting the Athena query that gets run when the data is imported by converting the complex field into a JSON string, then in the data set pipeline, creating custom fields for each of the nested map fields.

Basically, json_format(myMapField AS JSON) will do the trick.

It’s tedious and makes things much less dynamic, but I can see why they would want you to explicitly state the fields coming in so they can be indexed.

It just makes it difficult to create a dynamic event-driven architecture system.

I hope that by posting this in the future, someone facing the same problem someday will find this and save themselves hours of banging their head against Quick Suite.

If you need help scaling up your AWS infrastructure without breaking the bank, feel free to set up a consultation.