EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB313376: How to use the search function in Visual Insight in a highly controlled environment in MicroStrategy 10.2


Community Admin

• Strategy


The issue described in this document addresses a situation where the ability to use the search function in Visual Insight is needed in a highly controlled environment. This document will describe how a metric can be hidden from the browse and search functions in Visual Insight, but still be able to be used in an Intelligent Cube.

SUMMARY:
The issue described in this document addresses a situation where the ability to use the search function in Visual Insight is needed in a highly controlled environment. This document will describe how a metric can be hidden from the browse and search functions in Visual Insight, but still be able to be used in an Intelligent Cube.
 
A workaround is provided at the end of the technical note.
 
REQUIREMENT:
Administrator wants to be able to release the search functionality in Visual Insight so that end users are able to pick up any metric or attribute in a controlled environment. In this scenario, the administrator wants to be able to include metrics into an Intelligent Cube and have users be able to see and use them from the cube, but not be able to search or browse them from within Visual Insight.
 
PROBLEM:
In Strategy 10.x, after disabling the Browse ACL to a metric, users are not able to browse or search for that metric within Visual Insight nor are able to see or use the metric within a cube.
 
STEPS TO REPRODUCE:
 

  1. With Browse enabled to Profit metric, search in Visual Insight for profit
  2. Create a user with the Web Reporter, Web Analyst, Web Professional and Common Privileges allowed for the Tutorial Project.

 

ka04W000000OftWQAS_0EM4400000025Si.jpeg

 

  1. Now let’s that say that an administrator wants end users to have a schema restriction such as every time that users add the metric “Profit Browse Deny” users will have to add the attribute Category attribute otherwise the “Profit Browse Deny” metric won’t work correctly. To accomplish this, create an Intelligent Cube with the “Profit Browse Deny” metric and the “Category” attribute and save the cube as Cube Profit Deny

 

ka04W000000OftWQAS_0EM4400000025Sp.jpeg

 

  1. Since the metric “Profit Browse Deny” can’t be used in just any dataset, the administrator doesn’t want end users to be able to search for it. Thus, disable the Browse Privilege for the user 115576.

 

ka04W000000OftWQAS_0EM4400000025SS.jpeg

 

  1. Login to Web with the 115576 user and search for the metric “Profit Browse Deny”. Notice no search results are returned as expected.

 

ka04W000000OftWQAS_0EM4400000025SP.jpeg

 

  • However the Administrator still requires the end users to be able to use the metric in the appropriate dataset. Add the Intelligence Cube dataset “Cube Profit Deny”. The user expects to see the “Profit Browse Deny” metric and the “Category” attribute displayed.
ka04W000000OftWQAS_0EM4400000025SI.jpeg

 
“Profit Browse Deny” is not displayed.
 

ka04W000000OftWQAS_0EM4400000025Sn.jpeg

 

  1. In Developer, allow Browse ACL to the “Profit Browse Deny” metric.

 

ka04W000000OftWQAS_0EM4400000025Sk.jpeg

 

  1. In Visual Insight Dashboard, notice when the “Cube Profit Deny” cube is added, “Profit Browse Deny” is displayed.

 

ka04W000000OftWQAS_0EM4400000025SK.jpeg

 

  1. However, if the user searches for the metric in All Objects panel, the metric is also displayed which the Administrator doesn’t want to allow.

 

ka04W000000OftWQAS_0EM4400000025Sm.jpeg

 
CAUSE:
This is working as designed as the Browse ACL is required to see and use metrics in a cube and give browse and search access to those metrics.
 
WORKAROUND:
 

  1. On the Metric, grant the Browse, Read, Control Use, and Execute ACLs.

 

ka04W000000OftWQAS_0EM4400000025So.jpeg

 

  1. Hide the metric(s) users don’t want to see in search.

 

ka04W000000OftWQAS_0EM4400000025SN.jpeg

 

  1. Create a cube that contains the metric that has been hidden and was granted the ACLs.

 

ka04W000000OftWQAS_0EM4400000025SJ.jpeg

 

  1. In Web, create a new dashboard and add existing dataset (the cube which was just created).

 

ka04W000000OftWQAS_0EM4400000025Sj.jpeg
  1. Notice that you can see the metric on the left hand side and use this metric with no issues.

 

ka04W000000OftWQAS_0EM4400000025Sl.jpeg

 

  1. Remove the cube from the dashboard and try to search for the same metric we just used in the cube. Notice there are no search results and in addition, you can’t browse to the metric through the folder structure.

 

ka04W000000OftWQAS_0EM4400000025Sg.jpeg
ka04W000000OftWQAS_0EM4400000025SO.jpeg
ka04W000000OftWQAS_0EM4400000025SO.jpeg

 


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

June 8, 2017