I have a read only item on a page which is a calculation using date from two other fields. I use a search button that basically refreshes the data on the page. However, the refresh (fetching data relevant to new search) works as long as the item is not read only. The moment I make it read only, a new search is errored out. Any idea?
Srini-S wrote:
I have a read only item on a page which is a calculation using date from two other fields. I use a search button that basically refreshes the data on the page. However, the refresh (fetching data relevant to new search) works as long as the item is not read only. The moment I make it read only, a new search is errored out. Any idea?
Please do not post screenshots in when describing an issue. Screenshots are not accessible to visually impaired users, cannot be searched, unnecessarily bloat forum post sizes, and do not permit copying and pasting of code or settings in order to reproduce a problem. Moreover, even on very large displays most property sheets extend beyond the dimensions of the viewport so it is impossible for a single screen shot to include all of the component properties. As a result of this, users post cropped/edited images containing what they think is relevant, usually missing out critical details and/or contextual information that is essential in understanding the overall situation—as is the case here.
Post code and property settings as text, or share a demonstration of the problem on apex.oracle.com.
This is occurring because the value of the COMPLETION_DATE_3 item is being modified. Since it is defined as a display-only item that saves session state, this is not permitted. Is this item value only for display purposes, or is it referenced elsewhere?
Thanks for your response. It is for display to the user as of now, but we may have to pass on the resultant value to the package that is being called along with other values from this page as well.
That works, thank you. Will I be able to send this field's information by calling a package along with other page's data?
Srini-S wrote:
That works, thank you. Will I be able to send this field's information by calling a package along with other page's data?
No, which is why I asked before suggesting changing the Save Session State property. Only mark threads as correct when you are sure the problem is completely resolved.
Srini-S wrote:
Sure, do you have an alternate suggestion please?
Set the Save Session State property of the display-only item to No.
Create an additional hidden and unprotected item to mirror the value. In the dynamic action, copy the calculated value to both the display-only and the hidden item. Reference the hidden item to get the value in the dependent code.
Hi,
normally yes but since @fac586 is not happy with my solution i have one that will satisfy your requirements completly.
#P1_YOURITEM{
border: none;
}
this should do the trick. and no additional Dynamic action required.
regards,
Franck
i mean like this.
just replace "P1_YOURITEM" with the name of your item.
My question was: What are we telling the system through this code? What will it do?
Do the hidden items get updated with dynamic action everytime we change a value and refresh so that latest value is passed to the package?
Hi,
setting the attributes as readonly as i suggested will restrict the users interaction with the Item. But the borders lines will still remain on the item.
Using that css code will remove the border line arround the box and make that item look like a read only item.
regards,
Franck
Srini-S wrote:
Do the hidden items get updated with dynamic action everytime we change a value and refresh so that latest value is passed to the package?
If that's what you configure the DA to do. Add another Set Value action to set the hidden item, and reference the name of the hidden item in any Page Items to Submit properties instead of the display-only item.
