WebElements - Having problems putting CR report in WECollapsibleSection

Question

Hi there - 
The user doc indicates putting a WEcontrol in a collaspible section  is possible - I am trying to put a CR report in the section and am having problems.
Here's my code:
WECollapsibleSection (ElementName, {@WE_OppListRiskReport}, OpenText, CloseText, Font, SectionWidth, SectionHeight)
where {@WE_OppListRiskReport} is
stringvar targetpath :=WETargetPath ("rpt","CUID" ,{@WE_OppListRiskPullCUID},"");
(i've also tried other permutations of the placement of WETargetPath)...
When I run my report with the collapsible section and click on the OpenText Link, the section appears, but what appears in it is the Opendoc URL:
/OpenDocument/opendoc/openDocument.jsp?sType=rpt&sIDType=CUID&iDocID=ASHjBo78IzxEj_yzCRYc6uc
I have used the target path to the same CR report in an iFrame and the report displays correctly so I know it can find the report correctly.
Help!
thanks!
Pam
PS.  Just into a week of using WE and loving it!!

Answer 1

Hi Jamie -
I have already encountered issues after I accidentlally copied/pasted code and left  2 physical webelements with the same name.    (hey!  why is that report loading in that frame??)   That wasn't the issue here, but your response made me go through my code with a fine tooth comb to verify that I hadn't done that.
While I was double checking, I did some more experimenting and debugging.  This led me to an interesting discovery. 
As a reminder, I am trying to 'load' crystal reports into iframes onto a Main 'portal' report.  My main report has iframes, collaspible sections, editbox controls and a flyout section with 5 elements.  Loading a report into a frame works fine for the 'independent ' iframes that are placed directly on my main report.   The expected report also loaded on the 'top' element of the FlyoutSection control.  (When I say 'works fine', I mean that the reports loaded into their respective iFrame controls when I open the Main 'portal' report)
The 2 controls that I was having issues with were the CollapsibleSection and the  FlyoutSections (all but the top element.) . 
In each case, I had defined iframes and targeted the iframes with Cystal reports within these controls.  When my main report loaded and I clicked on the 'Show Report' link to open the CollaspibleSection, I could see the outline of the iframe but within it,  was the never ending 'please wait ' window.  The report just never loaded.  I experienced the same thing when I put an iframe on the 2nd 'section' of a FlyoutSection control.   I knew that my code was correct because if I pulled the iframe code out of the control and put it directly on my Main 'portal' report, it worked like a charm.
To me, it seemed as if, despite the 'please wait'  message, the iframe was NOT loading the report.   I was never prompted for parameters and the DB showed no I/O hits to indicate the report was hanging due to performance.      So just for the hell of it, I put a submit button within the content of the FlyoutSectionControl's second section (along with the existing iframe).  All the submit button did was force the report to be loaded into the same iFrame that was already there.  And, to my surprise, after pressing the button, the report loaded.
I tried adding a submit button to the collaspible section as well and that seemed to force the report to load as well.
Of course, this is really clugey.  My expectations are that when I click on the FlyingSectionControl's element headers, the reports wherein would load and, if I click on 'show report', the report will load as the collaspiblesection expands.  I think users will also have the same expections.  It's seems unnecessarily redundant to have a 'Show report' link open up and then the user have to click a button that says 'Do you really want to see the report' before the report will load.
Fundamentally, these 2 controls differ from others because you need to 'click' on them to change their state.  Perhaps this 'click' is interfering with the report loading into the iframe?
I'd love an explanation and also your input into how these controls could be 'preloaded' .
thanks!
-Pam
Here's the code for my collaspible section (that finally worked)  - the only difference from the prior version is the addition of the WeSubmit(btn) function:
stringvar item1:= WETargetPath ("rpt", "CUID", {@CUID_chart}, "weIframe=iframe5"  );
stringvar OpenText:= "Show Chart";
stringvar CloseText:= "HideChart";
stringvar SectionWidth:= "3in";
stringvar SectionHeight:= "2cm";
stringvar insideframe :=WEIFrame ("iframe5", "item1", 400, 200, "yes") ;  <==if I leave out the target path here, the frame shows up empty at first (which is neater than seeing the 'please wait' message box))
stringvar SectionElements:=   WESubmit("chartbtn","Button", "see chart",item1 , font)
+ WEBreak (2)+  insideframe;
stringvar collaspiblegroup := WECollapsibleSection (ElementName, SectionElements, OpenText, CloseText, Font, SectionWidth, SectionHeight);
collaspiblegroup + WEBuilder(collaspiblegroup,2);