Power Query Editor - Add Column > Date dropdown is cut off for small window sizes

[PG1979]

I'm taking a course on Power BI and had to add some date-related columns to a calendar table in the Power Query Editor.  When I clicked on the Date dropdown, it extended to the edge of the window and was cut off.  The dropdown doesn't "float above" or extend past the window borders like dropdowns in other Microsoft apps do (Edge, Word, Power BI Desktop itself), nor does it scroll like those dropdowns when they reach the edge of the monitor.

Additionally, the course content shows that the Date dropdown used to have its options in sub menu flyouts by category (Year, Month, Day, etc.)  While maybe not the best solution, that is a solution and would work for me, but I cannot find a way to make the menu behave that way.  I'm assuming that was in an older version of Power Query Editor.

Resizing the Power Query Editor window does allow the full dropdown to appear, so I can at least use it.

I've attached a screenshot of what the current behavior looks like on my computer.  Screen resolution is 2560x1440, scaling is set to 125%, though the issue persists at 100%.  At 100%, the text is so small that the full dropdown appears at my preferred window size, but if I make the window smaller, it is once again cut off.

[PG1979]

My instructor replied back with the solution.  If you go to File > Options and settings > Options > Report settings > Customize appearance (preview), there is an option for "Legacy".  My desktop was set to "Light".  Once I changed it to Legacy, the Power Query Editor behaved the way it did in the class materials.

[ronrsnfld]

I can definitely reproduce that behavior here. I believe it should be reported as a bug, since, without resizing the window, not all of the options under Date are accessible if one is not using the Legacy view.

I have not been able to locate a place to report this. Maybe someone else can.

[v-priyankata]

Hi @ronrsnfld 

Please submit your concern by using the link below to raise an issue in the issue forum.
Issues - Microsoft Fabric Community

Thanks.

[ronrsnfld]

I attempted that, but a label is required and none of the "acceptable" labels seem to have anything to do with the Power Query environment. Do you have another suggestion? (I tried typing in labels like "Power Query", "Power BI", "Editor" and none were acceptable

[v-priyankata]

Hi @ronrsnfld 
Please add your issue under the Data Modeling label. Microsoft will review it and address the issue accordingly.

[ronrsnfld]

Thank you.  Posted

[Mauro89]

Hi @PG1979,

Iam curious, are you on a Mac (Apple) or any other machine running Windows?

Maybe a possible workaround is to open power query editor in the Web UI / Fabric, if the behaviour there is like in the screenshot from @MasonMA you can select the relevant fields there. 

Best regards!

[PG1979]

I'm running Windows.  I didn't think there was a Power BI Desktop for MacOS...

[MasonMA]

Hi, 

Which desktop version are with? Consider updating it to the lastest version and this is what i have. 

[Zanqueta]

Hi @MasonMA, its weird.

I tested the question from @PG1979 before reply and we have the same situation.

I'm using the current version also:

[ronrsnfld]

Mine is very similar to @MasonMA . The screenshot is with the smallest PQ editor window I can create:

And my version is also from Nov 2025 but seems to have a higher Version number than yours.

Version: 2.149.1203.0 64-bit (November 2025)

Perhaps your version was a QFE release and the version I have changed that behavior.

[Zanqueta]

Hi @PG1979,

I guess you are right. 

Why does this happen?

• The Power Query Editor uses a fixed-position dropdown that is constrained by the window size.
• When the editor window is small, the dropdown cannot extend beyond its container, resulting in options being cut off.
• The previous submenu design was removed in recent updates for consistency with other menus, but it introduced this limitation.

Current Workarounds

Use the formula bar or Add Column → Custom Column
Instead of relying on the dropdown, you can add date-related columns manually using M functions such as:

Date.Year([Date])
Date.Month([Date])
Date.Day([Date])

If this response was helpful in any way, I’d gladly accept a 👍much like the joy of seeing a DAX measure work first time without needing another FILTER.

Please mark it as the correct solution. It helps other community members find their way faster (and saves them from another endless loop 🌀.