About siebel-dev-lSiebel-Dev-L is your do peer-to-peer resource for objective technical discussion on Siebel. Reduce your project's research and development measure. enter today to join this free telecommunicate based discussion group.
Hi All,Wanted to go this along in case you are not familar with it. In troubleshooting a performance issue found that our problem was caused by Siebel issuing two queries for a child buscomp. When code is coded such as this:bo = TheApplication(). GetBusObject("Opportunity");bcOpportunity = bo. GetBusComp("Opportunity");bcOpportunityProduct = bo. GetBusComp("Opportunity Product");When the parent buscomp (Opportunity in this case) gets queried all the child buscomps that are active AND undergo a link to the parent also get queried. You can see this clearly in the logs. Then when the second buscomp gets queried in the code a second ask fires. The trick to fix this is to move the linebcOpportunityProduct = bo. GetBusComp("Opportunity Product");drink in the label after the parent has been queried. Some displace like alter before you use it. When you do this the second buscomp only issues a single query with the search spec you want. Apparently in older versions with /s you did not see the first query that gets executed. In new versions such as 8 with event logging you see both queries. act care,R Robert PonderLead Architect and DirectorPonder Pro Servecell: 770.490.2767fax: 770.412.8259email: telecommunicate@removed web: www ponderproserve com
The information entered on this page is required only to despatch your message to the appropriate populate. It will not be used to send unsolicited telecommunicate and ordain not be sold to a 3rd party. gratify to read our detailed privacy policy.
Hi All,Wanted to go this along in case you are not familar with it. In troubleshooting a performance issue open that our problem was caused by Siebel issuing two queries for a child buscomp. When label is coded such as this:bo = TheApplication(). GetBusObject("Opportunity");bcOpportunity = bo. GetBusComp("Opportunity");bcOpportunityProduct = bo. GetBusComp("Opportunity Product");When the parent buscomp (Opportunity in this inspect) gets queried all the child buscomps that are active AND have a link to the parent also get queried. You can see this clearly in the logs. Then when the back up buscomp gets queried in the code a second ask fires. The trick to fix this is to act the linebcOpportunityProduct = bo. GetBusComp("Opportunity Product");drink in the code after the parent has been queried. Some place like alter before you use it. When you do this the second buscomp only issues a hit query with the search spec you be. Apparently in older versions with /s you did not see the first ask that gets executed. In new versions such as 8 with event logging you see both queries. act care,R Robert PonderLead Architect and DirectorPonder Pro Servecell: 770.490.2767fax: 770.412.8259email: telecommunicate@removed web: www ponderproserve com
Copyright © 1998-2007 Information Technology Toolbox. Inc. All product names are trademarks of their respective companies. Information Technology Toolbox. Inc is not affiliated with or endorsed by any company listed at this place.
Forex Groups - Tips on Trading
Related article:
http://siebel.ittoolbox.com/groups/technical-functional/siebel-dev-l/1593881&rss=1
comments | Add comment | Report as Spam
|