◆ Google Looker

Update data in bulk in Looker

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 taskUpdate the 'product_category' for all products with 'old_category_id' 123 to 'Electronics' and…+
Update the 'product_category' for all products with 'old_category_id' 123 to 'Electronics' and for 'old_category_id' 456 to 'Home Goods'. Apply these changes across the entire 'Products' table.
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 update the 'customer_segment' for 10,000 customers based on the new marketing model,…+
Before I update the 'customer_segment' for 10,000 customers based on the new marketing model, help me identify potential data integrity risks. Flag any customers whose current segment doesn't align with their historical purchase behavior and suggest a rollback plan in case of errors.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just ran a bulk update on customer addresses, and now I'm hearing from the sales team that a…+
I just ran a bulk update on customer addresses, and now a few key accounts are showing incorrect information.
I just ran a bulk update on customer addresses, and now I'm hearing from the sales team that a few of our top accounts have incorrect addresses. I'm afraid I used an outdated source file or there was an error in the mapping, and this could impact critical deliveries. What's the most likely reason for this error, and what's the quickest way to identify the affected records and revert them?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently get requests to perform ad-hoc bulk updates, like changing a specific product…+
I'm constantly asked to perform one-off bulk data updates that feel risky and time-consuming.
I frequently get requests to perform ad-hoc bulk updates, like changing a specific product attribute for hundreds of items or updating a customer status based on an external list. These feel risky, take a lot of my time, and often lack proper validation. What habit should I change to streamline these requests or empower others to perform safe, validated bulk updates themselves?
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.