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.
Recently we migrated from 8104 to 8105 and suddenly all the launch pages which were working perfectly in 8104 started throwing ‘Error retrieving data for control’ for each of the controls on the launch page, before getting the ‘Done Populating’ message at the bottom of the page.
It looks like it is also taking more time in loading due to this. Did anyone else have seen such issue in past. Any suggestion is highly appreciable.
Thanks, Pravin SinghThis message has been edited. Last edited by: <Emily McAllister>,
WebFOCUS 7703 Windows, All Outputs pravinsinghwebfocus.blogspot.com
We saw the same thing as we are in process of re-writing our older HTML’s and trying to complete them in HTML Composer. We have a lot of Hidden Input controls that did not have assigned values. We ended up removing those that didn’t have values as we had like 30 of them causing the page to take like 15 seconds pre-load and it would cycle through what you are describing above. What we ended up doing is assigning values to start for those that are required, but we are now in process of setting the values to !IBI.AMP.ampername; to allow launch fexes to pass the value to the HTML.
Were the HTML pages created originally in HTML Composer? Have you tried opening them in App Studio, saving, and closing? This can correct some problems with upgrading.
i am facing similar issues , created HTML page in app studio , i see few errors "Error retrieving data for control.." which is impacting few existing functionality like save & schedule features .
Tried to reproduce the message with simpler version of HTML , found when controls are renamed causing all these issues ..
This issue is still not resolved. It is communicated with IBI and they would be looking to get to some solution on this. Looks like WebFOCUS 8105 have many issue specially with launch pages. Recent issue is with Save Parameter option.
Thanks, Pravin Singh
WebFOCUS 7703 Windows, All Outputs pravinsinghwebfocus.blogspot.com
Originally posted by Pravin.Singh: This issue is still not resolved. It is communicated with IBI and they would be looking to get to some solution on this. Looks like WebFOCUS 8105 have many issue specially with launch pages. Recent issue is with Save Parameter option.
Thanks, Pravin Singh
Are you saying that you are having an issue with a parameter not being passed from a launch page to a fex? I'm having an issue with some static radio buttons. I can run fine in 8008, but when I test in 8015m, the html it passes the description rather than the actual value of the radio button. Has anyone else noticed this?
WF 8.0.08 (Prod); WF 8.2.06 (Dev)
Posts: 83 | Location: OK | Registered: November 19, 2015
Never mind about the parameters not being passed correctly. It looks like there has been some code tightening between 8008 and 8105m. I always has checked "send display value" when I built my html, thinking it meant to send the selection at runtime. Apparently I was mistaken as this means to send the description value instead of the value itself. Got away with it in 8008, but cannot any more.
WF 8.0.08 (Prod); WF 8.2.06 (Dev)
Posts: 83 | Location: OK | Registered: November 19, 2015