Today’s post is the last in a series of three reviewing our top 15 most popular blog posts covering a number of IBM Planning Analytics Tips & Tricks and the benefits of migrating from TM1.
Read this post to learn how to easily control your logs, while also making them easier to navigate. Your TM1 server tracks data transactions made in the system. When a cube value is changed, TM1 records the change in a transaction log file named Tm1s.log. The values in the log can be used as an audit trail and can also be used as part of a data restoration approach in the event of a server crash. While logging is a great auditing tool and an excellent point of reference, these logs can quickly become large and hard to navigate. This post shows you various ways to control your logging approach and offers some recommendations on when to disable it.
IBM Planning Analytics Workspace (PAW) allows you to visualize your data using a variety of charts and graphs, including the ability to display your results via a map. The only requirement for mapping is to ensure that your geography dimension includes recognizable place names. IBM defines “recognizable” to include items such as countries, states and provinces and offers a list of acceptable items on their website. Read this post to learn the three easy steps for creating a map in PAW.
You can use MDX to easily update a cube value to control the period elements that will display in a subset used in views. This blog post details a scenario on why you may need to do this, and then how to do it.
Here’s the challenge: It’s the end of a quarter and the VP of Sales wants to look at the projected financials for her department. You’ve already built a view that she can open to see the financials, but you just remembered that you forgot to change the period subset to display this quarter’s results. You’ve also just received an email notification from an annoyed VP of Sales. Despite the quarterly reminders that you’ve set for yourself, you forgot to update the default views in various cubes to reflect the current quarter’s plan.
This blog will show you a solution that will allow you to simply update a cube value to control the period elements that will display in a subset used in views.
There are easy ways to address resource issues in order to have a finely tuned IBM Planning Analytics environment. This is the second in a two-part series about monitoring the performance of your server to maintain a working TM1 system. In the first post, we reviewed several methods for monitoring the resources available on your system. Here, I’ll go over some ways to address resource issues you may see. Whether you notice a problem related to CPU, RAM, or disk space, there are short-term and long-term solutions for each.
There are many sample files available for Cognos Analytics. In order to better experience and understand new features in releases of Cognos Analytics, it is recommended that you install the sample databases, models, dashboards and reports.
Installing the samples involves the following four steps:
- Installing the samples
- Importing the sample content from its archive
- Restoring the sample databases from backups
- Creating data source connections in Cognos Analytics to the databases
In this blog post, we will setup the Go Sales and Go Sales Warehouse samples and restore the databases into Microsoft SQL Server.
Thanks for reading the final installment of our Top 15 IBM Planning Analytics Tips & Tricks of 2018. Missed the earlier posts on our Top 15 blogs? Click through to read the first in the series, covering posts 15 – 11 and the second, covering posts 10 – 6. We publish a new IBM Planning Analytics/TM1 tip every Tuesday morning so please come back an visit our Knowledge Center again.