◆ Google Looker

Fix data set configuration errors

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need to fix the 'invalid column type' error in the 'Customer Feedback' dataset configuration…+
I need to fix the 'invalid column type' error in the 'Customer Feedback' dataset configuration that's preventing the sentiment analysis report from running. Tell me the specific column causing it and how to correct its type to a string.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I deploy the updated 'Customer Feedback' dataset, check for any configuration errors…+
Before I deploy the updated 'Customer Feedback' dataset, check for any configuration errors that might cause issues for the marketing team's sentiment analysis report. Specifically, look for 'invalid column type' errors, suggest the correct types, and flag any other potential schema mismatches that could break their existing reports.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'Customer Feedback' dataset is showing multiple 'invalid column type' errors after a recent…+
The 'Customer Feedback' dataset is showing multiple 'invalid column type' errors after a recent source system change, and the marketing team needs their sentiment report by tomorrow.
The 'Customer Feedback' dataset is showing multiple 'invalid column type' errors after a recent source system change, and the marketing team needs their sentiment report by tomorrow. I'm worried about breaking downstream reports by making hasty changes, but delaying isn't an option. I don't know which columns are most critical to fix first. What's the best strategy to prioritize and correct these configuration errors without causing new problems?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternDataset configuration errors, especially column type mismatches after source system updates,…+
Dataset configuration errors, especially column type mismatches, frequently delay our reporting and require urgent fixes.
Dataset configuration errors, especially column type mismatches after source system updates, frequently delay our reporting and require urgent fixes. I spend too much time chasing down these issues reactively. What habit should I change to proactively validate dataset configurations and schemas after any upstream data source changes, ensuring data integrity before it impacts our business users?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Google Looker's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.