Master Detail Highlighting

Hi,
I have a master detail type form.
When I select record 1 in my Master block and go to next block (detail), I would like to have the record 1 highlighted, so that my users now which record they are editing.
I have tried to set the currect record visual attibute to DEFAULT for both blocks, but nothing seems to happen. Has anybody done this before?
I am using Forms 9i
Thanks in advance.
VC

You can set a visual attribute in the "Current record attribute" in the block property. This will show the current record in which you are.
I have created a visual attribute named RECORD with the following properties:
Foreground color: white
Background color: blue
Then in the property palette of a certain block, I have set property "Current record visual attribute group" to RECORD.
In this way when I move from one record to another the current record is highlight.
Hope it helps you,
Fabrizio
If this answer is helpful or correct, please mark it. Thanks.

Similar Messages

Keeping Row Highlighted In Master-Detail Table

JDev 11.1.2.0
I have a small .jsf page with a master-detail setup, using 2 tables.
When I select a row in the master table, the detail table is populated as expected.
When I select a row in the detail table, the row is no longer highlighted on the master table.
Is there any way to have the row selection in the master table remain highlighted while the user is clicking around the detail table?
I am not sure if it matters but I have manually added filtering to both tables.
Thank you.
Ray

Any help would be appreciated.

ADF master-detail master selection not updating detail tables properly

Hi All,
I am using JDev version : 11.1.2.0.0
I created new Fusion Web Application Module. In that module I created a master-detail data model and added them to a page fragment with a query panel. When I run it as a separate module, It works perfectly and Master selection correctly updates detail tables.
But when I integrate that module to another Fusion Application(Add application jar file to the Master Application libraries), Master-details master selection not updating detail tables properly. This problem occurred sequentially.
The problem is that.
After the page load, first selection of the Master Table works correctly and detail tables update correctly.
But second selection doesn't work, means detail table doesn't get update according to the Master table.
And again in the third selection works correctly.
This happens in a sequential manner. I monitor the behavior using Firebug. Observations are as follows,
When running correctly, Response of the Post Definition is
<?xml version="1.0" ?> <partial-response><changes><update id="pt1:t1"><![CDATA[<div tabindex="0" id="pt1:t1" class="xpa xpi" _leafColClientIds="['pt1:t1:c1','pt1:t1:c2','pt1:t1:c3','pt1:t1:c4','pt1:t1:c5','pt1:t1:c6','pt1:t1:c7','pt1:t1:c8','pt1:t1:c9','pt1:t1:c10','pt1:t1:c11','pt1:t1:c12','pt1:t1:c13']"><div id="pt1:t1::ch" style="overflow:hidden;position:relative;width:1365px;" _afrColCount="13" class="xz4"><table class="xz6" summary="This table contains column headers corresponding to the data body table below" id="pt1:t1::ch::t" style="position:relative;table-layout:fixed;width:1365px" cellspacing="0"><tr><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th><th style="padding:0px;padding-left:5px;width:100px;"></th></tr><tr><th id="pt1:t1:c1" _d_index="0" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c1::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DateFormat</div></th><th id="pt1:t1:c2" _d_index="1" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c2::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">DefinisionId</div></th><th id="pt1:t1:c3" _d_index="2" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c3::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldId</div></th><th id="pt1:t1:c4" _d_index="3" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c4::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLabel</div></th><th id="pt1:t1:c5" _d_index="4" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c5::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldLength</div></th><th id="pt1:t1:c6" _d_index="5" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c6::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOffset</div></th><th id="pt1:t1:c7" _d_index="6" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c7::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldOrder</div></th><th id="pt1:t1:c8" _d_index="7" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c8::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldStatus</div></th><th id="pt1:t1:c9" _d_index="8" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c9::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldType</div></th><th id="pt1:t1:c10" _d_index="9" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c10::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">FieldTypeLen</div></th><th id="pt1:t1:c11" _d_index="10" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c11::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IgnoreField</div></th><th id="pt1:t1:c12" _d_index="11" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c12::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">IsMandatory</div></th><th id="pt1:t1:c13" _d_index="12" _afrLeaf="true" _afrRoot="true" align="left" class="xz7"><div style="position:relative; float:right"><table id="pt1:t1:c13::afrSI" _afrHoverable="true" style="display:none" class="xzs" cellpadding="0" cellspacing="0"><tr><td _afrSortAsc="1"><a tabIndex="-1" class="xza" title="Sort Ascending"></a></td><td _afrSortDesc="1"><a tabIndex="-1" class="xzb" title="Sort Descending"></a></td></tr></table></div><div class="x19d">RecordType</div></th></tr></table></div><div id="pt1:t1::db" class="xyx" style="position:relative;width:100%;overflow:hidden" _afrColCount="13"></div><div id="pt1:t1::sm" class="xzt" style="position:absolute;display:none"></div><div id="pt1:t1::ri" class="xyz" style="position:absolute;display:none;overflow:hidden"></div><div id="pt1:t1::dataW" style="display:none"></div></div>]]></update><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="d1::iconC"><![CDATA[<span id="d1::iconC" style="display:none"><span id="af_table::disclosed-icon"></span><span id="af_table::undisclosed-icon"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval><![CDATA[AdfPage.PAGE.sendStreamingRequest("pt1:t1");]]></eval><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/dnd-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/nav-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/menu-SHERMAN-1147.js</extension><extension id="adf-script-library">/MillenniumCSD-ViewController-context-root/afr/partition/gecko/default/opt/table-SHERMAN-1147.js</extension><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){ self.location = "mcsd.html"; }</eval><eval><![CDATA[AdfDhtmlLookAndFeel.addSkinProperties({"af|table-tr-column-scroll-animation-duration":"300","af|table-tr-column-reorder-animation-duration":"600","af|table-tr-hover-highlight-row":"true"});AdfPage.PAGE.addComponents(new AdfRichTable('pt1:t1',{'rowSelection':'single','rowBandingInterval':0,'editingMode':'none','afrSelListener':true}),new AdfRichColumn('pt1:t1:c1',{'sortProperty':'DateFormat','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c2',{'sortProperty':'DefinisionId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c3',{'sortProperty':'FieldId','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c4',{'sortProperty':'FieldLabel','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c5',{'sortProperty':'FieldLength','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c6',{'sortProperty':'FieldOffset','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c7',{'sortProperty':'FieldOrder','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c8',{'sortProperty':'FieldStatus','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c9',{'sortProperty':'FieldType','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c10',{'sortProperty':'FieldTypeLen','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c11',{'sortProperty':'IgnoreField','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c12',{'sortProperty':'IsMandatory','sortable':true,'minimumWidth':12,'rowHeader':false}),new AdfRichColumn('pt1:t1:c13',{'sortProperty':'RecordType','sortable':true,'minimumWidth':12,'rowHeader':false}));AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
When not running correctly, Response of the Post Definition is
<?xml version="1.0" ?> <partial-response><changes><update id="f1::postscript"><![CDATA[<span id="f1::postscript"><span id="f1::postscript:st"><input type="hidden" name="javax.faces.ViewState" value="!-75cc188st"></span></span>]]></update><update id="javax.faces.ViewState"><![CDATA[!-75cc188st]]></update><eval><![CDATA[AdfPage.PAGE.__handleRichResponseAction('/MillenniumCSD-ViewController-context-root/faces/FileDefinition?_adf.ctrl-state=cmpl0ptfg_7');]]></eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/jquery-1.7.1.min.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/JarLoaderPages/dis_contx.js');</eval><eval>AdfPage.PAGE.addResource('javascript','/MillenniumCSD-ViewController-context-root/js/floating_bar_bottom.js');</eval><eval>if(self.window.name != "MillenniumDepository"){ self.location = "mcsd.html"; }</eval><eval><![CDATA[AdfPage.PAGE.__recordSessionTimeout(1800000, 120000, "http://127.0.0.1:7101/MillenniumCSD-ViewController-context-root/faces/FileDefinition");AdfPage.PAGE.__initPollingTimeout(600000);AdfPage.PAGE.clearMessages();AdfPage.PAGE.clearSubtreeMessages('pt1:t1');AdfPage.PAGE.clearSubtreeMessages('pt1:resId1');]]></eval></changes></partial-response>
I could not figure out what went wrong when integrating to another module.
Can you please help me to rectify this problem.
Thanks
dk

Hi,
sound to be an implementation specific issue that is hard to comment on without knowing how to reproduce it. If you have a rerooducible test case based on the Oracle HR schema using JDeveloper 11.1.1.6, zip it up, rename the "zip "extension to "unzip" and sent it to the mail address you find in my OTN profile. If you don't have that test case, explain how this can be reproduced
Frank

How Do I: Bind a YUI Calendar Widget to a Spry Master Detail Region?

Hello All,
Does anyone know how to bind a YUI Calendar widget to a Spry
master detail region? I have the dataset, yui calendar inserted but
no clue how to bind the two so my dataset populates the calendar
(Highlights dates that have a event) and when a date in the
calendar is clicked it shows in the details section.
I have found a tidbit or two via google but they don't deal
with the new yui cs4
widget. I have seen some video on adove tv that touches on
inserting the yui calendar into a spry dataset but not how to bind
the two together...
Any thoughts on this would be greatly appreciated.

You have to write some code that sets up a select callback on
the YUI side of things, and then set the current row of the data
set that matches that date.
Something like this:
var cal1 = new YAHOO.widget.Calendar("cal1","YUICal1");
cal1.render();
cal1.selectEvent.subscribe(function(type, args, obj)
// Get the selected date string from cal1.
var selectedDate = cal1.getSelectedDates()[0].getDate();
// Find the first row in the data set that has the
// selected date in it's "date" column.
var row = ds1.findRowsWithColumnValues({"date":
selectedDate}, true);
// If we have a matching row, make it the current row for
the data set.
if (row)
ds1.setCurrentRow(row.ds_RowID);
}, cal, true);
--== Kin ==--

Master Detail Form Question

I would like to create a master detail form that is essentially 2 tabular report regions. Is this possible?
Basically I would like to have region A that shows all of the relevant information for higher level items (there are multiple of these higher level items). I would then like to have region B which would show me all of the lower level details for the higher level item that was selected in region A. Is there a way to read the row that you are on in region A and only show those related items in region B?
Thank you!
Amber

Are you asking to create two tabular reports on one page (Reports that are editable), or do you just want two reports on one page (non editable) where you select a row in the first and the second displays the detail records of the selected row in the first, highlighting the the selected row in the first report?
If you want the two editable reports, then the answer is no, you can only have one tabular form on a page.
If you only want two reports, or perhaps the top report as a non editable report and the second as an editable report, then it is possible to do this.

2 different master/detail data sets

Hello. I have created a master/detail dataset for a photo gallery, with customised css. Whenever I tried to use this same spry tool for different purposes, so with different customised css, the photo gallery data set was roped into the new layout. To make the two independent, I tried saving the master/detail css of the photo gallery to an external style sheet - not sure why (I'm new to this), thought it would detach those rules from the default settings. Now when I add a new data set it appears with no css attributes at all. Help much appreciated.

I understand completely the desire to do something that turns out to be really complicated! But therein lies a real goal.
Have you uploaded this to a server, so I can see your code in action (or frozen...as the case may be!)?
To target specific IDs:
Wrap the entire masterdetail widget in a div:
<div id="galleryone">
<div class="MasterDetail">
        <div spry:region="ds1" class="MasterContainer">
          <div class="MasterColumn" spry:repeat="ds1" spry:setrow="ds1" spry:hover="MasterColumnHover" spry:select="MasterColumnSelected">{thumbnail}</div>
        </div>
        <div spry:detailregion="ds1" class="DetailContainer">
          <div class="DetailColumn">
            <h2>{title}</h2>
          </div>
          <div style="position: relative;"><div class="DetailColumn">{image}
          <div class="DetailColumn credit">{credit}</div></div></div>
          <div class="DetailColumn top"><em>{medium}</em>   {size}</div>
          <div class="DetailColumn">{date}</div>
          <div class="DetailColumn">{place}</div>
          <div class="DetailColumn">{price}</div>
          <div class="DetailColumn" id="sold">{sold}</div>
        </div>
        <br style="clear:both" />
      </div>
</div>
Then you can restyle the CSS file by making a complete copy of the CSS file and re-linking it:
@charset "UTF-8";
/* SpryMasterDetail.css */
/* Copyright (c) 2007. Adobe Systems Incorporated. All rights reserved. */
/* This is the selector for the main Master/Detail structure container.
* If you want to constrain the width of the Master/Detail structure, set a width on
* the Master/Detail container. By default, our structure expands horizontally to fill
* up available space.
#galleryone .MasterDetail {
    font: 100% Verdana, Geneva, sans-serif;
    margin: 2px;
/* This is the selector for the Master Container element which houses all the MasterColumn
* classes. By default the Master column occupy about 35% from the width of the
* entire structure.
#galleryone .MasterDetail .MasterContainer {
    width: 99px;
    float: left;
    height: 650px;
    overflow-y: auto;
/* This is the selector for a Master Column element which holds the actual data for
* a master column.
#galleryone .MasterDetail .MasterColumn {
    font-size: 75%;
    padding:5px 10px 5px 0;
    cursor:pointer;
    float: left;
/* This is the selector for a highlighted Master Column element.
#galleryone .MasterDetail .MasterColumnHover {
    background-color: #090;
/* This is the selector for a selected Master Column element.
#galleryone .MasterDetail .MasterColumnSelected {
    padding: 25px 5px;
    color: black;
/* This is the selector for the Detail Container element which houses all the DetailColumn
* classes. By default the Detail column occupy about 60% from the width of the
* entire structure.
#galleryone .MasterDetail .DetailContainer {
    padding:10px 0 0 0;
    width: 605px;
    float: right;
    overflow: auto;
#galleryone .DetailColumn.position {
    position: relative;
/* This is the selector for a Detail Column element which holds the actual data for
* a detail column.
#galleryone .MasterDetail .DetailColumn {
    margin-bottom: 1px;
Notice that I have pre-pended the #galleryone to every style in this stylesheet. Be sure to leave a space after #galleryone. This focuses specifically on the master/detail in <div id="galleryone">. Make sure this file is loaded after any generic master/detail CSS file. Better yet, make all your galleries specific with IDs (both in the page and in a CSS file).
If I only have small changes to make, I would add the additional styles into the generic stylesheet:
.MasterDetail {
    font: 100% Verdana, Geneva, sans-serif;
    margin: 2px;
#galleryone .MasterDetail {margin: 30px;}
Note that I only made a style selector for the one attribute that changed. All the other attributes will remain the same (font: 100% Verdana, Geneva, sans-serif;)
It is possible that styling other than specifically master/detail styling will vary from gallery to gallery.
For instance, if h2 will change from gallery to gallery:
#galleryone h2 {color: red;}
Do this in either your general or your master/detail stylesheet.
Curly brackets are the two keys to the right of the "P" key on the keyboard...shift to get curly brackets.
When you make a secondary stylesheet (named to correspond to its use), you must attach it to your page using the Link icon at the bottom of the CSS Styles Panel. Browse to the file and press the Link radio button. Then your additional styles will show in your stylesheet.
Beth

Visualize master-detail relationships using SQL Edge 1.2

SQL Edge 1.2 released by Bay Breeze Software (http://www.baybreezesoft.com) is an Eclipse Rich Client application that allows users to execute SQL queries, browse schema information, and visualize master-detail relationships.
With SQL Edge, users can use only one query to retrieve data in a master table, and then browse data in all related detail tables. Users can also insert, edit, and delete table records in the data grids.
SQL Edge has four perspectives. The Query Perspective allows users run any SQL queries, while the Schema Perspective displays table schema information. There are two relationship perspectives. The Relationship Table View displays data in the master-detail style. The Relationship Tree View displays master table records as top-level tree nodes. The nodes can be expanded to reveal any level of related detail records. In addition, clicking any node will display the corresponding data in a detail grid.
The following summarizes SQL Edge's major features:
(1) Support any JDBC compatible databases.
(2) Allow users to specify JDBC drivers at run-time, and provide wizards to help setup JDBC connections. Easy to install, and easy to setup.
(3) SQL editor with syntax highlighting based on currently connected databases.
(4) SQL edtior allows users to execute SQL queries asynchronously. Users can cancel the execution by click the "Cancel" button or just close the SQL Editor.
(5) Schema perspective displays the table schema information, including column definitions, primary key, indexes, and foreign keys.
(6) Relationship table view displays the related data in master-detail style, with master table data shown in the top grid, and all related detail table data in a list of bottom grids.
(7) Relationship tree view displays the master table records as top-level tree nodes, and the related detail records as child nodes. Click any of these tree nodes will display the corresponding record data in a detail grid.
(8) Allow users to insert, edit, and delete records in the master and detail grids of the relationship table view and relationship tree view.
(9) Allow users to define master-detail relationships even between tables in different databases. This enables the relationship table view and relationship tree view to display data relationships between tables in different databases or without pre-defined foreign keys.

Hi, Martin.
Maybe you don't need a master detail relationship. Do you need to do changes in your detail block, or just queries?
If just queries, you can create your second block based on a From-Clause Query, and change the QueryDataSourceName property with a When-List-Changed trigger in your T-List.
I know this is a little vague but, without knowing what you need to do in the second block, I'm afraid to tell you more.
Feel free to mail me directly, if you need some pointers about Forms.
Pedro

Questions on Master-Detail HTMLDB HOW-TO

Hi all
I have created a 3 page application based on the master detail how-to given at http://www.oracle.com/technology/products/database/htmldb/howtos/index.html
Instead of DEPT and EMP tables I have PERSON and PERSON_ADDR tables. The PK of PERSON is the person_id and the PK of PERSON_ADDR is the person_id and addr_start_dt. Person_id column in PERSON_ADDR is obviously the FK to the master table PERSON(person_id).
At first I had problems trying to create the pages themselves because the wizard always hides the person_id column on all the forms(and I don't want that,even though it is a sequence number I still want people to see it) , it being the PK, then somehow I managed it to display the person_id by replacing the EDIT link with the person_id itself. Now if a person already has an address and I click on EDIT then it copies the person_id values and others to the next page and all looks good but when I try to create a new address it does it ?? (It should take across the person_id as well)
My PERSON report is on page 1, when I click edit against a person it takes me to page 2 where I can see+change all the person details plus I can see the person_addr details. When I click edit against a person address it takes me to page 3 and I can edit all the address details nicely copied to the new page but when I click CREATE on the page 2, then all the fields appear as NULL on page 3( all the fields but the person_id should be null here). How can I fix this ?
Also, for my person address I would like to validate the address dates , there should be no overlapping start and end dates for a person's address. How to do this ? I think I will need to create a function to which I pass the person id and the new start and end dates and this function returns error message,if any, or null. I had a play around with validation and I think I need to use "function returning error text", what should I put in the "validate expression 1" box then...just something like
begin
my_function(param_1,param_2)
end;
If yes, then what variables would store the new start date and new end date of an address.
Lastly, for every table do I have to user a sequence number or a trigger to define a primary key, what if the primary key is just a character code and I want the users to add it ?
Thanks a lot in advance !!

thanks Marc.
Yes you are right, I used the 1.5 viewlet. I will try the master-detail wizard now.
With the primary key problems, for things to work nicely in HTMLDB, do you suggest each and every tables should have a sequence number generated primary key ? We have some tables for various statuses like ACTIVE,CLOSED where these codes themselves are the primary keys, so you suggest making these codes unique keys but still have a sequence number PK ? Also when I want the users to enter the primary key themselves I will let them enter new ones but not update existing ones, so data entegrity is maintained.
I was able to work out how to create validations using "functions returning error text" but my problem is I need to be able to compare what the user has just updated/entered with the data that already exists in the table. I have a table called person_Address having columns like person_id, start_dt,end_dt and various other fields. The primary key is person_id and start_dt and I need to put a validation which avoids any overlapping addresses. Overlap as in there can be only 1 active address for a given start and end date range. Does HTMLDB has something like :new.start_dt the way we can write database triggers ? Please suggest a way to do this.
Lastly, how does HTMLDB handles error messages raised by table triggers. Can they be shown along with the item on the page as we can with the other HTMLDB validations ? I have many tables with all sorts of triggers and if any validation fails I generally do...raise_application_error(-20001,get_my_message(234));
get_my_message function returns the message text for message number 234 . Will this message be displayed somewhere or not ? Do I have to duplicate my validations , once in the triggers and then in HTMLDB as well ?

Master-detail: detail field not displayed after changed by master field

I want to use the Depends on item with Clear/refresh value functionality in a master detail situation. Within the same group it is no problem to use the setter method of a field to change a second field and then displaying this new value. But in the detail group, I can not select items from the master group as a depends on item.
In the setter of the master field, the value in a field for each row in the detail (table layout) is updated. The only problem is that this updated value is not displayed, the old value doesn't change. When saving the changes, the displayed value is committed to the database. When de updated field is not displayed at all, the correct value is saved, so I know the detail field is updated.
How can I make sure the displayed value in the detail is displayed after changeing a master field? I already gave the detail field the correct partial trigger.

Wouter,
I guese you don;t see the changed value when you display the detail item because after the depends on item update changed the detail item, JSF procesing continues and the detail table changes are sent to the server which will override again the detail item attriibute, resetting it to the old, still displayed value.
So, the trick is to get PPR working. Make sure the partialTYriggers property of the detail item is set to the value of the id property of the master item. If it still doesn't work, try setting the partial triggers property on the table, instead of the individual item.
Steven Davelaar,
JHeadstart team

Master-Detail Detail does not refresh after it's been empty

I have a master detail page (both are tables) that works just fine, until I click a master record that has no details.
After that the panelHeader of teh detail is refreshed with the PPT but the table underneath it is not, I keep seeing "no rows yet", no matter which master record I click.
When I go to a different page and return it's fine again.
Only one of my pages has this behavior, I tested this on another and it was fine. Has anyone seen this behavior before?
My console has this message:
May 11, 2007 10:52:38 AM oracle.adfinternal.view.faces.model.binding.FacesCtrlRangeBinding$FacesModel getSelectedRow
WARNING: rowIterator is null
Message was edited by:
Wendy Tromp

Ok I found it,
My details iterator had the following properties:
<iterator id="AfdelingMedewerkersIterator" RangeSize="-1"
Binds="AfdelingMedewerkers"
DataControl="PRBAppModuleDataControl"
Refresh="IfNeeded" RefreshCondition="#{!adfFacesContext.postback}" />
I have no idea why I set it like that, but removing the Refresh properties fixed my problem.
I am still clueless as of why this led to the behavior as described above. I could have understood it if my iterator was not refreshed at all, but I have no idea why it stopped working only after the details were empty and not a second before...
Anyway, problem solved!

Unable to View records in a master-detail form

In a master-detail form, I am not able to view records of the master/detail table
by accepting the values of the PK of the header table items.
Please tell me the exact steps, so that I can view the detail table records based on the header table PK items.
Thanks.

Yes I wrote the LOV code in a different procedure. Now, the view is showing correctly. But I am now trying to update the viewed records.
The steps I am following in View Option is as below:
go_block('header');
clear_block(no_validate);
execute_query;
proc_lov;
go_block('item');
execute_query;
I am unable to commit the changes made in the blocks
The reason it is showing is : UNABLE TO update.....I saw the display_error.
The system is trying to update the PK part also..Why....Though PK party is clearly defined in the table as well as property palette. Pl. explain how to go about it. Uregent help is required once again.

What is the proper way to record line numbers in Master/Detail records?

Guys and Gals,
Been thinking about this for awhile, but thought it best to ask the people who really know what they are doing.
What is the proper way to record & show line numbers in a Master / Detail record set?
For example, take Master/Detail relationship Orders and OrderItems. Orders has a column Document_Number and OrderItems has Document_Number, Line_Number. Line_Number should contain the row number 1,2,3,4 ... etc. for each row in a document.
Should I ...
<ol><li>Add a sequence and a trigger in the database? The FusionOrderDemo does this, but then the sequence never "resets" and I've got row numbers that keep incrementing. So one document has rows 4,5,6 and the next document has 7,8,9 when they should both have 1,2,3.</li>
<li>Programmatically take care of the row numbers? This seems like I'm asking for trouble. Anytime an insert or delete operation gets done, I'll have to iterate through rows and re-assign row numbers.</li>
<li>Is there a way to assign row numbers in a table iterator (or data collection?) to an entity?</li></ol>
Any suggestions would be appreciated. It's looking like #2 is my only option, but if anyone knows different I'd love the input.
Will

Thank you both guys.
As John said, I believe I'm looking for a gap-free sequence per master record.
The line number of the OrderItems table is the second half of the primary key. The first half of the primary key (DocumentNumber) is the foreign key to the Orders table.
Think of it like line items on an order or invoice. For example, if you were talking to someone on the phone concerning an invoice, you might say, "The pricing for line item #3 is incorrect." In this case, it's good to have a common reference. Or imagine a Microsoft Excel spreadsheet with no row numbers displayed! You'd never get anywhere if you had to explain something over the phone.
If this is tricky to perform, I take it using a sequence and trigger such as the Fusion Order Demo is the best way to approach the challenge for simplicity's sake?
Will

OBIEE 11g: Inconsistencies with Master-Detail events and Navigate to BI

Hi everyone,
I'm getting some pretty annoying inconsistencies with the Navigate to BI Content action as well as the Master-Detail events. Basically the main issue I get is that 90% of the time, the click does nothing.
It's a pretty simple setup, I am setting up bulb gauges to act like a fancy column selector. The bulb gauges are setup to pivot based on a Metric Type column. The goal is that if you click on "Metric 1" bulb a trend report should refresh to show Metric 1. If you click on the "Metric 2" bulb, the same trend report will show that metric.
Here's how I implemented it:
Dashboard Tab A -- Uses Navigate to BI Content
1) I have a prompt on Fiscal month in dashboard tab A.
2) I created the bulb gauge and put it in dashboard tab A
3) Setup the interaction on the bulb measure to navigate back to Dashboard Tab A.
3) Prompted the trend on Metric Type column and put it in dashboard tab A.
4) In theory, clicking on the bulb, should navigate back to the same tab and update the trend report appropriately
5) In reality, nothing happens.
6) The only way I can get the navigate to work is if I first change the value in the fiscal month prompt and click Go. Then I click on the bulb and the navigation will work ONCE. After that it's broken again.
Dashboard Tab B -- Use Master Detail -Events
1) Pretty much same situation as dashboard A, but instead of navigate to BI Content, I use the master-detail events.
2) Pretty much the same results. I cannot get it to consistently work, in fact the trick with the filter didn't do anything.
3) One thing I tried was cleared my browser history completely (Mozilla Firefox) and then launched the page. It work for about 5 clicks and then stopped.
Either way, neither of these are working properly for me.
Has anyone else had these issues?
-=Joe
Has anyone else had an issue with this?

So someone explained to me that master-detail events only occur within a single report. They cannot be used to communicate across two different reports.
That is significantly less useful than I originally thought. I honestly that it was a method of communication for one report to update other target reports that are all listening on the same channel. That would have been a powerful feature. A single report refreshing other views in the same report is still useful, but not as much.
That being said, I still don't understand what the heck is going on with the navigate to BI content feature. I've been testing it out. It works with pivot tables and regular tables. But the moment I add a graph, gauge or even a "Filter" view into the dashboard page, the click stops working. Really really strange stuff.

Obiee 11g - Master/detail : How to initialize details ?

Hi gurus,
I'm using the last version of obiee.
I have a dashboard with master/detail. The master/details are working great when I click on cells.
But I have some "initialization" problems.
- master/detail with a prompt list on the master table
a change on the list won't initialize the detail. I would like to have the detail refreshed with the first row of the master.
- master/detail with different order by on master and detail
the initialization value of the detail does not fit with the first row of the master.
Is it possible to achieve this ?
Thanks in advance for your help.
Emmanuel

Hi Dpka,
Thanks for sharing your view . I ,even observe the same 'error' message returining false value at the bottom-left of my browser when set up the Master detail even and clicked my table column to reflect the value in the graph .
But my situation is bit tricky . I can't expose two different views to see if separating the interaction works well or not . In my case I have only 1 report with 4 compound layout(with pivot table(master) and Graph(detail)) having view selector . So this is practically not separable as this incurs loss of other functionalities.
Do you have any suggestion in mind . I tried to see Supportweb and doesn't have any valid bug reported :(
Rgds,
DxP

Master Detail Report for PDF Printing

Dear All,
       While trying to create a master detail report using Oracle APEX 4.2 and BI Publisher. I tried creating report queries and report layout following the below mentioned steps.
CREATE TYPE emp_row AS OBJECT (
EMPNO NUMBER(4),
ENAME VARCHAR2(10),
JOB VARCHAR2(9),
MGR NUMBER(4),
HIREDATE DATE,
SAL NUMBER(7,2),
COMM NUMBER(7,2)
CREATE TYPE emp_tab AS TABLE OF emp_row;
CREATE TYPE dept_row AS OBJECT (
DEPTNO NUMBER(2),
DNAME VARCHAR2(14),
LOC VARCHAR2(13),
EMP_LIST emp_tab
SELECT SYS_XMLAGG (
SYS_XMLGEN(
dept_row(
d.deptno, d.dname, d.loc,
CAST(MULTISET(SELECT e.empno, e.ename, e.job, e.mgr, e.hiredate, e.sal, e.comm
FROM emp e
WHERE e.deptno = d.deptno) AS emp_tab)
SYS.XMLGENFORMATtYPE.createFormat('DEPT')
) AS "XML_QUERY"
FROM dept d
WHERE d.deptno = 10;
Though the above steps generates xml output while trying to generate in APEX it says unsupported datatype. Tried using DBMS_LOB as well no luck. Any inputs will be quite helpful. Should there be any other way to incorporate master detail report printing in APEX kindly advise.
Thanks
Ahmed

Hi Ahmed_Jed,
Ahmed_Jed wrote:
Thanks Kiran for your prompt response. I tried following the steps already using this link (How To Create a Master-Detail PDF Report) somehow the detail record was not getting processed perhaps was trying to generate xml data using the above query. Any other reference will be highly appreciated.
Regards
Ahmed
    Well the problem lies here:
SELECT SYS_XMLAGG (
SYS_XMLGEN(
dept_row(
d.deptno, d.dname, d.loc,
CAST(MULTISET(SELECT e.empno, e.ename, e.job, e.mgr, e.hiredate, e.sal, e.comm
FROM emp e
WHERE e.deptno = d.deptno) AS emp_tab)
SYS.XMLGENFORMATtYPE.createFormat('DEPT')
) AS "XML_QUERY"
FROM dept d
WHERE d.deptno = 10;
    The Report Query itself generates XML data (in the required BI Publisher format). So, no need to generate it like this.
    As you are using table functions your query should be of the type:
SELECT EMPNO
            , ENAME
            , JOB
            , MGR
            , HIREDATE
            , SAL
            , COMM
    FROM TABLE ( EMP_PKG.GET_EMPLOYEES ( :PXX_DEPTNO ))
    where EMP_PKG.GET_EMPLOYEES is packaged table function which returns the Object Table of type EMP_TAB mentioned above.
    When you test the above Report Query with sample DEPTNO, it will generate the sample XML, which you can use to generate Report Layout in RTF format using BI Publisher Desktop.
    Hope this helps!
Regards,
Kiran

Master Detail Highlighting

Similar Messages

Maybe you are looking for