Web elements DCP

[Former Member]

I want to create a DCP in web elements.  I want to auto open document to itself on each drop down. So at high level combine these two formulas into one.  I do NOT want t submit button but auto re run the same report on each DCP.

WESelect ("St", shared stringvar StudyID, shared stringvar StudyName, ElementDefault, Font);

WESubmitLinkSelect ("Choose a Study", shared stringvar StudyName, stringvar path, global stringvar fontlink)

[JWiseman]

hey Brian,

that functionality isn't built into webelements...however, if you're feeling adventurous since webelements are custom functions you could try your hand at coding the selectcascade function to do so...right now there's a selectchange function that fires when an item is clicked on one of the controls that you may be able to change to use a hybrid of selectchange and the doit function that fires after a submit control is used.

are you wanting to do this to get around the 1000 value limit for each control? if so, in the past i've split controls up so that there's a cascading family for a certain number of values...e.g. a control set for parent values that start with A to E, another set that starts with F to J etc.

or as you may have already seen, there's a sample that shows you how to "stage" the controls, but using a submit for each level, which you don't want.

[Former Member]

Did you need two seperate sub reports for this or just two different variables inside the same sub report?

[JWiseman]

are you referring to the staging method for the controls? if so, no subreport should be needed...the webelementsstagedselectmenus report uses an opendocument link to rerun / filter itself...when you start at the first level you're only bringing in the country levels. once you move to the next level, only the regions associated with the chosen country are brought back. this limits the number of values brought back at each stage.

have a look at the saved data filter in the aforementioned report.

[Former Member]

I keep going over the 1000 on the aray's and trying to figure out a work around. 

You mentioned doing something like at the parent level of the DCP to break it up like one for A-F then G-Z. 

Do you have an example of when you did this that I can look at?

[JWiseman]

sure thing...you can grab a sample from here...i'll leave the report available until you're able to get it. it's in dropbox as i wanted to give you the report with saved data so that you can publish it to your enterprise system and see how all of the controls work. you could also change the webuilder mode to use a debugging mode if you want to see the resultant url from the submit method. just change the formula conclusion to weBuilder(allelementsA, 1);

when you use this method of dividing up dcp's into sub-groups (A-F, G-L, etc.), the target report must have one parameter / prompt for each of the controls that you add to the interface report. this then means that your target report selection filter must have a clause for each of the paramaters.

it's a bit of extra work but hopefully this will prove successful for you. please let me know if it does work out.

[Former Member]

Thanks I will look at it I hope tomorrow.  I did notice though the data was not saved and it was not Xtreme db.  So it will be hard to refresh the report.  To see how it looks.  But I can figure out something and try to point it to a DB I have and go from there.

[JWiseman]

please try to download it again, perhaps by doing a Save As instead..i just double checked / downloaded the rpt and it does have the data saved successfully on it.

it is one page and would look like below, but actually there are tons of records in two subreports and the main. i'm opening in cr 2011 14.06.1036.

[Former Member]

Total side question.

Have you ever passed BOuser to a command?

I want to say in a command in Crystal

select * from a

where user.a =@BOUSER

And the user is not asked to put in their user name. 

I am using Crystal 2011, BO 4.0 and SQL 2008

[JWiseman]

if you're using webelements to pass the user via a url to a target report based off of a command, you can add the current ce user name from the special fields (in a formula) to the additional url parameters piece of wesubmit.

you can also add this (via a formula) to an opendocument url via the hyperlinking wizard or a hand coded opendoc url in a hyperlink.

if you're not using webelements or opendocument and just a report, then you have to use a main report as a container and then pass the user from a formula on the main report to a subreport based off of a command.