The following are steps needed to ensure you capture the migration in a separate log instead of in the DSS Error log, where it can get lost, mixed in with numerous other log entries.

To ensure the OM Log file is big enough to capture the entire migration, please perform the following steps BEFORE you start the OM migration.

1. Open MicroStrategy Administrator – Object Manager 9.x and select Tools > Object Manager Preferences, as shown below:

2. Click on the Events tab.
3. Click on the Configure Logging button (Note what is listed: To set up the Object Manager log, specify a new file or choose the default for the Source Manipulator dispatcher under the Component ‘Client Services’)

4. Find Client Services in the list

5. On the line for Source Manipulator, click in the box for Console log and in the last column, select New

6. Name the log using a standard (Obj_Migration_log or OMLog_env_date). If you create it for a specific date, you will need to remember to change the log name before your next migration or this is where ALL migrations will be logged to.
Change the file size to 10240kb (10mb) and leave the type as Diagnostics.

7. Click Save and Close so the log is created

8. You will now see that the log name is listed to be used for this migration

9. Click the SAVE icon at the top of the Configuration logging screen

10. Click OK to exit the preferences window

11. The default path to the object migration log is \Program Files\Common Files\MicroStrategy on the server/client you are working from.

12. Then open the source and destination project sources and perform the migration.
AFTER the migration is done and BEFORE you do any other migrations, you will want to change the log name unless you are ok with the next migration going into the same log. Once it hits the 10mb limit, it will start deleting lines from the previous migrations to make room for the newer ones.

Working as a team will also help you maintain perspective on the project. Sometimes taking a step back and looking at the work you’ve done is necessary. It’s very easy to put your head down and get immersed in the project and lose the big picture. Working as a team helps with this problem. Ask yourself:

     Does the dashboard meet business objectives?
     Can users navigate effectively?
     Is design assistance required?

As with all facets of Business Intelligence, a team approach generally yields the best results. Dashboard design is about aligning the business around a common set of metrics and objectives, so it’s natural to involve many players throughout its development.

Creating a dashboard is a process, not a single event. There will be multiple iterations throughout its lifecycle. Embrace constructive feedback openly and don’t hesitate to speak out when additional resources are required.

Survival in Numbers

• Learn how users will interact with the dashboard, and tailor functionality to their needs.
• Ask peers to weigh in on designs and test drive prototypes. Early feedback can save hours of rework.
• Consult a graphic design professional for layout recommendations or hands-on assistance. There’s no substitute for experienced input.

That wraps up our Dashboard Survival series. I hope you found it informative and I hope it helps you in your own dashboard development. These are techniques we’ve put into practice over and over again, here at Lancet. We have experienced Dashboard Design experts and BI Architects that can help you in your dashboard development.

If you haven’t yet, please download your very own copy of our Dashboard Survival Guide.

Selecting the right visual to display a data set can be tricky, as it significantly impacts how readily users can absorb the information at hand. If in doubt, mock up your data in several different configurations and color schemes, and compare the results side by side.

The Bare Necessities

• Choose a color scheme with just enough contrast to make each variable stand out. Avoid jarring colors and monochromatic shading.
• Balance variety with appropriateness when selecting among line and bar graphs, pie charts, gauges and thermometers, heat maps and other options. Refer to the examples on page 18 of our Dashboard Survival Guide for choosing optimal visualizations.

Powerful dashboards incorporate great design. However, great design should be subtle. Your color, image and layout choices should support the user’s goals, not distract from them. One of the most common dashboard mistakes is failure to highlight what’s important – the data. Review your finished product with a critical eye. Don’t be afraid to edit.

The Bare Necessities

• Avoid design elements that don’t have a purpose. Less is more in design.
• Be sure the image is subtle if using a photo or graphic as the background to the dashboard.
• Try single colors in charts. Use a mix of font weights to emphasize information.

Studies prove that we approach information in a familiar pattern, moving left to right and top to bottom. For dashboard designers, that means the upper left corner should house the most important information, with critical components flowing in order of proximity.

Use Your Head

• Make sure Key Performance Indicators (KPIs) for the dashboard are located in the top left corner.
• Group like displays of information together to speed readability, such as grids in one area and charts in another.
• Place non-essential items like dashboard names, company logos and instructional text where they are visible to users, but don’t detract from prominent areas of the screen.

When we do the math on successful dashboards, it all adds up to one: one dashboard that fits on one screen with just one focus on each tab. Work with your business leaders to prioritize information and define the most critical material you need to present. A cluttered presentation that’s overloaded with information defeats the purpose of the dashboard and will reduce usability.

Stay on the Trail

• Group closely related information together so users don’t need to flip between tabs.
• Optimize your space by showing summary data on the main tab and using drill-downs so users can access details as needed.
• Set up your content so that it fits on one tab, without scrolling. Test on multiple browsers and devices.

The fifth survival tip involves you making sure you maximize what little space you have in your dashboard. Dashboard canvas sizes are usually pretty limited, so you need to make the most out of what space you have. Ask yourself:

    How much detail is absolutely essential?
    What is the primary focus?
    Can multiple items be served with one label or menu?

Great dashboards mind the details. Once you’ve mocked up your visual presentation, take time to review and tighten up each individual element. Every unnecessary decimal place, every redundant menu choice or oversized font is an opportunity to optimize your onscreen real estate.

Survival Rations

• Truncate figures to the shortest suitable format, such as displaying decimal places to tenths rather than thousandths, or showing data by quarters rather than months.
• Keep text as small as possible while maintaining legibility. Size fonts from 8-11 points, including heads and sub-heads.
• Minimize or eliminate the company name and logo or move it to a page footer.
• Consider a consolidated menu bar that can serve all elements onscreen, rather than individual menus for each chart or diagram.

Try to maintain a consistent structure from one dashboard to the next. This subconsciously trains users where to find the information and what to expect from the BI process.

    Can users of all levels find information quickly and intuitively?
    Are menu choices and drill-down options obvious?
    Is information logically structured and clearly labeled?

If one word could describe a great dashboard, it might be “intuitive.” A well-architected dashboard doesn’t require a user manual or a training session. It should present volumes of information at a glance, enable business users to monitor performance and make data-supported decisions – all from a single screen. Understand how your business leaders make decisions and you can engineer the optimal presentation for their needs.

Follow Your Instincts

• Review dashboard navigation and make sure it follows standard conventions, such as underlining hyperlinks.
• Check graphs, charts and grids for easy to follow titles and captions; avoid acronyms and jargon.
• Evaluate overall presentation of information so key items, like alerts, are readily apparent to even casual users.
• Maintain a consistent structure across every dashboard to train users where to go and what to expect.

Customer reported that a dashboard I built several months back was suddenly missing metrics. The dashboard in question is a very large MicroStrategy report with quite a few metrics identified by the business team. I have not made any modifications to the reports/dashboard in months so I was curious why the metrics would have suddenly been removed from the dashboard.

So today I connected to their site and first edited the dashboard via Desktop – and low and behold the metrics are all still there! I then ran the dashboard via Web and the metrics were also visible. I emailed the customer and asked him if I was missing something. He opened the current MHT file from his machine and indicated that the metrics are being chopped off the report.

Here’s where it gets interesting. While on the phone with him, I had him save the same MHT file to the Web server machine and open it from there. When he does, all metrics are visible and nothing is chopped off. However, when he opens the exact same MHT file on his own local machine, the metrics are being chopped off.

The Solution:

When we viewed the file on the Web & I-Server it was fine, when I viewed it on my PC it was fine, but everyone else reported the problem. After some trial and error I discovered that the problem was tied to the version of Adobe Flash ActiveX they were running on each PC. The hypothesis was that the I-Server is running version 10.1.102.64, I am running 10.2.153.1 and I could read the file in its entirety whereas the users were running 10.0.32.18 (an earlier version than the I-Server) and couldn’t. They updated their local version and now they are able to see all columns on all reports.

Our respondents utilize one or more of the following resources, with the majority of organizations relying on in-house staff:

• In-house development team
• In-house MicroStrategy administrator
• Independent contractor
• Outside consulting firm
• MicroStrategy partner

Administration Options

Whether you assign a dedicated administrator, or split responsibilities across several people or departments, there are pros and cons to each approach.

• Dedicated administration clarifies responsibilities with a single “go to” person, but can leave the organization short-handed in peak periods, or with unnecessary interruptions when the administrator is ill or takes vacation.
• Sharing administration adds bandwidth, and helps companies comply with regulations that require segregation of duties—but it can be challenging to balance administration responsibilities with other IT projects, often short-changing the BI platform. Part-time administrators may also lack the specialized skills necessary for more sophisticated trouble-shooting.

A third option that is gaining traction is a blended approach that outsources all or a portion of day-to-day administrative functions . This combination offers constant availability and specialized skills from external resources, and enables in-house developers to attack higher value projects and core business activities.

However you choose to manage platform administration, face the opportunities and the challenges head-on, so you’re prepared to handle whatever issues may arise.