I am obviously passionate about Alteryx, being one of its creators, but I am equally passionate about cycling in general, and Colorado in particular. Now that I have subscribers from all over the world on this blog, I think its time to show off this amazing state of Colorado.
A few years back, we mentioned a open source YXDB reader/writer on LinkedIn. After that, a whole lot of nothing. It turns out that Alteryx did release the open source YXDB code, but it was so stealth that no one noticed. This code is used inside of an R plugin, which had to be GPL’s because of R’s licence. But since it was never published as a way to read/write YXDBs, no one noticed.
The thread on LinkedIn was recently revived, so I decided it was time to expose it to a bigger audience.
The bike industry, like any other, has repeated fads that are designed to separate us consumers from our money. The latest fad is fat bikes – bikes with tires greater than 4″ wide tires. The original idea was a bike that you could ride on snow. I guess it was invented by crazy cyclists in Alaska or something. The hype though goes far beyond riding in the snow – people kept telling me how amazing the big tires are on dry land as well. Continue reading
Sometimes you need to look back in order to look forwards. Sometimes its just nostalgia. While we are hard at work in Boulder designing and building Alteryx 10.0, I thought it would be interesting to go back to where it all started. Continue reading
A few people have been using the macro I wrote about in Alteryx: Wildcard Inputs, but have an issue with XLSX files. The first thing to remember is that these macros I post (on my personal blog) are examples only and are not a supported part of the product. I am happy to give people advice on how they might take what I did and extend it. However, in this case, I thought it might make a good post about Alteryx macros with optional parameters, so I went ahead and did it anyway. Continue reading
One of the really great strengths of Alteryx is that is can handle any amount of data that you throw at it. If your data is small enough, it might all be in memory, but when Alteryx gets more data than fits, it silently swaps out to disk. This way people are routinely processing data sets that are 2, 10 or even 100 times bigger than they have enough memory for!
Mostly the user never notices this aspect of the Alteryx engine and it just works. There are times though when we get feature requests that would be much easier to implement if all the data was in memory. One example of that is aggregate functions in the formula tool. Since other desktop products that are similarly easy to use, like Tableau and Excel, have simple SUM and AVG type functions in their formulas, it is assumed that Alteryx would too. Continue reading