BUG::LAKEHOUSE::SQL ENDPOINT::GUI

[Element115]

ISSUE:

Bottom status bar disappears when lakehouse SQL endpoint query result pane is maximized:

[Anonymous]

Hi @Element115 ,

Thanks for reporting this. I communicated this issue internal.

The best course of action is to share this in feedback channel.

Appreciate if you could share the feedback on our feedback channel. Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog.

Hope this helps. Please let me know if you have any further queries.

[Element115]

How can I do this when your Ideas site continuously locks my account out!?! for the nth time, for crying out loud. How many times do I need to contact the Ideas site support to ask them to unlock my account?  

This is the very reason why I post on the Forums site because the Ideas site is... fill in the blank (I think you can guess what choice words I have for the Ideas site UX).

So please post it yourself, because considering the insane amount of time I spend on this forum reporting various Fabric deficiencies and not getting paid for it, no thanks, my patience is at an end.  I got a day job, you know, and all this back and forth is taking time away from my job for which I am getting paid, contrary to this.  Which makes one wonder:  Does Microsoft even have a QA department??? And if yes, what on earth are they doing? Smoking ganja and letting users find and report the bugs instead of them doing it?!?

[Anonymous]

Hi @Element115 ,

I agree that this issue looks strange and if you have a support plan could you please file a support ticket for deeper investigation and do share the SR# with us? In case if you don't have a support plan please let us know here.

[Element115]

Yeah I got a plan, but I don't have anymore time for this.  You do it please.

[Anonymous]

Hi @Element115 ,

Thanks for the update.

[Anonymous]

Hi @Element115 ,

Thanks for using Fabric Community and reporting this minor bug.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.