Report customization form only posts default settings

I am currently on version 3.0.9.
We have problems with reports generated with the wizard where settings in the customization form return to default when posted. The problem only happens when the report is viewed as a portlet. It works fine when it's run in full page mode.

I have experienced the same problem with other default parameters also. I used the workaround for maximum rows in portlet. I defined a contstant if the Page Parameters for the maximum rows.
I did NOT find a work around for Break fields in Reports.
If anybody can tell me how to fix the "bug" or has a workaround I would greatly appreciate it!!!

Similar Messages

  • Customize the QBE report customization form

    Does anyone have some ideas about how to customize the QBE report customization form
    (e.g take off the "case sensitive check box" or "format mask" .. etc)
    thanx

    repost the above msg.
    What I'm trying to do is to show only the column displayable options to portal users and hide the other cutomize sections.

  • Search report customization form

    Hi,
    does anyone know how I can achieve context-insensitivity in a query-wizard based report customization form??
    Or how I can default user entries in the query fields to all UpperCase?
    Thanks for you help!!
    Maike

    Hi,
    This cannot be done in query based wizard report. You can do this in sql based report by designing your query in such a way.
    select * from scott.emp
    where upper(ename) like upper(:name)
    This code makes the code cases insensitive inspite of the user entering small case in the :name.
    Thanks,
    Sharmila

  • Calling javascript function from report customization form

    I have been unable to call any user-defined javascript function from Portal Report Customization forms.
    Even a simple Message Box function doesn't work. I've been placing my code in the ..after header PL/SQL section for the report customization form.
    htp.p('<script type="javascript">');
    htp.p('function MsgBox(message){');
    htp.p('alert(message);}');
    htp.p('</script>');
    htp.p('See if it works');
    I have verified in plain html that my syntax is fine. Even the syntax rendered by portal is correct:
    <script type="javascript">
    function MsgBox(message){
    alert(message);}
    </script>
    See if it works
    Despite this, you will get a javascript error that an Object is expected, MsgBox not defined. Clearly from the script above MsgBox is defined.
    I have tried any number of calls to user defined functions and can't get anything to work. However, calling native functions like 'alert' works fine ( ie
    See if it works
    Anyone know how I can call a user defined javascript function in a Portal Report Customization form?

    Try changing the code
    htp.p('<script type="javascript">');
    to
    htp.p('<script language="javascript">');
    Thanks
    -Krishnamurthy

  • Two LOVs in same report customization form causes problems

    My report includes two parameters which are set by the user using dynamic LOVs in the customization form. The report used to only have one parameter and this worked fine. After including the second one only one of the LOVs work as they should. The second one doesn't trigger a value to be sent to the report. Working separately the second parameter/LOV also works as it should.
    The code:
    SELECT distinct ID, STILLING, F_DATO, STILLING_NAA, DATO
    FROM JOBBSOKNADER
    WHERE STILLING in :lov_stillinger
    union
    SELECT distinct A.ID, A.STILLING, A.F_DATO, A.STILLING_NAA, A.DATO
    FROM JOBBSOKNADER A, JOBBINT_KOBL B
    WHERE A.ID = B.JOBBSOKNADER_ID
    AND A.STILLING = '(apen soknad)'
    and B.INT_ID in :lov_interessefelt

    Hi,
    Are you trying to use dependant LOVs i.e second LOV depends on the value selected in the first LOV. If you are trying that, then reports does not support that. You have this facility only in forms.
    If I have understood wrong, then please give me the query you used for the LOVs
    Thanks,
    Sharmila

  • When calling report in forms, only html format can show chinese characters

    To all experts,
    When I run report by calling run_report_object() in forms, only html format can show chinese characters. If I choose pdf format, garbage characters were shown instead of chinese characters. My settings on server are as follows:
    NLS_LANG=TRADITIONAL CHINESE_HONG KONG.UTF8
    FORMS60_REPFORMAT=PDF
    Do you know why? I hope to print report in PDF format as PDF turned out to be more regular in format. Is there any additional settings required?
    May experts here broaden my mind?
    Richard

    Assuming that you are using version 6i, try using Oracle9i Reports it has support for multi-byte in PDF.
    By the way, Reports questions will get better response if you send them on the reports forum.

  • When calling report from forms, only html format report can show chinese characters

    To all experts,
    When I run report by calling run_report_object() in forms, only html format can show chinese characters. If I choose pdf format, garbage characters were shown instead of chinese characters. My settings on server are as follows:
    NLS_LANG=TRADITIONAL CHINESE_HONG KONG.UTF8
    FORMS60_REPFORMAT=PDF
    Do you know why? I hope to print report in PDF format as PDF turned out to be more regular in format. Is there any additional settings required?
    May experts here broaden my mind?
    Richard

    You have two different ways of generating Japanese PDF files from Reoprts. One is font aliasing and the other is font subsetting.
    <font aliasing>
    You will need to have the following entries in uiprint.txt (example).
    [ PDF ]
    .....JA16SJIS = "KozMinPro-Regular-Acro"
    "MS UI Gothic".....JA16SJIS = "KozMinPro-Regular-Acro"
    You may need to download and install Japanese Font Pack from Adobe's web site (if your Acrobat is non-Japanese version).
    <font subsetting>
    You will need to add C:\WINNT\Fonts (or wherever your TTF/TTC fonts are installed) to your REPORTS_PATH.
    You will also need to have the following entries in uiprint.txt (example).
    [ PDF:Subset ]
    "Andale Duospace WT J" = "Aduoj.ttf"
    "Albany WT J"="AlbanWTJ.ttf"
    "MS UI Gothic" = "msgothic.ttc"

  • Report Customization Form Question

    How do you display the report customization before the report is rendered?

    If the Report is used as a portlet, I think it's not possible. Only the personalize link will display the customization options
    If the report is display in a full page, try: <SCHEMA>.<REPORT>.show_parms
    Patrick.

  • How to get the value from another report Customizes Form

    Dear all,
    I create a report such as
    select * from mytable.table1
    where field1 = :bind_variable
    I create a menu to run this Customized Form and user have to select the bind_variable values. So I have another report created which also want this bind_variable as it WHERE Clause. But I don't want my user to key the same bind variable twice. They can just same the Customized Form and run for both report.
    Could anybody know how to get the bind_variable on 1st report and used by the 2nd report.
    Thank you very much.
    Best Rgds,
    SL Voon

    Hi,
    are you on BI7.0? There you can create variables type replacement path and get the value out from a different variable without any coding.
    regards
    Cornelia

  • Error WWV-00100 in Report Customization Form

    All,
    I am getting a WWV-00100 error, when I
    click on the customize link for the report.
    any tips?
    Thanks

    Chetan,
    select ''&#0124; &#0124;user_name&#0124; &#0124;'' as login_id, first_name, last_name,'[View Request Details]' as the_request,'[Create DB Login]' as the_db_req,'[Modify User]' as the_mod
    ,'[Close request]' as the_action
    from portal30.wwsec_person$
    where created_on between :the_start and :the_end
    and user_name <> db_user
    Error encountered when trying to call show_parms
    is
    Error:
    Unexpected error encountered in wwv_render_parmform.show (wwv_render_parmform) (WWV-00100)

  • Pass a parameter from a report to a customization form of another report

    Hello,
    I want to pass a parameter value from a report to the customization form of another report and display it in the text field in the customization form as a default value. I have 2 variables in the customization form and in one of them, I would like to display the default value from a previous report.
    Thank you
    Jayasree

    1. go to the manage component screen of the report
    2. open the package body (pl/sql source)
    3. search for 'procedure show_parms'
    4. scroll down till you find
    -- call to parameter form rendering engine
    5. copy the procedure call below it
    a) you will have to pass <PORTAL_SCHEMA>.wwv_utlglobl.RUN_AS_NORMAL to p_mode
    b) remove the parameters p_reference_path, p_redirect_url, p_exec_mode, p_page_url ( or you can pass null to them)
    c) 'p_parm_names' will contain your 2 parameters
    d) you can pass values to 'p_parm_values' which you want to be displayed in the parameter forms.
    6. you can call this procedure from a dynamic page and link the dynamic page to your first report

  • How can I make Edit/Default Customization form with Java ?

    In previous portal relise developers have simple way to rendering Edit/Default Customization form:
    <% PortletRendererUtil.renderCustomizeFormHeader(portletRequest, out, null, "services_action", null, null); %>
    <TABLE BORDER="0" CELLPADDING="0" CELLSPACING="2">
    <TR>
    <TD>Days</TD>
    <TD><INPUT TYPE="text" NAME="services_days" VALUE="<%= days %>" SIZE="10"/></TD>
    </TR>
    <TR>
    <TD>Rows</TD>
    <TD><INPUT TYPE="text" NAME="services_rows" VALUE="<%= rows %>" SIZE="10"/></TD>
    </TR>
    </TABLE>
    <% PortletRendererUtil.renderCustomizeFormFooter(portletRequest, out); %>
    In current portal version I can not find these methods, these methods not exists in JavaDoc and in jar's. And all old code do not works!!! Why?
    I must hide portlet borders and use <renderContainer>false</renderContainer> in provider.xml. Then portal do not render Edit/Default Customization form in Edit/Default mode. In previous relise I can make this form with Java code.
    My question: how I can get Edit/Default Customization form in Edit/Default mode with Java code?
    Thanks in advance
    Cheslav

    Hi George, the trick is to figure out which browser is your default now, and remove that designation using the Android settings for Apps. It might be Chrome or it might be something Samsung provides.
    This article has more information: [[Make Firefox the default browser on Android]].
    Does it work?

  • Any hacks to modify default settings in common adjustment settings?

    Hey folks, I've just recently upgraded to Aperture 2.0 and am (thankfully) seeing many improvements both in performance and features.
    However, it seems that with the new version, Apple has decided to not allow you to customize any of the default settings for commonly used adjustments (in my case "Crop") to use my own settings.
    Specifically I'd like to add my default crop-values of a ratio of 16x9 (ideally replacing the default 3x2)
    Any chance there's n easy hack?

    It appears to me after tinkering around that I can set a page like I want it and then save it as a template.  I did so to a folder in Finder.  Now the only way I can automatically bring up "default" settings on a Pages blank document is to go directly to that file in Finder and open it from there, not from Pages itself.  Is there any other way to do this?

  • Passing a parameter to aReport Customization Form

    I have a report that has a default view and a customized view. The default view has a button that allows the user to customize the report by showing the same report in show_parms mode. This allows them to sort and break on different fields. I would like to send the same parameter sent to the default view to the version generated by the run button on the customization form. I just can't fiqure out how to do it. Any ideas would be appreciated.
    Thanks,
    Linda

    Martin,
    Thank you for responding. I will certainly keep in mind the way you solved the problem. But I actually solved it myself with the following technique.
    STEPS
    1. Created a link to the Reports Customization form from the Report.
    2. Captured the value of the parameter sent through the URL to the bind variable for the report.
    3. Set the parameter value to a global variable using the Session storage API=wwsto_api_session.
    4. Retrieved the value of the global variable by setting the default value in the "Customization Form Display Options" tab of the report.
    In the Report add the following PL/SQL Code....
    --Location:      Additional PL/SQL Code
    --Attribute:     ... after displaying the header
    declare
    l_store portal30.wwsto_api_session;
    l_param_value varchar2(4);
    begin
    --(#2)TStudy is the parameter name passed through the URL and the name of the bind variable in the SQL Command
    l_param_value := portal30.wwv_name_value.get_string(l_arg_names,
    l_arg_values, 'Tstudy','',1);
    --(#1) Add Link to the Reports Customization Form
    htp.p ('<CENTER>');
    htp.p('<font class=portletheading2> CUSTOMIZE</font>');
    htp.p ('</CENTER>');
    htp.br;
    --(#3)Store Parameter Value sent to the bind variable
    l_store := portal30.wwsto_api_session.load_session ('MYPORTAL', 'MYReport');
    l_store.set_attribute ('PValue', l_param_value);
    l_store.save_session;
    END;
    --(#4) Default Value in "Customization Form Display Options" for TStudy
    #portal30.wwsto_api_session.load_session('MYPORTAL', 'MYReport').get_attribute_as_varchar2('PValue')
    ?????My Last Question - How do I hide the prompt for the bind variable. I don't want the user to change this value after I went to such trouble to set it???????
    Thanks again,
    Linda Gowen

  • Customization forms display message Query options

    Is there any way to eliminate or change the message 'Query Options' in a report customization form?

    Query Options will appear in customization form if you have any bind variable set in the component's design time.
    If u dont want to have any query options,
    you can suppress them by redesigning the component without any bind variables.

Maybe you are looking for