Conditionally Displayed Field

I have a select list, and I want one of the options to be "Other." When the user selects other, I'm trying to have a text field that conditionally displays. I'm trying to set the conditional display for when the select list item is equal 'Other', but it's not working. I want to be able to have that item's value to be set as 'Other' when they choose it from the select list, but I don't want to set the item as "select list with submit" because I don't want the whole page to submit, I just want the select list to submit 'Other' so the text field will conditionally display.

Brice,
When a page submits because of a 'select list with submit' selection, the REQUEST value is set to the name of the select list item. You can use that REQUEST value to control what actions occur after submit. So if you didn't want a process to fire in that case, you could put a condition on the process like 'Request != Expression 1' and type the item name in the Expression 1 field. This is the standard way to use page-submitting items to do their work without side-effects.
You might be able to do what you want with javaScript also, but I don't know how.
Scott

Similar Messages

Data not submitting when I have a conditional display on a date field

Hello all,
Could someone please help me with the following issue?
I have created an updateable report region with four updateable fields. 3 of the fields store a number values and the fourth stores a date value.
Each updateable report item has a conditional display, and whether they are displayed or not is controlled by the end user using a radio group (with submit). This provides the user with three options.
If I remove all conditional displays all data will commit to the database without any problems. If I apply the conditional display to the number fields only, again the data will commit as normal. However, as soon as I add a conditional display to the date field it all goes pair shaped. The data will then cease to commit, with no error message at all. Once I remove the conditional display normal service is resumed.
I'm certainly an APEX novice at the moment, so I wondered if anyone could shed some light on this.
Thanks in advance for your help
Steve

Stew,
Basically, I have edited each applicable report field column attributes, via the report attributes tab, and selected a conditional display 'Value of item in Expression 1 = Expression 2' for all of them.
In the same report region I have created a radiogoup with submit called p51_update_type, specifying three static return values; R, F and S
Condition e.g.
*"Expression 1"*
p51_update_type
*"Expression 2"*
S
All columns display as expected, and commits to the database are normal, that is until I apply a conditional display to the date field (which relates to a table column of type DATE in the database).
Thanks
Steve

Conditional Display Based on a Field Value

I'm a newbie ...
I developed an application that shows payment information.
Record type one is a cheque
Record type two is a payment stub
Rec Type Account Amount PDFFile
1 888888 1234.00 summary.pdf
2 888888 10.00
2 888888 400.00
2 888888 800.00
2 888888 24.00
I have developed a program that assimilates a number of cheque images into a single pdf file. I write the filename and location of that pdf file into a field on 'record type one' (cheque record).
I want to have a button that only renders on records that that have a value in this field.
I've looked at conditional display, but can't seem to find the right option.
Can anyone get me pointed in the right direction?
Thanks
Dave

Dave - Where do you "write" this field? On the same page or from a previous page? What is the display type of this field (which I hope is implemented as an Application Express page item)?
It's all about having a value in session state for that page item at the time your button is rendered. If you've got that, then the button condition will be trivial.
Scott

Conditionally Hide/Display fields in a region

How can I conditionally hide/display fields in a region. Based on a user selection whether they want to 'Enter' or 'Select', I want to dispaly the appropriate field .i.e. if the user selects 'Enter' then I want to display a Text field and if they opt for 'Select', then I want to display a Select list.
Thanks in Advance.
Regards,
Hilal

Hi Halil,
I've been trying to reproduce what the linked site does.
Here's my solution:
1 - Add all items to the page whether or not they are going to be displayed
2 - Ensure that all items that could be shown/hidden are on lines on their own (ie, set New Line to Yes)
3 - In the region's Region Footer (or in a new HTML region in the Before Footer position), add in this bit of javascript:
<script type="text/javascript">
html_HideItemRow('NameOfFieldToHide');
-- repeat for each item to be hidden when the page first loads
</script>
4 - On the radio button's definition, add the following in the HTML Form Element Attributes setting:
onclick="html_ToggleItemRow('NameOfDisplayedItem');html_ToggleItemRow('NameOfHiddenItem');"
Now when the page is loaded, one field is automatically hidden then clicking any of the radio button options will toggle the hidden/displayed fields and their labels.
As stated before, if you do a View Source on the linked application's page, you will see either more methods that are used to show/hide items/regions, but the above should be a starting point for you.
Regards
Andy

Conditional Display of Interactive Report Based on Field Above

Page one has simple text box entry for a Vendor # with a button that branches to a page displaying information for that vendor. In a region below, I would like an interactive report that displays all of the item and description that vendor provides to our company. I have tried to use the Conditional Display to disply only items in the report but have been unsuccessful. Your help is appreciated!
Thanks.

Hello user2961006 (please tell us your name),
I understand your question to be, "how do I make a report on page two only show rows related to an item entered on page one". Putting a condition on a region isn't the answer here - you want the report to always display, but just with different rows depending on the vendor number entered. A condition on a region is used to either display the region or not.
What you need to do is put a WHERE clause on the SELECT statement that your report is using to get its data. For example, if the item holding the entered vendor number is P1_VENDOR_NUM, the SELECT statement for your report would look something like:
SELECT item, description
FROM my_items
WHERE vendor_num = :P1_VENDOR_NUMNote my_items is a fictitious name. This will tell the DB to only retrieve rows where the vendor number is the vendor number entered by the user.
Hope this helps, I'll gladly accept reward points if it does ;-)
John

Problems with Conditional Display and Read Only

Hi Everybody,
I have a form to Add/ Modify Table Info.
I have column which stores numeric value (like no. of purchases, no.of returns etc.,) and I have a text field with this Database column as Source.
In some cases the value is a foreign key (Id of the Owner, Buyer etc.,) to another table. In such cases, I want to display a select list containing people information. Is that possible?
This is what I did to achieve that
I added a select list with info from second Table. Made both the text field and the select list to conditional display and conditional read only.
My understanding is that When an item is made read only it should not be saved to the Database.
But while Updating I am getting the following Error
ORA-06550: line 1, column 130: PL/SQL: ORA-00957: duplicate column name ORA-06550: line 1, column 7: PL/SQL: SQL Statement ignored.
Any can anybody help me out on this?
Thanks
Nimmi

My understanding is that When an item is made read only it should not be saved to the Database
No, all page items with a Source Type of "Database Column" will be used by the Automatic DML process to insert/update the database. Form inputs with the "disabled" HTML attribute set are not POSTed to the server.
Try to create 2 items, one Select List and other Text Field but setup their conditions such that only one of them is rendered on the page at any given time. That might work.

Help with Conditional Display and Validation

Version 4.1.1.00.23
Hello,
I'm having a difficult time with a conditional display and validation I'm hoping someone can help with.
Requirements:
When the Start Date (Datepicker) and/or End Date (Datepicker) change then display the Change Reason (Select List) and Change Description (Textbox)
If the page is saved without entering a Change Reason display a validation error message that the Change Reason cannot be empty (NULL)
What I've tried
Create a Dynamic Action on the Start Date
Event: Change
Selection Type:Item(s)
Items(s): P51_START_DATE
Condition: none
True Action Section:
Action: Show
Fire on Page Load: Checked
Show all page items on the same line: No
Affected Items Section:
Selection Type:Item(s)
Item(s): P51_CHANGE_REASON,P51_CHANGE_DESC
I've also created a Dynamic Action with similar settings for the P51_END_DATE.
I created a Validation for the P51_CHANGE_REASON as Function Returning Error Text:
DECLARE
    v_start_date    work_items.start_date%TYPE;
    v_end_date      work_items.end_date%TYPE;
BEGIN
    SELECT start_date
          ,end_date
    INTO   v_start_date
          ,v_end_date
    FROM   work_items
    WHERE work_items_id = :P51_WORK_ITEMS_ID;
    IF ( (v_start_date != TO_DATE(:P51_START_DATE,'DD-MON-YYYY') OR v_end_date != TO_DATE(:P51_END_DATE,'DD-MON-YYYY') ) AND
          :P51_CHANGE_REASON IS NULL ) THEN
        RETURN 'Change Reason must have a value';
    END IF;
END;
The Issue
I tried to create another Dynamic Action to hide the P51_CHANGE_REASON and P51_CHANGE_DESC fields on page load, but when either of the date fields are changed and the validation is fired the P51_CHANGE_REASON and P51_CHANGE_DESC are hidden again.
There are two buttons to submit the page: 'SAVE' will submit the page and stay on the page and 'SAVE_CHANGES' will submit the page and branch to the previous page (which is a report with EDIT buttons to edit the record).
I can't get the page load Dynamic Action to NOT fire when the validation is fired.
I hope this is clear and if not what information can I provide?
Thanks,
Joe

Phil,
Thank you for looking at this.
Yes if the Change Reason is NULL when the edit page is displayed then the Change Reason and Change Description fields are hidden. If the Start Date (Datepicker) and/or End Date (Datepicker) change then display the Change Reason (Select List) and Change Description (Textbox). If the page is saved without entering a Change Reason display a validation error message that the Change Reason cannot be empty (NULL).
The problem I'm having is that if no Change Reason is entered and the page is saved thereby firing the validation the Change Reason and Change Description fields are hidden again (because of the On-Load Dynamic Action to hide them). So now the user can't put in a Change Reason...unless they change one of the date fields again which isn't going to be accepted.
Is there a way to determine if a validation error was fired and be able to use that on the On-Load Dynamic Action to hide the two fields? Something like...If the validation fired then don't run?
Please let me know if I'm still confusing you.
Thanks,
Joe

Application Level Function for Conditional Display

I need to hide a field on Print Preview if it is null. I currently have the following PL/SQL Expression Condition:
:P305_DEPT IS NOT NULL AND v('PRINTER_FRIENDLY') <> 'YES'
It works great; now I need to do this for a lot more fields within my application. Is there a way to call a PL/SQL process defined in HTML DB, passing it the current item value, or some other way to save myself some typing?
I've tried various combinations of shortcuts, substitution strings, application processes, etc. and can't seem to get the right combination.
I'm hoping you have a cool solution, or some other ideas I can try out.
Thanks!
Chaunaci

Hi Raj,
All of this came up because we have several data items displayed above each report page, which allow the user to enter filter criteria. When the page is displayed in Print Friendly mode, the Select Lists display as blanks when null, but Text Boxes display as [] when null.
Our QAs have asked us to make all of the filter fields consistent in appearance in Print Friendly mode. The work-around solution is to hide the filter fields that are null when in Print Friendly mode. Therefore, we came up with the following PL/SQL Expression to use in the Conditional Display:
:P305_DEPT IS NOT NULL AND v('PRINTER_FRIENDLY') <> 'YES'
Because I will need to add the above conditional statement to many items, I was hoping to create and call an HTML DB application-level process and pass the current item value in, so my conditional display logic would look something like...
HIDE_NULL_ON_PRINT(:P305_DEPT).
When I was doing some additional testing last night, I realized my boolean logic needed to be tweaked, and it would be nice to tweak it in just one place, rather than on every field's conditional display.
I currently have it working by putting the IS NOT NULL AND v('PRINTER_FRIENDLY') <> 'YES' into an application substitution string, so my conditional logic shows as:
:P305_DEPT &HIDE_NULL_FOR_PRINT.
In trying to determine if this was the best solution, I need answers to the following issues:
1. Is there a way to generically reference the current item in the conditional display logic? I currently type in the specific item name (ex: :P305_DEPT), but it would be nice if instead I could just say &CURRENT_ITEM_NAME. (or something similar).
2. Can I create an application-level process, pass a parameter into it (the current item), and have it return a value that can be evaluated by my conditional logic display?
Thanks so much for your quick responses to this and all my previous posts. It is wonderful to be able to post a problem at the end of the day, and come in to a solution in the morning!
Chaunaci

Conditional Display - ideas needed

Hello
I have this:
http://vels.dk/tmp/display.jpg
I would like to show only "Choice invoices view" region when the user come to the page.
When the user press the "Show All" or "Last x days" then I have a 2 Branches. The Branches set a hidden item to 0 or 1 (1= all 0= last x days)
The user surf to another page in the application and come back to the page. But now the "Invoice" region is display... How do I solve this? I have tryed some REQUEST, but the "next row select" belov the table has no REQUEST functions :(
Some ideas?
Best Regrads
Jesper Vels

Hi Jesper,
I would suggest something like the following:
1 - Your hidden field should have THREE values - 0=Hide, 1=All and 2=Last x days
2 - The default value should be 0
3 - Have a conditional display on the report's region that only displays the report is the value of the hidden item is not 0
4 - Your two buttons can then set the value of the hidden field to 1 or 2 and the SQL statement should include a WHERE clause something like:
WHERE ((:P1_SHOW = 1 AND ....)
OR (:P1_SHOW = 2 AND ...))
5 - Create an application computation for the hidden item
6 - This should set the value to 0 when the current page is NOT this page - therefore, whenever the user moves to any other page, the value will be set to 0 and the report will be hidden
Regards
Andy

Not able to create conditional required fields at Tcode CJ20N Proj Systems

Hello experts,
I have a requirement to create a few custom fields under custom enhancement tab in CJ20N transaction, and depending on a particular value for one of the fields, another set of fields need to be set to required. (If FIELD1 = 'Y', FIELD2 & FIELD3 should be set to required)
My approaches..
1. Assign a screen group to FIELD2 and FIELD3. If FIELD1 = 'Y' then LOOP AT SCREEN, and set screen-required = 1 for that specific screen group.
Problem with this approach is that, if I select FIELD1 = 'Y' (hit space or enter -> sy-ucomm = TOGGLE), the fields are successfully set to required. However, now if at this point I go and change value for FIELD1 = 'X' (hit space or enter), FIELD2 and FIELD3 still remain set to required, and keep requesting value.
2. Do not set any fields to required. Instead set it to an information message in PAI, informing user that this field requires a value when FIELD1 = 'Y' on TOGGLE and SAVE.
Problem with this approach is that even though during TOGGLE event user is provided with an informational message, if the user directly decides to SAVE (no change for TOGGLE event), in this case the same message is displayed, and the project screen itself is closed. I do not think it would be ideal for the user to see the entire project close on SAVE everytime they miss a conditionally required field.
I am just not sure at this point how to handle this at SAVE so that I can still have the same control as I would when TOGGLE event is triggered.
Experts please help if you have come across such a situation!!! Your insight would be greatly appreciated!
Edited by: akkinair on Dec 16, 2011 1:25 AM

Please find below the response.
1. Assign a screen group to FIELD2 and FIELD3. If FIELD1 = 'Y' then LOOP AT SCREEN, and set screen-required = 1 for that specific screen group.
Problem with this approach is that, if I select FIELD1 = 'Y' (hit space or enter -> sy-ucomm = TOGGLE), the fields are successfully set to required. However, now if at this point I go and change value for FIELD1 = 'X' (hit space or enter), FIELD2 and FIELD3 still remain set to required, and keep requesting value.
--> When FIELD1 chnage used module with additon CHAIN-REQUEST and check its value if it is to be set to optional by using loop at screen and set screen-required =0.*_
2. Do not set any fields to required. Instead set it to an information message in PAI, informing user that this field requires a value when FIELD1 = 'Y' on TOGGLE and SAVE.
Problem with this approach is that even though during TOGGLE event user is provided with an informational message, if the user directly decides to SAVE (no change for TOGGLE event), in this case the same message is displayed, and the project screen itself is closed. I do not think it would be ideal for the user to see the entire project close on SAVE everytime they miss a conditionally required field.
--> Can you please clarify it.
Thanks
Nabehet

Conditionally displaying different images in a report

Hello. I have a simple report. In one column of it I have a link to another report. Instead of showing the value for the column, I show an image using the column's Column Link's Link Text property.
In the Link Text field, I put an <img src="#WORKSPACE_IMAGES#my_image.jpg"> tag.
Works like a charm - on the report the column displays little icon images that can be clicked on that take the user to a different page.
I would like to conditionally (based on the actual value of the column's row) display two different images. Think of a green Up arrow vs. a red Down arrow.
How can I do that?
Or can I at least have the image above conditionally display and if the condition is not met, not display anything?
I notice each of the report's column's attribute page has the Conditional Display section. How does work for a column?
Thanks
Boris

Use a case expression in the query, e.g.
case
when x <= 50 then 'down.png'
else 'up.png'
end icon
...and change the Link Text field to
<img src="#WORKSPACE_IMAGES##ICON#" alt=""/>

Error in Display Fields

A New issue arised.
We have successfully executed an input schedule on our side. Here, the values entered in Display field Areas cannot be send and we get a Popup saying that "There is no data to refresh"
But surprisingly, the same input schedule executed at my Client's end behaved wierdly.
They were able to send data from Display Fields as well ( to the Data Base), which is not correct.
This is the same schedule executed from our side.
Why so?
Any ideas would be gladly appreciated!
Thanks in advance.
Regards,
Madhuri

Hi Madhuri,
Can you please tell me how you tried to configure it?
Let me give you an example
CRITERIA                  EVALUATE IN      FORMAT      USE      PARAMETERS      APPLY TO
DEFAULT                                        12,345.00                             DATA
SalesAccount.CALC = "Y"      COL           12,345                                DATA
Product.CALC = "Y"           ROW           12,345.00                             DATA
Like the above example, you need to come up with some conditions for the cells, which needs to be locked. You define those conditions in the criteria section. In the format section, you lock the cell using native excel's cell property.
I am sure this will work, if configured properly.

How to conditionally encapsulate fields within ECC 6.0

I'm interested in strategies to conditionally encapsulate fields within ECC 6.0.
The requirement would be to mask specific fields (e.g. Vendor Name) within a particular data set (e.g. a particular Company Code) by default while allowing those fields to be visible by some users. The key is that we do not want to mask these fields globally, nor do we want them masked for every user. Even more important, we do not want to modify all the transactions and programs where these fields are available.
I know one option is to add custom code at the Domain level of the fields. We're currently investigating this further to see if it will satisfy all our needs and perform well.
I'm looking for any other options we should explore, including 3rd party options.
Thanks,
~Matt

Alex Ayers wrote:Taking the example of the vendor master, i dont think retrcition on F_LFA1_AEN would really help. when a display transaction is used the protected fields are also shown. I understand it is a "no worry' on the complaiance front, but i suppose there could be a valid reason for not allowing users to display something (the operator can shed light on that)
And from what i understand, the object doesnt get checked during the creation of master records too - its primarily to control the changes made on certain fields of the master record.
and it needs a certain amount of effort to understand & check the implications before starting with the filed group customizing
>
> For the benefit of Shekar there may be the opportunity to use transaction variants
thanks, Alex. This need could in all fairness end up with that.... a transaction variant
> 1. Don't give access to the transaction if you can't trust users to use it properly
> 2. Use a detective control to identify where users have changed things that they shouldn't have.
Why do i feel an Auditor posted this????
> Finally, using parameter ID's for this purpose generally will not work and should not be considered for security reasons
100% agree with you

How to conditional display Report Region based on number of rows returned

I have a page with two Report Regions.
One Region should display if the Query returns 0-1000 rows. The other should display if the same Query returns more than 1000 rows.
The only way I can figure out how to do this is have ANOTHER query in the conditions field for each Region to Select count(*) from etc.
I know there is a #TOTAL_ROWS# value but that is only available after the Region is displayed. Is there some other built-in variable that can be used to put in the Conditions field or is doing duplicate SQL queries the only way?
Any help would be appreciated.

Rather than running your query 4 times (by embedding it in your condition), you can have a region that is not displayed, with a hidden item, and set the value of the item in a before header computation to the count of your query. Now you can conditionally display based upon the value of that item.
-- Sharon

Conditionally displaying tabs

I have a page that I want to call in two different methods.
1. I want to display the page with tabs
2. I want to display the page as a popup and therfore do not want the tabs to display.
Is it possible to conditionally display the tabs?
Thanks

Brian,
Standard Tabs and Parent Tabs both have condition attributes. If your popup page URLs can include a certain keyword in the request value field (between session ID and debug positions in the f?p URL), you could make the tabs conditional on that request value.
Scott

Conditionally Displayed Field

Similar Messages

Maybe you are looking for