Bryan Brandow (photo, right), a Data Engineering Manager for a large social media company, is one of my favorite bloggers out their in regards to thought leadership and digging deep into the technical aspects of Tableau and MicroStrategy. Bryan just blogged about triggering cubes and extracts on his blog. Here is a brief synopsis.
One of the functions that never seems to be included in BI tools is an easy way to kick off an application cache job once your ETL is finished. MicroStrategy’s Cubes and Tableau’s Extracts both rely on manual or time based refresh schedules, but this leaves you in a position where your data will land in the database and you’ll either have a large gap before the dashboard is updated or you’ll be refreshing constantly and wasting lots of system resources. They both come with command line tools for kicking off a refresh, but then it’s up to you to figure out how to link your ETL jobs to call these commands. What follows is a solution that works in my environment and will probably work for yours as well. There are of course a lot of ways for your ETL tool to tell your BI tool that it’s time to refresh a cache, but this is my take on it. You won’t find a download-and-install software package here since everyone’s environment is different, but you will find ample blueprints and examples for how to build your own for your platform and for whatever BI tool you use (from what I’ve observed, this setup is fairly common). Trigger was first demoed at the Tableau Conference 2014. You can jump to the Trigger demo here.
I recommend you click on the link above and give his blog post a full read. It is well worth it.
Here is a link to the MicroStrategy vs. Tableau post.
I have some good news to share with you.
Bryan Brandow, a Data Engineering Manager, has started (or perhaps restarted) blogging again. His new blog is called Bryan’s BI Blog and the first post is a must read. It is titled Evolving BI and Bryan shares his latest adventures, his thoughts on the current state of BI as he has observed and experienced it, and where he feels we collectively need to go.
Bryan has also migrated all of his old MicroStrategy Blog posts to this blog site and I encourage you to read these as well.
Here is a link to the Evolving BI post.
Here is another blog re-post from my friend, Bryan Brandow’s MicroStrategy site.
If you want to directly visit Bryan old site, the URL is http://www.bryanbrandow.com.
Bryan originally posted this on July 22, 2011.
Removing Sections of a Report via URL API
While working with the Web SDK to try to make a small customization, I stumbled on a pretty useful set of URL API codes that allow you to quickly modify the Report Page by removing various elements. While such customizations are common, I wasn’t aware that they were available out of the box. I would think that these would be very useful in doing simple linking to reports via an IFrame from another application, such as a Portal.
The trick to get the URL for a Report by right clicking it in Web, choosing Properties, and then copying the Link at the bottom. Now, locate the src section of the URL:
and add in one of the transforms just before the .4001.
Available transforms that I’ve found:
Unfortunately, these are actual transforms and not flags, so you can’t mix and match to fit your needs (for example, if you only want to hide the toolbar, reportNoToolbar will NOT work). Those are the only 4 that you can use that I’ve found, but they may be handy in a pinch and best of all, not require customization work to use.
Another method of doing this that does let you pick and choose and supports documents as well:
Place that code in the URL, for example (Note: I have shown this on multiple lines. You should paste this in as one long line with no line breaks):
List of options (case-sensitive):
Bryan’s Blog Entry Link: http://www.bryanbrandow.com/2011/07/removing-sections-of-report-via-url-api.html
I have been kicking around the idea for this blog for several years now. Last year, I started my data visualization blog and find it very fulfilling. However, I have wanted a blog focused on and devoted to the MicroStrategy platform. In the past, I have relied on Bryan Brandow’s excellent MicroStrategy blog, but I believe with Bryan’s work commitments and other things, he has been too busy to blog. I can only hope to produce the quality of blogs that Bryan did.