Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "power bi"
Dear Microsoft power bi team.
Go fuck yourself. Put that dashboard up your ass. The documentation for this is a joke.
The doc says I can get my tokens from azure portal. But guess what. The portal is a sea. And seems like powerbi is moved out from portal to its own powerbi.fuckyoumicrosoft.com
What the actual fuck you dimwits. Why don't you document it properly ?
For fuck sake. Go show up your analytics deep into your pie chart.2
Security is a joke. And people don't seem to get it. Especially Data mungers.
I've spent about half an hour trying to work out how to securely connect to power BI using PowerShell in a renewable manner for unattended access later on.
Every single example I've found seems to involve you storing $user and $password variables inside your script. If I'm lucky, they're going to pass them through ConvertTo-SecureString. And nobody talks about securely storing AD auth tokens, or using the Windows Credential Manager.
I know it's possible, but it's going to take me ages to work out how from all sorts of disparate sources...16
i was about to talk about golang - but it can wait.
snapchat's discover section is TERRIBLE. the amount of BULLSHIT, INCORRECT INFORMATION, AND PURE IDIOCY IS MAKING IT TERRIBLE.
now, usually, i rant about mashable when i say it's terrible. AT LEAST WHEN MASHABLE WROTE ABOUT THIS THEY WERE CORRECT. but no, alas, my faith in humanity is put to an all time end. a new evil has arose, by the name of "wired."
of course, and incredibly late to the party, a "tech" outlet wrote about bitcoin. the headline was "is bitcoin killing the planet?" IT HAS BEEN POSSIBLY THE STUPIDEST ARTICLE IVE READ OF ALL TIME. THEY CLEARLY HAVE NO IDEA ABOUT ANY SHIT THEYRE TALKING ABOUT.
let's take a look at the TWO facts they got wrong, and displayed to over a MILLION people.
now, instead of just GOOGLING TWO SIMPLE FACTS, THEY DECIDED TO JUST WRITE RANDOM SHIT.
ENOUGH WAITING - HERE THE THE TWO FACTS THEY GOT WRONG
picture 1: bitcoin up $900 in the last year? THE LAST MOTHER FUCKING, COCK SUCKING
WHY DO SUCH DUMBASSES HAVE ACCESS TO SOMETHING MILLIONS VIEW?
IT MAKES NO FUCKING SENSE
picture two: the actual fuck????
did i just read that?
b- bi- bitcoin will "run dry" BY 2032.
i think i finally figured it out.
these facts, they're literally just random number.
i can see it now:
wired employee 1: hey, guess what number im thinking of?
wired employee 2: 14?
wired employee 1: *screaming* BITCOIN WILL RUN DRY IN 14 YEARS
how do these people get hired. do they hire only hire 12 year old interns? im genuinely asking. does anyone know?
okay, end of rant. plz continue complaining about dumbasses who have power thru the media in tech8
Rough start to the morning. Working with a partner in a Power BI scenario. He uses forums, over research, to find how to map IP to latitude/longitude. Naturally our mangager wants this done as short as possible so I stay back a few hours and get it done.
Show him this morning all the effort I put in to get it to work... He denies it's good enough and proceeds to tell me 'his way' of getting a forum 'genius' is easier and will work better, and refuses to hand in what we have done... Help 😰
So, the PowerQuery type system appears to be a Joke.
For those you that aren't familiar with PowerQuery, it's the ETL language that is used in PowerBI, and some other parts of the MS PowerPlatform. It was formerly known as the M Language.
The language has a type system, that includes records (think hashes) and tables, which are, for practical purposes, a list of records.
The wonderful M language specification document states that:
"Any value that is a record conforms to the intrinsic type record, which does not place any restrictions on the field names or values within a record value. A record-type value is used to restrict the set of valid names as well as the types of values that are permitted to be associated with those names."
Except that the restriction is only to the set of valid names, and the language interpreter doesn't throw an error when I place a number into a text field, but also doesn't do any sort of implicit conversion. This is all hunky-dory, until you then try to load the data into the Tabular Model that underlies the query engine, which does expect the values to be of the type that is specified, and it throws an error.
But PowerBI, in its infinite wisdom, doesn't actually *record* the error, it merely tells you the error exists, and tells you to go back to the query editor to list the errors thrown up by the powerquery engine. Which, as previously stated, doesn't throw up an error for this instance.
So I've spent all afternoon trying to work out why my queries aren't loading, because I have an error that doesn't exist. fml.
[You can follow this issue on the communtiy feedback site here: https://community.powerbi.com/t5/... ]
That moment when you have to attend power bi introductory session but you already delivered 2 business intelligence solutions in a previous job.
And he doesn't even have a clue what he is talking about
So it's been 4 months and my struggles with Power bi continues. The .net developer I once remains only a bleak memory.
So yesterday the client thought about securing reports, I appreciate the step and suggested embedding them in SharePoint Web parts and securing the access from the desktop app. The client wasn't thrilled with my suggestion as his clients might not have SharePoint, valid point. Instead he wants me to create a small web app with a login page to share the public web url of the reports.
He can't trust client by giving them direct urls but will trust them to login first and then have the url....1
Power BI: wonderful tool, pretty graphics, and can do a lot of powerful stuff.
But it’s also quite frustrating when you want to do advanced things, as it’s such a closed platform.
* No way to run powerquery scripts in a command line
* Unit testing is a major pain, and doesn’t really test all the data munging capabilities
* The various layers (offline/online, visualisation, DAX, Powerquery, Dataset, Dataflow) are a bit too seamless: locating where an issue is happening when debugging can be pain, especially as filtering works differently in Query Editing mode than Query Visualisation mode.
And my number 1 pet peeve:
* No version control
It’s seriously disconcerting to go back to a no version control system, especially as you need to modify “live code” sometimes in order to debug a visual.
At best, I’ve been looking into extracting the code from the file, and then checking that into git, but it’s still a one-way street that means a lot of copying and pasting back into the program in order to roll back, and makes forking quite difficult.
It’s rewarding to work with the system, but these frustrations can really get to me sometimes2