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

KB31788: 'Maximum number of elements per selection' option in prompt editor does not work for 'Qualify on a attribute' prompt in MicroStrategy 9.4.1


Stefan Zepeda

Salesforce Solutions Architect • Strategy


KB31788: 'Maximum number of elements per selection' option in prompt editor does not work for 'Qualify on a attribute' prompt in MicroStrategy 9.4.1

SYMPTOM:
'Max number of elements per selection field' is a new prompt restriction option in Strategy Developer 9.4.1  for 'Qualify on a attribute' prompts. This option lets sets the maximum number of elements that a user can add to the prompt's attribute qualification. When the prompt is executed, a user cannot add more elements than this value if the In List or Not in List operator is chosen. When a value is entered for 'Max number of elements per selection field' in prompt editor for 'Qualify on a attribute' prompt , Strategy Desktop fails to check this prompt restriction.
 
STEPS TO REPRODUCE: 
 
 

  • Create a 'Qualify on a attribute' prompt on Category attribute. Set Max number of elements per selection = 2 as shown below:
     
ka02R000000kXH5QAM_0EM440000002EIK.jpeg
  • Create a report with Category attribute on the template and the prompt in the filter.
  • Execute the report. To answer the prompt
    • Qualify On :elements
    • Operator : In list
    •  Element list : choose more than 2 elements
  • Notice that it lets you choose more elements that the value set in the 'Maximum number of elements per selection' as shown below: 
     
ka02R000000kXH5QAM_0EM440000002EI9.jpeg

CAUSE:
This is a known issue and has been logged with Strategy Technology Department.
 
ACTION:
Contact Strategy Technical Support for an update on the issue.
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 19, 2017

Last Updated:

June 19, 2017