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

KB440619: Selector values are not getting passed on from one document to the other document/VI/report when by default all the elements of a selector is selected, using URL API


Community Admin

• Strategy


This Knowledge Base article describes how sector values appear to be not be passed in Visual Insight and the explanation of what the expected behavior is when running the outlined configuration.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.
[SYMPTOM]
Despite all the elements of a selector is selected, using URL API users will see that values are still not passed through Strategy reports, documents, and Visual Insights. 
[STEPS TO REPRODUCE]
The issue could be reproduced with Tutorial in Strategy 10.2, also was tested in 10.8 
1. Create a document with two selectors A & B (checkbox,listbox,drop-down selector) and a panelstack 
2. Inside the panelstack, add a HTML container which has the URL to point to a report/document/VI dashboard within the same project (make sure this target report/document/VI dashboard has a prompt built on top of the attribute used in the selector B) 
Support comments based on the test in house --> The issue could be reproduced using a text box, using an hyperlink 
For the test in house the following URL API was used. 
Main.aspx?evt=3140&src=Main.aspx.3140&documentID=D49BBB454C53478EB46BFB93737133D5&Server={&ServerName}&Project={&Project}&Port=0&share=1&elementspromptanswers={&subcategory@GUID};{&CurrentSelectionElementID:W78&} 
3. Edit Selector A and make the below settings 
a. Choose Selector B as the target 
b. Check the “Apply selections as a filter” checkbox if it is not already checked 
c. From the “Update target filters when current selection changes” dropdown choose “All” 
d. Uncheck “Show option for All” checkbox 
e. Click OK 
4. Edit Selector B and make the below settings 
a. Choose the panelstack as the target 
b. Check the “Apply selections as a filter” checkbox if it is not already checked 
c. Uncheck “Show option for All” checkbox 
d. Click OK 
** Note: With the test in house, the issue could be reproduced, setting or not what is mentioned from a-d. 
5. Save and run the dashboard 
6. Notice that all the elements in both the selectors are selected by default. 
Support comments based on the test in house --> this is not happening in house, in fact none of the elements is selected. 
7. Deselect few elements from the Selector A and notice that the elements in the Selector B are auto adjusted and the elements related to the deselected elements (in Selector A) won’t show up in Selector B 
Support comments based on the test in house --> this is expected because selector A is targeting Selector B. 
8. Click the hyperlink on the document and it opens the target report/document/VI dashboard and notice that the Selector B values are not getting passed on to the prompt in the target report/document/VI dashboard, instead the target report/document/VI dashboard displays the data for all the elements of the attribute used in selector B . 
9. Now go back to the original document, deselect and select any element from the Selector B and then Click the hyperlink 
10. Now notice that the elements of Selector B are getting passed on to the prompt in the target report/document/VI dashboard. 
[CAUSE]
1. Whatever we set "Update target filters when current selection changes" to "Unset" or "All", the elements on selector B are auto picked when client tries to get data from IServer. So there is no real selection on it. It is expected at this time if you directly click the link to open the prompt based dossier/document/VI and see all elements from the attribute in Selector B, since no element will be used to resolve the prompt. Elements are "dynamically" selected and can be changed at any time once selection of selector A is changed while link is passing the selections "statically". 
2. If a user manually selects some of the elements in Selector B, they can be passed to target dossier/document/VI because its concrete selections are saved in document definition that can be read in link. That is different from the above case. 
3. A possible workaround wout be to add another prompt in target dossier/document/VI based on Selector A, and pass the selection of Selector A in source document through link. In this case, the whole behavior is reasonable and logical. 
A sample URL would be like the one below, this is to run a VI and is passing 4 prompt to the target: 
Main.aspx?Server={&ServerName}&Project=Strategy+Tutorial&Port=0&evt=3140&src=Main.aspx.3140&documentID=0B2F4D234E44328A5323BE98B9D3E743&elementsPromptAnswers={&[Zip Code]@GUID};{&CurrentSelectionElementID:W51&},{&Customer@GUID};{&CurrentSelectionElementID:W53&},{&[Customer Region]@GUID};{&CurrentSelectionElementID:W55&},{&[Customer State]@GUID};{&CurrentSelectionElementID:W57&}
[ACTION]
This issue was reviewed by our Technology team for feasibility and will not be scoped for a code fix in any upcoming Strategy release. KB440619


Comment

0 comments

Details

Knowledge Article

Published:

April 18, 2018

Last Updated:

March 21, 2024