Read Only Conditions - Master Detail

I have a page with a master detail
i created an read only condition and the master passed to read only but the detail not...
Why? Is not possible to put the detail component "read onyl" ?

Hi,
When i understand correctly you want that the form is editable when the user is an admin user
and read only when the user is a normal user.
You can solve this by the use of dynamic actions
to enable and disable items of that region(s)
do this conditional (standard user = disable and admin = enable)
Other solution
When making master/ detail with the wizard choose edit detail on different page
On the edit link you can put a condition (only visible when user is ADMIN)
Regards,
Frank

Similar Messages

  • Read Only condition on RadioGroup item

    I have a RadioGroup item on my page that is conditionally set to read only (using a function in the read-only condition type). I have a process that is updating the table with the value of the radio item
    ie. update table
    set column_name = :P1_RADIO
    It seems that when the item gets set to read-only (from the condition), the page value of that item is blank, which in turn sets my DB column value to blank. Why is that? It only seems to work that way on Radiogroups that are readonly.

    Anybody know why setting a radiogroup item to read-only (thru read-only condition in properties) makes the value blank?

  • Textarea with Read Only Condition Type

    A have a textarea (database field with Varchar2(4000) with the Read Only Condition Type set to Request != Expression 1. Works fine, except that data presented as a long 1 line text (like a Displayed text) when condition meet (no vertical scrollbar).
    Am i missing some additional settings.

    the easiest way to get the read-only version of your textarea item to appear more like your read/write version is to add some style specifications into the "Read Only Element Table Cell(s) Attributes" field that's right below where you specified your read-only conditions ("Expression 1" and "Expresssion 2"). as the name suggests, values entered into that field end up in the table data tag for the cell in which your read-only content is placed. added style specifications for height and width would help you control how the text is spread across your page. you can/should also consider using background and color style attributes to color the table cell the way we're used to seeing read-only data ("grayed out"). so though my colors are way off, a string like this...
    style="width:16px;height:30px;background:#C5D5C5;color:666666;font-weight:bold;font-size:12pt"
    ...in that "Read Only Element Table Cell(s) Attributes" field would format your read-only data closer to what you're going for. at the least, it'd give you an idea for the type of control you have.
    for extremists, there's also another approach: if you want absolute and total control over the way your textarea item's data is displayed, you could display your item's data in an HTML region instead of as the item directly. for instance, you mentioned you liked that scroll bar. you could achieve the scroll bar by defining your table, the scroll bar class, and table cell in an HTML region. say we saved your textarea item's data to a hidden item called P1_MY_TEXTAREAS_DATA. i'm pretty sure this html would let you show that data in that scrollable non-updatable format you're shootin' for...
    <style type="text/css">
    .scrollarea{
    font-size: 10pt;height:250px;width:100%;text-align:left;
    background-color:#ffffff;color:black;padding:0px 0px 0px 0px;margin:0px;overflow: auto;
    float:left;}
    </style>
    <div class="scrollarea">
    <table summary="" width="100%"><tr>
    <td style="width:16px;height:300px;border:4px;margin-left:4px;margin-right:9px">
    &P1_MY_TEXTAREAS_DATA
    </td></tr></table><div>
    ...see? by defining your own table, you get the easy opportunity to wrap it in those div tags that call the scrollarea class. also note that i just referenced the content of your textarea item with that ampersand syntax (&P1_MY_TEXTAREAS_DATA). you could, of course, keep things cleaner by defining your scrollarea class in a css, but that's your call.
    hope this helps,
    raj

  • Strange behavior when Popup LOVs has read-only condition and Bug Report

    Hi,
    I observed an inconsistent behavior of Popup LOVs when the read-only condition is true. In that case the defined lov query is used to map the internal value of the page item to the display value defined in the lov query.
    What is the reason for this behavior? Because if the Popup LOV is in "edit mode" the page item value is just displayed without looking up the display value. The display value is just used for the popup lov. Mapping the value is normally a behavior of the popup key lov.
    -> The result is that different values are displayed if the page item is in edit or read-only mode. That's not really the behavior someone would expect.
    BTW, there seems to be a bug with "Display Extra Values" set to "Yes" in the case read-only is true. If the lookup doesn't return a value it just displays [ ], but because the property is set to yes it should display the value. The Popup Key Lov has the same bug.
    Thanks for bringing some light into that behavior
    Patrick
    Oracle APEX Essentials: http://essentials.oracleapex.info/
    My Blog, APEX Builder Plugin, ApexLib Framework: http://www.oracleapex.info/

    Patrick,
    I've added your comments to a task already in our queue to examine all item types for correct behavior in read-only mode. I've noticed the quirks with display extra values also.
    By the way, still interested in your thoughts re: Re: Bug Report: Images broke when using get_blob_file_src and not authentic .
    Scott

  • Read Only Condition Question

    Hello,
    I would like the fields on the screen to be Read Only when the current
    person logged on is not the person that created the Record.
    The following case works in the Read Only condition:
    NOT Exists (SQL query returns no rows)
    SELECT 'X' FROM DUAL WHERE :P90_ASSESSOR_USER_ID = :GLOBAL_USER_ID
    But this does not work:
    Value of Item in Expression 1 != Expression 2
    EXPRESSION 1: P90_ASSESSOR_USER_ID
    EXPRESSION 2: GLOBAL_USER_ID
    I've tried changing the Expression 1 & 2 fields to be prefaced with : and & and also used V('P90_ASSESSOR_USER_ID') and NV('P90_ASSESSOR_USER_ID'),
    but can't get the second way to work. Anyone know why?
    Happy Holiday Season!
    Carol

    Try
    IN EXPRESSION 1
    P90_ASSESSOR_USER_ID IN EXPRESSION 2
    :APP_USER Cheers,
    Hari

  • Tabular Form - Read only condition for certain users

    Is it possible to make a select list field in a tabular form read-only to certain users? Here's the situation:
    The tabular form lists the users who need to select "Approve" or "Reject" in that field (they are approving or rejecting an engineering change)
    I want all of them to see the approval/rejection of their team, but only have access to edit the select list associated with their record.
    Thanks in advance.
    Apex 4.0.0.00.46

    You could use either "authorisations" tab or "conditional display" for the relevant column attribute.
    Report Attributes->Column Attributes->authorisationsIt would be better to have some more detail about what you are trying to get (maybe a quick mock up of the form, for example) but, I can envision something along the lines of the following:
    For each approval/rejection field:
    1. Create an authorisation appropriate for access to to each approval/rejection field e.g. authorisation scheme "FOO"
    2. In the relevant fields column attributes, set the authorisation to "FOO"
    3. now create a read only "public" copy of the above field, using the "display as text (based on LOV does not save state)" - set the authorisation for this field as "{NOT FOO}"
    (if you don't want to use authorisations, you could build an equivalent using "conditional display" instead, which is basically the same thing, except column specific)
    The downside is of course that you're duplicating fields in your query, which creates a bit of redundancy. There may be better ways to achieve this (maybe you could make use of the APEX_ITEM api, for example) but this is fairly easy to set up IMO.

  • Why does my sub-projects open in read only when master is opened

    I have created a master schedule with 4 sub-projects inserted as read only.
    My problem is that when the master is opened the sub-projects will only open in read only so PMs can not update their schedules when requried.
    I have sold my company on using master schedules and ow it doesnt work any better.  I have not had this problem previous using MSP 2010 so can anyone help me please.

    Krys,
    You are using a dynamic master and that may not be necessary nor the best choice in your situation. You say you use the master as a reporting tool and for creating links between subprojects. I have a suggestion. When you need to create cross-project links,
    go ahead and create a dynamic master, make the links and then save, but don't close, each the subproject file. That will preserve the links you just make. Now close the master and when it asks if you want to save changes to all files, answer "no to all". Finally
    delete the master, it is no longer needed to maintain those links and in fact, having a dynamic master creates another level in the linking structure and thus increases the chance of file corruption.
    When you need to do your reporting, create a static master. Simply uncheck the "link to project" option in the lower right corner of the Insert Project window. That will create a separate file that is a snapshot in time of all the subproject files. The advantage
    is that you have not created a linked structure and thus have not added to the corruption dice roll, as Rod Gill (MVP) likes to say. And yes, you will have to create a new static master each reporting period, but that is easily automated with a recorded macro,
    if doing it manually is a burden.
    Hope this helps.
    John

  • Always "Read-only" in dimension detailed view, OWB10gR2

    In OWB10gR2, let's get any dimension open in the "Data Object Editor", then click on dimension object, right button menu and select "Detail View". The editor shows as expected, the dimension itself and the underlying table, however in the lower pane where we can select tabs(Storage, Attributes, Levels, etc.) it always says "Read-only". Why is that? According to my security settings, I do have full control over these objects.
    Can anyone explain this to me?
    Thanks,
    vr

    Everyone, the "detail view" is read only becuase you aren't allowed to change settings here. If you notice, there should be a set of tabs at the top that say "relational", "dimensional", "business definition", and something else for the detail view (can't remember now). It appears that you can only change settings when on the "dimensional" tab - so just click there and you'll be good to go.
    Hope this helps,
    Scott

  • How to make rows read only conditionally

    Hi All,
    I have a query region and when i select it shows the data in a table region, now based on a particular column i want to set the entire row read only.
    Please let me know if it is possible.
    Thanks
    Tom.

    Hi All,
    I have finally figured out a way, i have created a SPEL attribute and set it to the read only property to all of the view attributes, and as soon as the query is executed i am filtering the rows based on my column criteria and set the value of the SPEL attribute to true.
    Thanks again.
    Tom.

  • Authorization scheme for display/read only conditions on item level

    Hi All,
    I have question. I want to use an authorization scheme to manage if users with a certain role have the permission to either update an item or have the persmission to only see the item or that they don't have permission to see it at all.
    So, the input for the scheme would be: 1. user role 2. the current page 3. the current item.
    The output would be: 0 (update) 1 (read only) 2 (not displayed).
    I think I can manage that.
    And I can attach this schema to the items.
    So far so good.
    But how can I make it so that the 0,1 and the 2 will actually do what they need to do?
    I have been thinking about making a function like GET_AUTHORISATON(ROLE,PAGE,ITEM) output: 0,1,2 but I still can't figure out how to connect this with the functionality I want to achieve.
    Can somebody give me a hint?
    Andre

    Thanks Hari,
    Thanks, it works, almost, but what if items are mandatory on a page, but not always mandatory?
    If a user has a certain role, some fields are manadatory, otherwise not.
    Again, a function would do the trick as far as the input and output information
    something like IS_MANDATORY(USER_ROLE, CURRENT_PAGE, CURRENT_ITEM) but how can I make it work?
    I guess a PL/SQL validation like:
    IF IS_MANDATORY(USER_ROLE, CURRENT_PAGE, CURRENT_ITEM) THEN ITEM IS NOT NULL
    END IF;
    Andre
    PS: personally I think item level security is not something you wish to implement in your system. I prefer different screens for different roles.
    Far more straightforeward. Easy for maintenance. When something disfunctions, it's far more easy to pinpoint the location of the cause.

  • Bug report: Read Only Condition Type

    See
    http://htmldb.oracle.com/pls/otn/f?p=24317:105
    The item with label "readonly" has a readonly condition set to 1=1 so it should always display as readonly. But no matter what item type I change it to, setting this readonly condition makes it dissapear.
    Thanks

    Ah, I was mixing up "readonly" and "disabled". I expected readonly to show up as a regular text field but non-editable.
    You are right, thanks for clearing that up.
    Hope this bug with the readonly feature gets fixed soon. The workaround (define 2 "mutually exclusive' items and conditionally display one or the other) gets to be a pain since that readonly feature is (supposed to) solve this problem much more elegantly.
    Thanks

  • Help needed with 'Conditions' for field with read only on demand

    Hy guys,
    I really need your help now, i have two items named P22_LOGIN_TYPE (..wich can be 'Default' or 'Special') and P22_PASSWORD, i need to turn to 'read only' the second item when the first item is 'Default', i'v tryied the conditional option but with no success, i know is managed from there but it's not working for me, it seems that i don't know exactly how to do it. By the way, i have APEX 2.2.
    I need an exact guide (explanation) on how to do it, thank you very much.
    Best regards,
    Victor

    Firstly you could set your First item to be a select list with submit. Make the branch go to the same page.
    Secondly, on the read-only conditions for your second item, use the condition when item in expression 1 = value in expression 2, and set that to 'Default' in expression 2.
    Essentially this will re-submit your page when you make a selection either 'Default' or 'Special'. If 'Default' is selected, then the PASSWORD item will be rendered as read-only. If you don't want to display the PASSWORD item at all, you can put the above condition for the read-only, into the conditions section of the item.
    Hope this helps and is not too confusing. It reads a lot worse than it actually is ;)
    Cj

  • Old items are not populated after adding items into a master/detail form

    Hi,
    I am relatively new to APEX. I am creating a master/detail form. It works well. When I add new items the older items are no more populated. Why ?
    For example I have an itme which is a select list as a Named LOV. At creation of the row I want the user to choose from this select list. It works well.
    But when modifying the record, I don't want the user to change this name. For that purpose, I create an item which is a display only item. This item is conditional and appear only when the record has been created.
    And this is where the problem comes. It seems to work but, if I logout of the application and login, then values are no more populated to the items and I get an error when trying to update the form.
    I hope I make it clear. I have been trying a lot of times and found that if I add items, then everything goes wrong.
    Thank you for your kind help.
    Christian

    Hi Christian,
    You don't say what the error is that you are getting - this may help us with your problem!
    On the form, do you now have TWO fields - one being the original select list and the other being a read-only version of it? Is it likely that BOTH fields could appear on the page at the same time AND that both are connected to the field on the table?
    You can set the select list to be read-only conditionally - in this case you could make it read-only on the condition of the primary key field not being null.
    Andy

  • Master/Detail form with modal edit

    I have a master/detail form that I generated using the wizard that I want to change to have a modal Edit button; i.e. the behavior I want is that the form view is initially read-only and you then have to click an Edit button to make the form editable.
    I figured out how to do this for the master row by making the edit button redirect back to the same page with the request set to 'EDIT' and then making all the page items read-only with a condition REQUEST <> 'EDIT'.
    I cannot find a good way to do this for the detail rows, which are actually a report with editable columns. The problem is that the 'Tabular Form Element' section of the 'Column Attributes' page does not have a read-only condition.
    The only work around I can come up with so far is to have a second read-only report region with the same SQL query and then display either the editable or non-editable report region conditionally depending on whether the request is EDIT. But this obviously not ideal (having same SQL in two places, etc.).
    If anyone can think of a better way to do this, I'd be grateful.
    HTML DB Team: Can you log the addition of a read-only condition attribute on editable report columns as an enhancement request?

    Simply add the lookup table to the FROM clause and join its PK with the FK in the master table in your query. That's basic SQL, and you definitely must get a good grasp of SQL to do more than very basic work in APEX.
    For a good example, please see http://download.oracle.com/docs/cd/E10513_01/doc/appdev.310/e10498/build_app.htm#BCEBJJGB
    While you're at it, read and implement the tasks outlined in the 2 Day + Application Express Developer's Guide - http://download.oracle.com/docs/cd/E10513_01/doc/appdev.310/e10498/toc.htm. After that, read the "Oracle Application Express 3.0-- Building a Functional Application" OBE in http://www.oracle.com/technology/obe/apex/obe30/apexdev30.htm - great stuff.
    Georger

  • How to make form as read only when another time as  user sees it..

    Hi All,
    I have a form to raise the issue. once the issue is raised it appears in the issue raised reports( that is form on a report )
    so all can view this report and click on issue no ..the form with details appear .
    but i want to restrict it , by allowing only one up manager to view the form on a report in editable format rest all can just view it .
    how can i do this?????????
    can any one help me with this ????..
    my approach is like this ...
    a column called "checked shud be added to issue table , then its values must be set to "raised" when issue is submitted for the very first time..( so it is zero when the end user is submitting it ).
    when ( the logged in user =1 up manager or checked!="raised") then
    form fields to be displayed as edited
    else
    form fields need to be read only .
    Thanks & Regards,
    Nandini Thakur.
    Edited by: Nandini thakur on Jun 26, 2010 12:04 PM

    Nandini,
    If you edit any item, you can see a section where you can specify "Read-Only" condition. Here you can write your read-only logic using SQL OR PL/SQL or predefined conditions.
    Cheers,
    Hari

Maybe you are looking for