◆ Microsoft Power BI

Load data from a relative path

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 taskLoad the 'MonthlySales.csv' file from the 'Data' subfolder into the current report, assuming…+
Load the 'MonthlySales.csv' file from the 'Data' subfolder into the current report, assuming it's always in that relative location.
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 share this sales report with the team, ensure it loads data from a relative path, so…+
Before I share this sales report with the team, ensure it loads data from a relative path, so anyone can open and refresh it without breaking the connection, even if they move the project folder.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentDavid just opened the Q4 sales report I sent him, and all the data connections are broken,…+
My colleague, David, just tried to open the Q4 sales report I sent him, and all the data connections are broken.
David just opened the Q4 sales report I sent him, and all the data connections are broken, showing 'file not found' errors. He's frustrated because he needs these numbers for his meeting in an hour. I'm afraid he'll lose trust in my reports. I don't know if he moved the folder or if my paths were absolute. What's the best way to diagnose why the connections broke and quickly fix them so he can refresh the data, ensuring it won't happen again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI consistently lose time and cause frustration when my reports break for colleagues because…+
My reports often break when shared or moved because of absolute file paths.
I consistently lose time and cause frustration when my reports break for colleagues because I've used absolute file paths, especially when project folders are moved. This leads to constant troubleshooting calls. What habit should I change to reliably load data from relative paths, ensuring my reports are portable and always refresh correctly for anyone who uses them?
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 Microsoft Power BI'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.