Following this strategy we load the data to our file and we find our
first challenge. “Each passport is represented as a sequence of
key:value pairs separated by spaces or newlines. Passports are
separated by blank lines.”
The interesting part begins after line 3, where we are going to need
to get positions that are over the length of the row. The value that
we wish for row 4 is 1, which is the value of the remainder of
dividing 12 by the lenth of the track which is 11. Adding a new column
with the remainder we can crosscheck with our data and everything
seems to work:
In part one we need to check if a given character occurs between a
certain lower and upper bound.
This kind of operation seems to be more suited to be done in Power
Query as we are going row by row checking for the validity of the
rule. My idea here is to create a column with value of 1 if the
password is valid and 0 otherwise.
This will be the first post of a series where I hope to be able to
solve the problems from the Advent of Code using only Power BI.
This event, sadly, only came to my attention this year. It started in
2015 and it’s a lot of fun. In these posts I will talk about my
thinking and strategy to try and solve these problems.
⚠ WARNING: The content of this post has been made deprecated due to the availability of the official Google Sheets connector and you should use that feature to import the data. ⚠
Check the official announcement on the link below:
I’ve been tasked to find a way of exporting data from Google
Spreadsheets for a client. I’ve started researching for an already
working solution and got to the following links:
⚠ WARNING: The content of this post has been made deprecated due to the availability of composite models and you should use that awesome feature to import the data. ⚠
Check the official announcement on the link below:
This mode gives you syntax coloring and code completion inside Emacs.
It has all the functions listed by '#shared' and color codes them.
For more details on listing all Power Query functions you can check the
post
from RADACAD.
While working with some customers a few times this question came up: “How
can I diff my current file with a older one? I really want to compare
my files, to know what changed from one to another.”
Many many people working with Power BI end up with a directory full
of files looking like: “myPowerBIFileV1.pbix”,
“myPowerbifilev2.pbix”… “myPowerbifilevN.pbix”. The scenario wull
get worse if we have two or more people working in the same file, and
until recently my answer was always the same: “You can’t”.
Thanks to the contribution via GitHub from Hadi
Fadl there’s a new method available for
the flat file connection manager that adds the existing columns in the
source file. This is very handy because in the past you would have to
define each and every column that existed in the flat file.
I had a request to give an example of adding event handlers to a generated SSIS package. The code is quite convoluted. There’s no method to initialize a DtsEventHandler, you need to cast it after adding to the package with a String describing the type of event. Here’s a list of the available events:
Here’s a sample of how to do insert a ExecuteSQLTask to a event handler using a small console application: