Logical View columns have GUID :-D

My friend told showed me something that was kinda unbelievable. He had column REPORT_ID in 4 tables and had created 2 Logical views in MicroStrategy that also have a column named REPORT_ID. We he tried to create a new attribute based on this column REPORT_ID, MicroStrategy logical views were not getting listed as the source table 😕 . After much finding, I came to know that it is as per design. The example in the tech-note is about fact, but same issue also occurs for attributes.

If the column name is added manually via typing, it will have a different ID than the original column.

Wooof. Something never ever thought. I thought that column must be getting mapped, but no, there are GUIDs for each column too. If typed manually, there would be a new GUID created for the column in the Logical View. So, even if there are column with same names Logical View won’t get listed as Source table.

As per the tech-note: Select the desired column from the existing tables in the Warehouse Catalog, and drag it over to the Column Object.

Some nifty information about Logical Views:

  1. Logical views are embedded in the SQL as either derived tables (also known as in-line views) or common table expressions.
  2. A derived table is an independent SELECT statement that appears enclosed in parentheses in the FROM clause.
  3. Logical view produces a virtual table in the database.
  4. The column objects are matched to columns returned by the SQL statement by name, not by position. It matters only that the columns are defined and that the SQL statement provides an unambiguous name for each column. This is in contrast to a MicroStrategy Freeform SQL report, in which result columns coming back from the query are mapped onto report objects by position.The difference is that in a logical view, the mapping takes place entirely on the database, while in a Freeform SQL report, MicroStrategy has to interpret the dataset coming back from the database.
  5. The order of columns in a logical view definition cannot be changed permanently (A partial defect as the function is not as user would expect but this doesn’t add any issue in the SQL generated)

Stumbled upon this nice tech-note about Physical Modeling using Multi Source while finding information about Logical Views.

Data restriction using Security Filter

Take following scenario. You have three attributes. Region -> Market -> Country. (I know, spelling are pretty bad)

Geography Hierarchy

Geography Hierarchy

I had implemented Security Filter at Country level several time and explained to several friends about how to do it. But I never came across a scenario when I had to do it at Market level or Region level, i.e., not the lowest level of hierarchy.

Take a scenario, when you have put security filter for the User Group, who have been provided access to only South Asia Market runs a report containing Country attributes or someone with EMEA Region access runs a report with Market attribute. What would happen? Do you think that someone with South Asia Market would be able to see only India and/or Srilanka or someone restricted to APAC can’t see Middle East Market or Panama Country?

I know the half answer. There are so many possibilities. Hope to completely post by Month end.

MicroStrategy 9 Live Roadshow! Now in India

Upcoming Roadshows in India

During this live event, you’ll learn about exciting new technology and capabilities designed to:

  • Graphically display the key information about your business
  • Provide interactive analysis to better understand your business challenges and opportunities
  • Dramatically increase the speed and simplicity of deploying new BI capabilities
  • Empower business users with extensive self-service capabilities
  • Extend the scale, performance, and efficiency of your BI solutions

Roadshow Agenda

6:15 -6:30 PM

Registration

6:30 – 9:30 PM

Welcome and Introduction to MicroStrategy

How Information Creates Competitive Advantage

Customer Presentation

MicroStrategy & Sybase Joint Value

Extending the Boundaries of BI

9:30 – 10:30 PM

Dinner

Note: Schedules may vary slightly.

Technology Partner: Sybase

Roadshow Sponsors:  InfoCepts, InfoSTEP, Lunexa, OBSI, Systech

To Register: MicroStrategy 9 Roadshows in India or the links above.

Make sure you write MicroStrategy101 for How did you hear about this event? in Registration form.