As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
1) Can someone confirm this for version 7703. 2) Anyone know of a work around? 3) Is this fixed in version 8.
Situation: Create a fex with a SINGLE value prompt for a string data type. Apply WHERE condition using the parameter. Can you confirm that you must put single quotes around the amper parameter used in the WHERE condition. It only seems to work in this manner. Example:
-SET &SPECIALTY = &IDXSPECIALTY.(FIND TBL_VAR.TBL_VAR.IDXSPECIALTY,TBL_VAR.TBL_VAR.IDXSPECIALTY IN TBL_VAR).Select Specialty; . . . WHERE TBL_VAR.TBL_VAR.IDXSPECIALTY EQ '&IDXSPECIALTY';
Please confirm that if you change the prompt to a multi select (OR) now you must go into the WHERE statement and REMOVE the single quotes around the amper parameter since the multi select (OR) appears to add a set of quotes itself. Failure to do so yeilds two sets of single quotes and an error.
Is there a way around this?This message has been edited. Last edited by: Tamra,
I think this might be a case of expecting the text editor to autocomplete your syntax?
Liken it to using a function where the last parameter is normally the format or the field to which the result is placed. e.g. NEWFIELD/A4 = GETTOK(SOURCE_FIELD, 255, 1, ' ', 4, 'A4'); If you changed the A4 to the field name would you expect the quotes to be removed for you - or vice versa? Ok, not exactly the same but you get my point?
If you create your filter through the GUI then you will see that, for a single select, quotes are placed around the variable filter e.g. '&COUNTRY.(FIND CAR.ORIGIN.COUNTRY IN CAR).COUNTRY:.'
However, when changing that to a multi select OR then the quotes are removed e.g. &COUNTRY.(OR(FIND CAR.ORIGIN.COUNTRY IN CAR)).COUNTRY:.
I would venture the argument that, if you wish to manually code then you have to follow the correct rules as you are responsible for using the correct syntax.
So - 1) I would expect that to be the case. 2) Yes, if you change the operation then expect to have to use the correct syntax. 3) It is working correctly.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
Posts: 5694 | Location: United Kingdom | Registered: April 08, 2004
Interestingly, the HTML Layout Composer now has the option to have or not have quotes around multi-select values, so it's great for when you want to choose whether to treat them as numeric/alpha or when you want to use it for other stuff besides a WHERE condition.
(Didn't notice this in 7.6.4, I don't think it was an option then).