Exploring, modeling, predicting and reporting with SAS Visual Analytics and SAS Visual Statistics

Using Text search

Accepted Solution Solved
Reply
Contributor
Posts: 59
Accepted Solution

Using Text search

VA 7.3 on windows

i have a table where one of the fields is a 2000 character customer comment.

we wish to search comments via a text filter box and show all the comments that match a word or phrase such as "manager" or "prime rib" but this does not work as expected.

 

i would expect to drop a text search box on the designer and then drop the customer comment field on the box.

this works but of course comes up with too much data if used as a report filter.  instead of dropping the box on the report filter section, i have it now placed in the designer area where the user must first use the report filters top subset the comments.  this in turn filters the comment box.

 

however, this is where the problems begin,  the text search box is NOT a text search box at all. if you type a word in the box, ALL comments with that word appear in the drop down and you are forced to click on one of the entries in the drop down.  which in turn simply displays one record in the list table object. plus because the comment field is 2000 characters, the screen becomes totally unreadable due to the system attempting to resize all screen objects because it wants the text filter box to be 2000 characters wide.

 

the purpose here is to simply show ALL ocomment records with the word "manager" 

any ideas how to do this?

 

thanks

 


Accepted Solutions
Solution
‎07-11-2016 01:19 PM
Contributor
Posts: 59

Re: Using Text search

found an older post with the answer....

 

Re: Fitlering a text field if it contains a specific word[ New ]

Hi Alex,

 

As you said, an on-report keyword search filter would require a filter expression created in the designer, and the keyword couldn't be modified by report consumers in the current and previous releases of Visual Analytics.  However, in the upcoming 7.1 release, targeted for this fall, you will have a new parameterization capability that will enable you to create a filter control that uses additional operators, such as contains, startswith, endswith, etc.  Essentially, you'll be able to create numeric and character parameters and use them in both filter and calculation expressions, among other things, and associate a parameter with input controls that you place on the report for viewers to change.  To meet your text search filter requirement for report consumers in 7.1, you first create a parameter in the designer, and then a filter expression that references this parameter.  Then, you associate that parameter with an input control, like the text input control.  Not only does this allow you to use operators other than equality for report consumer filter selections, a parameterized filter expression allows you to have multiple filter controls that are ORed.  As you likely know, multiple on-report filter controls in the viewer are implicitly ANDed in 6.4 and prior releases.

 

Alex, I hope this helps.

 

Rick Styll

View solution in original post


All Replies
Solution
‎07-11-2016 01:19 PM
Contributor
Posts: 59

Re: Using Text search

found an older post with the answer....

 

Re: Fitlering a text field if it contains a specific word[ New ]

Hi Alex,

 

As you said, an on-report keyword search filter would require a filter expression created in the designer, and the keyword couldn't be modified by report consumers in the current and previous releases of Visual Analytics.  However, in the upcoming 7.1 release, targeted for this fall, you will have a new parameterization capability that will enable you to create a filter control that uses additional operators, such as contains, startswith, endswith, etc.  Essentially, you'll be able to create numeric and character parameters and use them in both filter and calculation expressions, among other things, and associate a parameter with input controls that you place on the report for viewers to change.  To meet your text search filter requirement for report consumers in 7.1, you first create a parameter in the designer, and then a filter expression that references this parameter.  Then, you associate that parameter with an input control, like the text input control.  Not only does this allow you to use operators other than equality for report consumer filter selections, a parameterized filter expression allows you to have multiple filter controls that are ORed.  As you likely know, multiple on-report filter controls in the viewer are implicitly ANDed in 6.4 and prior releases.

 

Alex, I hope this helps.

 

Rick Styll

Post a Question
Discussion Stats
  • 1 reply
  • 370 views
  • 1 like
  • 1 in conversation