◆ Microsoft Power BI

Extract month names from dates

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
See the prompt↓All Microsoft Power BI tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskFrom the 'SaleDate' column in the sales data, extract the full month name (e.g., 'January',…+
From the 'SaleDate' column in the sales data, extract the full month name (e.g., 'January', 'February') and create a new column called 'Sale Month Name'. The marketing team needs this for their monthly campaign analysis.
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 the marketing team gets this sales data, create a new column that shows the full month…+
Before the marketing team gets this sales data, create a new column that shows the full month name from the 'SaleDate'. Make sure it's easy to use for filtering and grouping in their reports, and check if there are any dates that might cause issues.
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 extracted the month names from the 'OrderDate' column, but now they're sorting alphabetically…+
I extracted month names, but they're sorting alphabetically instead of chronologically.
I extracted the month names from the 'OrderDate' column, but now they're sorting alphabetically in the report, which is confusing the sales reps. I need them to sort chronologically, but I'm not sure how to link the new text column to the original date order. What's the right way to fix the sort order without creating a messy workaround?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI constantly struggle with getting month names to sort chronologically instead of…+
I always struggle with getting month names to sort correctly in my reports.
I constantly struggle with getting month names to sort chronologically instead of alphabetically in my reports, leading to confusion for stakeholders. I usually end up creating complex helper columns. What habit should I change in how I extract or prepare month names to ensure they always sort correctly from the start?
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.