◆ Google Looker

Bulk update Looker content

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 primary data source for all 'Marketing Spend' dashboards from the old Google Ads…+
Update the primary data source for all 'Marketing Spend' dashboards from the old Google Ads account to the new unified marketing platform by Friday.
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 bulk update the data source for all 'Marketing Spend' dashboards, identify any reports…+
Before I bulk update the data source for all 'Marketing Spend' dashboards, identify any reports that might break or display incorrectly due to schema changes between the old Google Ads data and the new marketing platform. Flag these specific reports and suggest a mitigation strategy for each.
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 the bulk update for the marketing spend dashboards, and now three key reports are…+
I just ran the bulk update for the marketing spend dashboards, and now three key reports are showing 'data source error'.
I just ran the bulk update for the marketing spend dashboards, and now three key reports are showing 'data source error'. The marketing director needs these for a board meeting tomorrow, and I'm terrified they'll lose faith in our entire reporting system. I can't tell if it's a simple field mismatch or a deeper connection problem. What's the likely diagnosis here, and what's the best next move to get these reports live again before the morning?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI often find myself manually fixing individual reports after a bulk update fails partially,…+
I often find myself manually fixing individual reports after a bulk update fails partially.
I often find myself manually fixing individual reports after a bulk update fails partially, which consumes valuable time and frustrates the end-users. This makes me hesitant to perform necessary updates. What habit should I change to better anticipate potential issues with bulk updates and implement more robust pre-checks or rollback strategies?
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.