(After a long gap, a short post)
When running a (Saved with default answers) Ad hoc report that has been re-prompted, the metrics on the resulting report will be displayed in alphabetical order rather than in the order they were selected.
A possible workaround to this issue is to click and highlight one of the selected metrics , then re-execute the report.
As usual, we are touch base with MicroStrategy (its known issue in 9x, please contact MicroStrategy Tech Support 😛 )
MicroStrategy 9 Release 2 (9.0.1 products) is now available on the download site.
What are the new features in MSTR 9 R2 (9.0.1)
1) Jump Start Project
2) MicroStrategy Health Center
1) JUMP-START PROJECT
What is the Jump-Start Project?
Jump-Start is a complete MicroStrategy project that comes with 7 dashboards and 30 reports and all the underlying metrics, filters, attributes, and dimensions. All you have to do is add data and rewire. It was designed with one purpose in mind – to help you develop a complete MicroStrategy Project FAST!
How does Jump-Start Work?
MicroStrategy’s Jump-Start Project provides the standard building blocks of any project, attributes and facts, and uses those objects to create application objects such as metrics, filters, reports, enterprise documents, and dashboards. Because a specific project has yet to be defined, all of these objects use generic names as placeholders. You redefine/rewire the attributes and facts so that they work off your data tables, and due to the object oriented design of MicroStrategy, the data will be cascaded into the pre-built reports and dashboards automatically. With all this work prebuilt, the Jump-Start project delivers a complete BI project in a matter of a few hours
Manuals are available in MicroStrategy site.
2) MicroStrategy Health Center
MicroStrategy Health Center allows users to prevent, diagnose and fix problems in a MicroStrategy system. It detects known problems and provides an immediate solution to many of them.
Health Center can email a system administrator if it encounters a problem with the system. In cases where Health Center cannot fix a problem immediately, it enables users to bundle relevant system information, such as log files, into a diagnostic package and transmit the package to MicroStrategy Technical Support for review and troubleshooting.
Source: MicroStrategy’s Technical Email
Issue: Not able to add tables/views to the Schema in Warehouse Catalog
Error: ‘Error adding Table(s) to the schema. This key is already associated with an element of this collection’
Solution in MSTR 9:
1) Open ‘Architect’,
2) Right click the table <table name>
3) Add to the project
4) once its added, Right table in Left Pane and update structure
5) Save and close (it will ask for Update Schema, so do the same
6) Now open Warehouse Catalog
7) you can see the table/view added to schema
After long gap posting ‘Object Tracking Tool’ with some updates.
1) The tool tested in system where I-Server is installed (not got a chance to test without I-Server)
2) Tested in XP,2003,Vista, 7
3) For those testing using Tutorial; the object ID for some objects may looks like same…but actually there is one number difference between each ID. Don’t assume that its repeating the same ID.
4) Any suggestions/Comments are welcome
Note: Soon the tool will be integrated with some other tool also.
Download the tool here.
Note: This application is provided “as is” and I disclaim all warranties, whether express or implied, with respect to all provided items, including all warranties of merchantability, fitness for a particular purpose, accuracy, systems integration, title, satisfactory quality and non-infringement. I do not warrant that use of the provided items or any portion thereof will be uninterrupted or error-free, or that the provided items or any portion thereof will meet any need or requirement of licensee.
In MSTR 9, there is a new feature called Multisource where user can connect Multiple DB instance.
We used the same and due to new license model we are forced to change back to single DB instance. So we pointed all DB instance to same ODBC connection (logically its one DB connection)
Issue: Even though all DB instance pointing to same ODBC, MSTR considering that as multiple DB instance. So when user without Multisource license login to the MSTR and try to run any report, it throws an error saying that ‘this is requires multisource license’. Interesting thing is, the tables for that report are coming from single DB instance.
Solution: It’s become critical issue during SIT due to client’s license changes…blah….blah.
Took bit risk option and also that’s the only solution…Changing DB Instance for all attributes in Metadata tables. (Alternate option, edit all attributes and change the table pointing to single DB instance which is huge task – [400 attributes].
Did some analysis on MD tables, relationships, etc…I changed the all DB instance 32 bit ID to single DB instance 32 bit ID (need to be very careful while deleting the rows, changing the column values in the Metadata DB.
I’m still doing documentation on changing DB instance in Metadata directly and along with that planning to document or new tool for “‘find and replace object in any definition”.
If anyone come cross this kind of issues like ‘Object ID cannot be found’ and also issues like SCANMD, DOCTOR MD not able to resolve, Will try to help you to fix the same.
Soon will post the document and tool for the same……