tag:blogger.com,1999:blog-5874979429188093780.post7563180098563790345..comments2024-03-18T06:46:54.352+01:00Comments on Andrej Baranovskij Blog: Defining the LOV on a Reference Attribute in Oracle ADF 11gAndrej Baranovskijhttp://www.blogger.com/profile/04468230464412457426noreply@blogger.comBlogger43125tag:blogger.com,1999:blog-5874979429188093780.post-37591148290553776462017-10-28T15:16:56.512+02:002017-10-28T15:16:56.512+02:00Hello there. Thanks for your great helpful blog.
C...Hello there. Thanks for your great helpful blog.<br />Considering your sample, let's suppose JobId is not mandatory in EmployeesView. Hence, when one attempts to set a currently null JobTitle to a not-null value, an error similar to what Delia commented will happen. It seems the reason is the lov tries to insert a new row on it's view accessor, or something like that.<br />In other words, if JobId in JobsView is mandatory, the error is like: Attribute JobId in JobsView1 is required. And if JobId is not mandatory, the error is like: It cannot insert to Attribute JobsView1.<br /><br />Is there any solution?<br />BTW, it seems the sample application download link is dead!Anonymoushttps://www.blogger.com/profile/07990756482397141334noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-26957898298806455742015-10-16T16:13:54.938+02:002015-10-16T16:13:54.938+02:00Allowing me to download the source code was of hug...Allowing me to download the source code was of huge help. I was struggling with a very simple thing using the LOV and checking your example I was able to quickly resolve the problem. As I am new to ADF some stuff still consume a lot of my time. Thanks for your post!Fernando R. DalSottohttps://www.blogger.com/profile/06650385430034944480noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-57757498282431481502015-09-03T21:04:58.527+02:002015-09-03T21:04:58.527+02:00Hi Andrejus,
I am struggling on one issue from p...Hi Andrejus,<br /><br /><br />I am struggling on one issue from past one week. Can you please help me out in creating LOV where I have only one table with Columns Name, Address, Job. And I need to create LOV for name and Address on one form with Select One Choice and populate list with Uniques list of Name and Address.<br /><br /><br />Thanks & Regards,<br />VikrantAnonymoushttps://www.blogger.com/profile/01189709688008048666noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-69032147820023739672014-12-07T20:24:09.706+01:002014-12-07T20:24:09.706+01:00Hi Marko,
I have tested and it works well in ADF ...Hi Marko,<br /><br />I have tested and it works well in ADF 12c (12.1.3). No error reproduced.<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-30964798525810177192014-11-28T07:51:28.531+01:002014-11-28T07:51:28.531+01:00Hi Marko,
I will need to test this, thanks for th...Hi Marko,<br /><br />I will need to test this, thanks for the question.<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-49368261373068368602014-11-28T00:40:54.055+01:002014-11-28T00:40:54.055+01:00Hello Andrejus,
Did you try find mode in this sam...Hello Andrejus,<br /><br />Did you try find mode in this sample on 12c or 11.1.2? I am getting <br /><b><br />JBO-25009. Error message parameters are {0=oracle.jbo.domain.Number, 1=HrModule_EmployeesView1.__DefaultViewCriteria__._DefaultViewCriteria_Row_, 2=java.lang.String}<br /></b><br />It happens every time when lov have more than one column in join. Is there any workaround for this case? Do I need to create SR for this is this a bug? Appreciate any help.<br /><br />RegardsMarkonoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-69593151462996887712014-06-16T06:39:37.527+02:002014-06-16T06:39:37.527+02:00Hi,
I used the transient lov for an attribute as ...Hi,<br /><br />I used the transient lov for an attribute as u mentioned,<br />whereas i'm implementing it as panel with table design,<br />lov is working fine in table level, but while selecting values from search area(query panel), it displays all the records instead of matched records. how to resolve it..?<br />Miraclehttps://www.blogger.com/profile/03341422425698339265noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-89322366509234098262012-01-30T10:09:39.370+01:002012-01-30T10:09:39.370+01:00Hello Andrejus,
I am creating the LOV with popup.I...Hello Andrejus,<br />I am creating the LOV with popup.I have created a read only VO and associated the VO as view accessor to the base VO.I associated the corresponding attribute with the LOV.Now the pop up is coming fine, but when I am selecting any value in the popup,everytime the first value from the search is getting selected,irrespective of selecting any other value.Any suggestions regarding this.Gauravhttps://www.blogger.com/profile/09012723861792702102noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-78082770635955558392011-11-15T13:48:16.820+01:002011-11-15T13:48:16.820+01:00Hello Andrejus!
I am trying to create a inputComb...Hello Andrejus!<br /><br />I am trying to create a inputComboboxLOV as a column in a table. I have two EOs with master detail relationship. Master EO holds the FK from a details table. I wish to replace this FK with a LOV from detail table. What is the correct way to do this? When a user selects a value for a master table from this LOV, I want to handle the change programmatically.Andrejs Daskohttps://www.blogger.com/profile/10744582547029203737noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-13597997351076438172011-06-14T16:27:12.364+02:002011-06-14T16:27:12.364+02:00Same approach works for me even in create mode - L...Same approach works for me even in create mode - LOV is editable.<br /><br />Must double check your implementation...<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-82398061223402658312011-06-14T14:58:40.473+02:002011-06-14T14:58:40.473+02:00Hi Andrejus,
I have tried implementing the same, b...Hi Andrejus,<br />I have tried implementing the same, but in the creation mode the reference entity attribute is shown as read only. In my task flow, the createinsert method of the base EmpVO is the default activity and after that i am showing the Create Employee page. The attribute is coming as readonly. Do you suggest any other approach where the same form has been used in Create and Update mode both.<br />ThanksDeepakMCAhttps://www.blogger.com/profile/09657857773055254380noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-32968431748164705252011-05-20T22:42:17.161+02:002011-05-20T22:42:17.161+02:00Hi,
I'm not exactly sure about your requireme...Hi,<br /><br />I'm not exactly sure about your requirement. But second idea looks more close - VO join. First one is Master-Detail, and third - transient fields - no point having them.<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-31202931271570064852011-05-20T08:33:30.966+02:002011-05-20T08:33:30.966+02:00Hi Andrejus,
I am porting my forms based applicat...Hi Andrejus,<br /><br />I am porting my forms based application in ADF and i am having a problem in the following scenario:<br />I have three tables, One for location, second for countries and third for cities which also contain country id as foreign key. Location table has foreign key of city table only. Now in a new location form, I want to have three fields. Address line from location, country name from country table and city name from city table. Requirement is that either user can select city from LOV or can create new city. So how should i do this. One idea was to create a view linke between locationVO and cityVO. second idea was to create a VO based on LocationEO and then add CityEO and CountryEO as reference entities but CountryEO as updatable, and third idea was to create VO based on Location and then add transient fields for city and country. What do u suggest?amer sohailhttps://www.blogger.com/profile/03123932514283187533noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-15568912024661940372011-03-07T17:49:28.078+01:002011-03-07T17:49:28.078+01:00May be I could help, by looking into your sample a...May be I could help, by looking into your sample app.<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-50864056744714355012011-03-07T17:46:04.624+01:002011-03-07T17:46:04.624+01:00Hello Andrejus,
I cannot update the field. In the ...Hello Andrejus,<br />I cannot update the field. In the jspx I see inputListOfValues component, but in the web browser, I see just non-editable text without LOV button and displaying the correct value. <br />I see inputListOfValues component just when I check updatable for for reference entity(like checkbox in the 5th image, you have it unchecked). But when it's checked, it does not behave correctly.<br />Do you have any idea what could I change, please?<br />Thank you in advise<br />TonyTonynoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-75009462848634525132011-02-12T18:57:59.057+01:002011-02-12T18:57:59.057+01:00Andrejus, thank you!
I'll prepare sample app ...Andrejus, thank you!<br /><br />I'll prepare sample app and two tables with data for this case and send you!!<br /><br />SY, Andrey.Andreynoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-18263500403423339712011-02-12T18:33:26.129+01:002011-02-12T18:33:26.129+01:00Ha ha, most funny comment I ever received :)
If y...Ha ha, most funny comment I ever received :)<br /><br />If you could send me your sample app, I could look into it. Hard to advice something without seeing code.<br /><br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-10548118762272166162011-02-12T17:57:08.819+01:002011-02-12T17:57:08.819+01:00Good day again.
Solve this problem by using calcu...Good day again.<br /><br />Solve this problem by using calculations on transient fields (getting row from LOV Accessor by key value), but still have feelings - this solutiong is not right. Like trying to stretch condom on terrestrial globe :)<br />I would be very grateful, if anyone suggest "right" solution (by using returning values of LOV).<br /><br />SY, AndreyAndreynoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-20857374644608056312011-02-12T01:22:42.168+01:002011-02-12T01:22:42.168+01:00Andrejus, good day!
May be you can help me with c...Andrejus, good day!<br /><br />May be you can help me with case:<br /><br />Have 2 views. First - updatable, base on Entity, which have FieldId attribue, and second - readonly, based on query, which have - FieldId (key), FieldName, FieldDescription.<br />In first view i make transient field "FieldDescr" (update always) and LOV (for view-2 as LOV source) for "FieldId" with display field "FieldName" and returns (view2.FieldId -> view1.FieldId,<br />view2.FieldDescription -> view1.FieldDescr).<br /><br />When i open first view - i see: FieldId displays correct (show name of key value), and FieldDescr is empty. When i change value of FieldId - FieldDescr display corrent value (i.e. FieldDescription of key value).<br /><br />So question is: I doing something wrong to display other attributes from LOV or it's a bug?Andreynoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-46708705944429674172010-08-16T19:33:45.670+02:002010-08-16T19:33:45.670+02:00I used your example, but wanted to additionally re...I used your example, but wanted to additionally return maxsalary in the employee query.<br />I added the field as reference in the VO and as return value in the LOV.<br /><br />However the LOV funtionality is lost a run-time.<br />Please help. <br />Have i done something wrong or is this a bug? Any workaround?<br />thanksUnknownhttps://www.blogger.com/profile/17066666676718257949noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-87598994348087530642010-06-03T12:05:40.561+02:002010-06-03T12:05:40.561+02:00Hi Andrejus,
Yes, you are wright. The attribute J...Hi Andrejus,<br /><br />Yes, you are wright. The attribute JobTitle was not mandatory in entity. I should have noticed this from the missing "*" in the form.<br />Thanks for your help.<br /><br />DeliaDeliahttps://www.blogger.com/profile/04120214583556807213noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-70542657405523450502010-06-03T11:31:55.772+02:002010-06-03T11:31:55.772+02:00Hi Delia,
Thats correct behavior - JobTitle attri...Hi Delia,<br /><br />Thats correct behavior - JobTitle attribute is not set as Mandatory, but JobId is mandatory. So, Model layer protects JobId and show error message to the user.<br /><br />If you want to protect JobTitle and show nice red highlight border, you need to set JobTitle attribute as Mandatory=true on Jobs EO. Then it will invoke validation earlier, on JobTitle.<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-21182037507520522862010-06-03T11:10:28.969+02:002010-06-03T11:10:28.969+02:00You can run the app you uploaded for this post. Sa...You can run the app you uploaded for this post. Save the form with no value for JobTitle field. You will get the error that I was talking about.<br /><br />Regards,<br />DeliaDeliahttps://www.blogger.com/profile/04120214583556807213noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-69233996753917853112010-06-03T11:03:08.513+02:002010-06-03T11:03:08.513+02:00Ok, it should work generally. If you want, you can...Ok, it should work generally. If you want, you can send me sample app, I can take a look...<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-11199464489817403012010-06-03T10:55:24.078+02:002010-06-03T10:55:24.078+02:00Hi,
In this case we don't get a nice validati...Hi,<br /><br />In this case we don't get a nice validation message saying that a value is required. We get a JBO error in stack trace, which means that the database table did not get a value for the mandatory attribute JobId. <br /><br />Regards,<br />DeliaDeliahttps://www.blogger.com/profile/04120214583556807213noreply@blogger.com