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.
I'm trying to parameterize the database name for use in calling a MSSQL stored proc:
SQL SQLMSS EX &&DBNAME.dbo.spMyProc;
I have set the &&DBNAME = 'HEPBIDEV'. WF, clever as it is, interprets the period as a WF format and concatenation and says "Could not find stored procedure 'HEPBIDEVspMyProc'. How can I avoid the concat?
well, that's one way to do it, but you'd have to add a parameter to every stored procedure to know if it's a test db or prod. i'd rather change my WF code instead of every SP. I've been able to do it like this: -SET &proc = &&DBNAME | '.dbo.spMyProc' SQL EX &proc;