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

KB35314: How to qualify on an attribute element that contains a special character that is interpreted as a wildcard in MicroStrategy Web


Community Admin

• Strategy


This article notes how to handle filters containing string wildcard characters

In Strategy Web, when creating a filter on an attribute element or any other object whose name contains characters such as *, the Strategy SQL Engine interprets that character as a wildcard and the SQL returned will appear as shown below:
 

ka04W000000OcAUQA0_0EM440000002DrB.png

 
The asterisk character (*) is considered as a wildcard when the SQL is generated:
 
select a11.[ITEM_ID] AS ITEM_ID,
max(a12.[ITEM_NAME]) AS ITEM_NAME0,
sum(a11.[TOT_COST]) AS COST
from [ITEM_MNTH_SLS] a11,
[LU_ITEM] a12
where a11.[ITEM_ID] = a12.[ITEM_ID]
and a12.[ITEM_LONG_DESC] like '%%TEST%%'
group by a11.[ITEM_ID]  
 
To prevent this from happening, configure the report filter with the special character repeated as shown below:
 

ka04W000000OcAUQA0_0EM440000002DrD.png

 
The filter now works as expected:
 
select a11.[ITEM_ID] AS ITEM_ID,
max(a12.[ITEM_NAME]) AS ITEM_NAME0,
sum(a11.[TOT_COST]) AS COST
from [ITEM_MNTH_SLS] a11,
[LU_ITEM] a12
where a11.[ITEM_ID] = a12.[ITEM_ID]
and a12.[ITEM_LONG_DESC] like '%*TEST*%'
group by a11.[ITEM_ID]  
 
Further Reading
 
KB6893: How to qualify on an element whose name contains a symbol usually interpreted as a wildcard in Strategy Developer 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

May 22, 2017

Last Updated:

May 22, 2017