PanelCollection - Query By example Label Change

Hi,
We have panel collection in our screen with the properties of defaultToolbarItemDisplay="iconAndText",
but its showing the Query By Example icon only, not showing the label.
Our requirement is We have to show the label as Search after the QBE icon.
We are using Jdeveloper 11.1.1.4.0
Please give me the suggestion..
Best Regards,
Vijay

Hi,
did not have a chance to reproduce, but I would suggest testing with 11.1.1.5 and if it is the same problem there, file a bug with customer support
Frank

Similar Messages

How can i change the default text "Query by Example"

Studio Edition Version 11.1.1.3.0
how can i change the default text *"Query by Example"* in a Panel Collection
Thx

Hi thieto,
The label you are looking for is af_panelCollection.LABEL_MENUITEM_QBE*
I'm currently writing a blogpost on this issue. In short, you will have to create a skin resource bundle.
In the skin definition, refer to this bundle class.
<?xml version="1.0" encoding="ISO-8859-1"?>
<skins xmlns="http://myfaces.apache.org/trinidad/skin">
<skin>
    <id>mySkin.desktop</id>
    <family>MySkin</family>
    <extends>blafplus-rich.desktop</extends>
    <render-kit-id>org.apache.myfaces.trinidad.desktop</render-kit-id>
    <style-sheet-name>skins/MySkin.css</style-sheet-name>
    <bundle-name>com.blogspot.lucbors.view.bundles.MySkinBundle </bundle-name>
</skin>
</skins>In this class, adjust the label text to your needs.
package com.blogspot.lucbors.view.bundles;
import java.util.ListResourceBundle;
public class MySkinBundle extends ListResourceBundle {
public MySkinBundle() {
    super();
@Override
public Object[][] getContents() {
    return _CONTENTS;
static private final Object[][] _CONTENTS = {
     {"af_panelCollection.LABEL_MENUITEM_QBE","the text that you want"}
}More in the blogpost
Good luck
Luc Bors
Edited by: lucbors on Jul 26, 2010 11:39 AM (blogpost finished - URL added)

Query By Example search in Uppercase (value only)

Hi,
I am using Jdev 11.1.1.6.
I need to allow users to use QBE on table (wrapped by PanelCollection) using case-insensitive search.
My application stores everything in uppercase, so there is no need to put UPPER on database column. So I am looking for solution to only uppercase value entered by user.
I found one old post by Steve Muench here[http://radio-weblogs.com/0118231/2004/04/16.html#a276]
private void adjustStringViewCriteriaToUppercaseWildcards() {
    ViewCriteria vc = getViewCriteria();
    if (vc != null) {
      ViewCriteriaRow vcr = (ViewCriteriaRow)vc.first();
      AttributeDef[] attrs = vc.getViewObject().getAttributeDefs();
      int attrCount = attrs.length;
      while (vcr != null) {
        for (int z = 0; z < attrCount; z++) {
          if (attrs[z].getSQLType() == Types.VARCHAR ) {
            String criteria = (String)vcr.getAttribute(z);
            if (criteria != null) {
              vcr.setAttribute(z,criteria.toUpperCase()+"%");
        vcr = (ViewCriteriaRow)vc.next();
}Steve suggested to put this method in custom ViewObjectImpl and called from getViewCriteriaClause(), something like this:
public String getViewCriteriaClause() {
    adjustEnameViewCriteriaToUppercaseWildcards();
    return super.getViewCriteriaClause();
}I noticed that getViewCriteriaClause() has been deprecated in 11gR1, so I instead implemented it in getViewCriteriaClause(boolean b).
The problem is that first statement ViewCriteria vc = getViewCriteria(); returns null. My view object does not have any View Criteria. I was expecting the temp VC that is attached by framework during QBE.
I modified the code to this:
        ViewCriteria[] vcs = getApplyViewCriterias(ViewCriteria.CRITERIA_MODE_QUERY | ViewCriteria.CRITERIA_MODE_CACHE);
        if (vcs != null && vcs.length > 0) {
            for (ViewCriteria vc : vcs) {
                if (vc != null) {
                    ViewCriteriaRow vcr = (ViewCriteriaRow)vc.first();
                    AttributeDef[] attrs =
                        vc.getViewObject().getAttributeDefs();
                    int attrCount = attrs.length;
                    while (vcr != null) {
                        for (int z = 0; z < attrCount; z++) {
                            if (attrs[z].getSQLType() == Types.VARCHAR) {
                                String criteria = (String)vcr.getAttribute(z);
                                if (criteria != null) {
                                    vcr.setAttribute(z,
                                                     criteria.toUpperCase());
                        vcr = (ViewCriteriaRow)vc.next();
        }Now I see that, it is getting the VC and executing vcr.setAttribute(z,criteria.toUpperCase()); on the value that I entered during search but still matched rows are not retrieved.
When I explicitly put the value in Uppercase on UI then it returns the correct rows.
What am I doing wrong here? What else do I need to handle here? Is there another way to achieve my usecase?
Note: If I do vc.setUpperColumns(true) then it returns all rows matching search criteria but the statement is executed with UPPER on both sides of where clause, which is desired behavior but something I don't want as it will not use any index on that column.
Thanks,
Jai

Thanks for the info Timo.
I did not mention it explicitly but I need this for entire application. I don't need this for my declared bind variables, which are already taking care, but for QBE provided by PanelCollection component where framework attaches temp bind variables. So I don't know the bind variable name to set their values.
Do you know how to achieve using the method you mentioned in your post?
Update on Steve's method:
When I tried to test it using BC Tester (as the post suggests for testing), it worked. Here is what the post says:
To test out your work, you can use the Business Components Tester tool that's built-into JDeveloper (right-mouse Test... on your application module in the navigator).
When viewing your view object, their is a "Specify View Criteria" toolbar button that allows you to enter one or more rows of View Criteria query-by-example criteria.It does not work when I invoke QBE from UI using PanelCollection filter component. At that time, first statement [i.e. ViewCriteria vc = getViewCriteria();], in the helper method returns NULL.
I thought the solution is meant for BC Tester as well as UI but since the post is very old [2004], I am not sure if something has changed on the framework side, which is breaking the logic for UI.
Question: What is causing this not to work from UI? How can I tweak this method to make it work from UI?
Any help is appreciated here.
Thanks,
Jai

Query by example - how can I display VCRow in JTable?

I would like to provide the user with a searchable table.
Actually I would like to use two tables: one, displaying one row where the user can specify the search criteria. And the second table should display the data found.
I could store the entered criteria locally in a hashmap in TableModel, for example, then create a WHERE clause. This solution is quite messy, since the user can add, remove and rearrange the columns of both tables.
Or I could use -I hope- the query-by-example feature, like this:
am = app.getApplicationModule();
ViewObject vo = am.createViewObject( "MyVO", "mypackage1.PatView" );
ViewCriteria vc = vo.createViewCriteria();
ViewCriteriaRow vcr = vc.createViewCriteriaRow();
Now I can set attributes and use vo.applyViewCriteria() to find my data.
But how can I bring the first JTable to display this single ViewCriteriaRow, so that the user can do the editing?
The JUNavigationBar does it, if I am not mistaken. It switches the PanelBinding to find mode, and then a JTable displays a ViewCriteriaRow (?) instead of the ViewObject's data. But I don't want to use the bar. How do I create this behaviour manually?
The javadoc of JUPanelBinding says:
"Sets this panel and all its associated iterators into find mode."
So I guess that setting iterators into find mode is what I need. But I cannot figure out how to do that. Who can?

You cannot set the iterators in a panelBinding to separate find/data modes individually.
However you can create two JUPanelBinding objects one for the findMode form and one that displays Data.
here's what I did to modify a generated SingleForm, to display two panels of the same type one in find mode and other in data mode.
I changed the jbInit method of the "LayoutPanel" class to be like:
//declare this as a member of the class.
JButton findBtn;
public void jbInit() throws Exception
// Panel layout
masterViewPanel = new PanelDeptView(panelBinding);
//create another instance of PanelBinding for a second (findform) DeptView panel.
JUPanelBinding binding = new JUPanelBinding("Project3.Mypackage1Module", this);
binding.setApplication(panelBinding.getApplication());
masterViewPanel1 = new PanelDeptView(binding); //create second instance
findBtn = masterViewPanel1.navBar.getButton(JUNavigationBar.BUTTON_FIND);
findBtn.doClick(); //set the second instance in find mode.
//add a listener on the second instance's execute button so that it resets the form into find mode
//this forces the second instance to be in find mode when execute button is pressed.
masterViewPanel1.navBar.getButton(JUNavigationBar.BUTTON_EXECUTE).addActionListener(new ActionListener()
public void actionPerformed(ActionEvent ev)
SwingUtilities.invokeLater(new Runnable() {
public void run()
findBtn.doClick();
this.setLayout(panelLayout);
add(masterViewPanel, BorderLayout.WEST);
//add the second instance.
add(masterViewPanel1, BorderLayout.EAST);
I also had to call findBtn.doClick() again in the "constructor" that takes (JUApplication, boolean) after the panelBinding is executed,
to force the initial startup of this panel in findmode

JClient query by example doesn't work in 10.1.2.

I've a JClient application I migrated from 9.0.4 to 10.1.2.
In the migrated app query by example doesn't work anymore in JTables.
Could someone help ?
Tks
Tullio

Frank, I got a testcase from Tullio. It's a 9.0.4 project uding JClient that is pre-ADF bindings.
I migrated his 9.0.4 project to 9.0.5.2 first.
In 9.0.5.2, I see already a change in behavior related to enter-query mode in the JTable, but the number of rows displayed looks correct.
Tullio, can you confirm if the problem you are seeing vis a vis enter query mode is that if you:
1. Click enter-query button
2. Click into a field like Ename and type SMITH but don't [Tab] out of that field yet
3. Click on the execute-query button
It behaves as if you've entered no criteria there.
If at step 2 above you clicked [Tab] to exit the field where you typed SMITH, then it works correctly.
Is this the enter-query-JTable-related problem you're seeing (that is, related to when you don't focus-out of the field?)
The "number-of-rows-displayed" issue you mention in this other thread (10.1.2 JClient binding Error. does reproduce with your testcase only in 10.1.2 (as well as also still having this 9.0.5.2 focus-related issue in enter query mode).

Explorer InfoSpaces on HANA Views - column label changes cause issues?

Key question is – do simply label changes in HANA view cause issues with Explorer InfoSpaces? Furthermore, on source view changes, does the InfoSpace also need to be adjusted?
What we have observed is this
1. InfoSpaces have been created using the “SAP HANA appliance” connection highlighted below. The corresponding “Home” screen is shown below that, so there are around 14 or so InfoSpaces that should be available.
2. Yesterday, there was a production deployment that contained some changes to the underlying views in the form of label changes (not column name changes).
3. Now, in the “Manage” screen we cannot see these same 14 InfoSpaces available under the expected connection. Instead, they are all available under the “Source Unavailable” node with the default action of “Change Source” shown.
Additionally, we are seeing some strange behavior where certain facets are actually containing the wrong data. For example, in a facet/column called “Source Type”, where the expected values are “NBP or PBP”, we are seeing Material numbers like “00001112453”. This leads me to believe that there is a mapping issue under the covers.
Thanks,
Justin

Our BOE Explorer is Version: 14.1.1 Build: 1072 - I’m not sure how this corresponds with your 69.01 to 74 numbers (release note numbers?).
But it sounds identical to your description.
One of our observations: if we change the sorting on a facet pane using the upper right sort control the values are corrected for a while, at least until we change a measure and the set of facets get updated with the miss-mapped values again. This only occurs on some models and we haven’t been able to determine what the underlying criteria might be that aggravates the problem.
Thanks for your input – it helps us determine a viable path forward.
Cheers,
Tony

BC4J Query by example for dates uses wrong date format

When querying by example on date fields, I get the following nested exceptions:
oracle.jbo.SQLStmtException: JBO-27121: SQL error during statement execution.
JBO-26044: Error while getting estimated row count for view object
and
java.sql.SQLException: ORA-01830: date format picture ends before converting entire input string.
It would seem to be caused by the following clause added to the end of the entity object's query:
"QRSLT WHERE ( ( (DATE_FIELD = TO_DATE('23/12/2003', 'yyyy-mm-dd')) ) )"
which causes problems as our entity objects use a 'dd/MM/yyyy' date format.
Is there a way we can make the query by example use the same date format as the rest of our app?

Im not an expert on this but I see nobody is replying so this might help you. I've been having problems with dates as well and Im pretty sure that the attached formatter isn't used in find mode. That is because the java date class (can't remember which one) used by the BC4J has the format yyyy-mm-dd. I don't now if it is possible to change it but I got around the problem by writing my own domain. You can take a look at Toystore demo, by Steve Muench, that uses a custom date domain, ExpirationDate (see the code below). It is mapped to a VARCHAR column in the database but it is possible to map it to a DATE column.
I have been watching the postings with questions about dates and I have noticed that a lot of people have problems with this but I havent seen an answer yet.
package toystore.model.datatypes.common;
import java.io.Serializable;
import java.text.SimpleDateFormat;
import java.util.Calendar;
import java.util.Date;
import oracle.jbo.Transaction;
import oracle.jbo.domain.DataCreationException;
import oracle.jbo.domain.DomainInterface;
import oracle.jbo.domain.DomainOwnerInterface;
// --- File generated by Oracle Business Components for Java.
* This custom datatype implements an immutable domain class that
* maps to a VARCHAR column containing values like '10/2004' representing
* expiration dates of credit cards. We could have chosen to implement
* this as a domain that stores itself in a DATE column instead of a
* VARCHAR column, but since the Java Pet Store demo schema stored the
* information in a VARCHAR column, we decided to illustrate how to
* accommodate that case using domains.
public class ExpirationDate implements DomainInterface, Serializable {
private Date mDate;
private String mDateAsString;
protected ExpirationDate() {
mDate = new Date();
convertDateToStringFormat();
* Return the value of the expiration date as a java.util.Date
public Date getDateValue() {
return mDate;
* Allow expiration date to be constructed from two
* strings representing month and year
public ExpirationDate(String monthVal, String yearVal) {
this(monthVal+'/'+yearVal);
public ExpirationDate(String val) {
validate(val);
convertDateToStringFormat();
* The getData() method must return the type of object that JDBC will
* see for storage in the database. Since we want this ExpirationDate
* datatype to map to a VARCHAR column in the database, we return the
* string format of the date
public Object getData() {
return mDateAsString;
* <b>Internal:</b> <em>Applications should not use this method.</em>
public void setContext(DomainOwnerInterface owner, Transaction trans, Object obj) {
* Performs basic validation on strings that represent expiration dates
* in the format of MM/YYYY. Note that in the process of testing whether
* the string represents a valid month and year, we end up setting
* the private member variable mDate with the date value, so if the
* validate() method does not throw an exception, the mDate will be setup.
protected void validate(String val) {
if (val != null) {
if (val.length() != 7 ||
val.charAt(2) != '/' ||
!isAllDigitsExceptSlashAtPositionTwo(val) ||
!isValidMonthAndYear(val)) {
throw new DataCreationException(ErrorMessages.class,
ErrorMessages.INVALID_EXPRDATE,
null,null);
* Returns true if all digits except position 2 (zero-based) are digits
private boolean isAllDigitsExceptSlashAtPositionTwo(String val) {
for (int z=0, max = val.length(); z < max; z++) {
if (z != 2 && !Character.isDigit(val.charAt(z))) {
return false;
return true;
* Returns true if the val string, assumed to be in "MM/YYYY" format
* is a valid month and year value, setting the mDate member variable
* if they are valid.
private boolean isValidMonthAndYear(String val) {
try {
int month = Integer.parseInt(val.substring(0,2));
int year = Integer.parseInt(val.substring(3));
Calendar c = Calendar.getInstance();
c.setLenient(false);
c.set(year,month-1,1); // Month is zero-based !
mDate = c.getTime();
catch (IllegalArgumentException i) {
return false;
return true;
public String toString() {
return mDateAsString;
* Convert mDate to String format
private void convertDateToStringFormat() {
if (mDate != null) {
SimpleDateFormat sdf = new SimpleDateFormat("MM/yyyy");
mDateAsString = sdf.format(mDate);
* Return true if the expiration date is in the future
public boolean isFutureDate() {
return mDate.compareTo(new Date())> 0;
* Compare the Expiration Dates by comparing their respective
* getData() values
public boolean equals(Object obj) {
if (obj instanceof DomainInterface) {
Object thisData = getData();
if (thisData != null) {
return thisData.equals(((DomainInterface)obj).getData());
return ((DomainInterface)obj).getData() == null;
return false;

Query By Example and security issues

HI,
I have started looking at security issues in our ADF application.
Is the default implementation of Query By Example (QBE) on a table safe from Cross Site Scripting and SQL Injection?
In other words, can a user enter some value in a QBE input field that can either:
- execute a malicious script (CSS)
Or
- somehow change the underlying will change the SQL query
I am more worried about SQL Injection as QBE takes input from a web user, and makes a corresponding SQL query to the database.
Are there any ways to prevent any of these?
Thanks

Timo thanks for your answer.
So far I am confident on the following (based on responses and other reading):
1) default implementation of Query By Example (QBE) (e.g. search fields) is "safe /safer" from/on SQL injection issues.
2) User entered data via non QBE fields (I assume this is "For other input text you" Timo mentions) should by checked against special characters (> < etc) to "prevent " cross side scripting.
However, should I do 2) for QBE filters on alphanumeric columns (default implementation) ? I can do it, but if I do it I would loose some searching functionality
as >, < are valid wildcard characters.
Thanks

Query By Example and LOV

Hi all,
I need to do query by example and let the user choose from the LOV before executing the query. I want the user to click on the button that will make the form enter the query mode and then lauch the LOV automatically. I tried to make LOV automatic display on but it would result the LOV to be display again after I execute the query.
Thanks in advance for your help.

Write a trigger that openes the LOV using show_lov builtin.
Then use the value that is returned in a set_block_property('block',DEFAULT_WHERE...)
builtin. and then issue an execute_query.
you then don't need to go into enter query mode.
(If you return the LOV value to a field you might want to clear the block before you execute query or you'll get asked to save your changes.

How to build "Query by example" Report?

I want to create a report which allows user to select which columns to return.
It is similar to "Query by example" form. Have someone done that before and share me the PL/SQL how to do that?
Thanks in advance.

I got the answer, u need to set table.setFilterModel("") and refresh panel collection which contains this table
whenever u need to make "Query By Example" button of panel collection invisible.

Multi Lingual Form Label Change

Hello All,
We have single oracle application custom form fmb which supports several languages, now i got a label change for spanish language so how can i change the label for spanish. While checking only one fmb they are maintaining for several languages and while opening the fmb its always opening in english. help on this is highly appreciated.
Thanks,
Devaraj.K

Pl post details of OS, database and EBS versions.
You need to create a separate fmb file for each language using the seeded TEMPLATE.fmb file for each language. If you want to use only one fmb file for all languages, then all your boilerplate objects will have to be in one language (typically English)
http://docs.oracle.com/cd/E18727_01/doc.121/e12897/T302934T458261.htm
HTH
Srini

Newbie question on text label change according to program

I managed to get the property of the gauge scale (range) changes according to the different measurements selected.BUT the thing is I could not get the text label change and display as differrent measurements is selected. Pls advise

Thanks Kim"
I managed to do it. Yes,the name label cannot be changed but the caption text is possible when selected.
I did it by right-clicking the property node in the REAR(block) diagram. I click on the property and set the caption text. It works now.
Include here a .jpeg file for other newbies!
Attachments:
pic1.jpg ‏51 KB

Clearing VO dynamic Query-By-Example ViewCriteria

Looking for some help with JDev 11.1.1.4.0, ADF BC + ADF Faces RC please.
At it's simplest we're looking how to clear the query-by-example (QBE) filters on a VO without using the table UI component and not accidentally clearing other view criteria on the VO. To explain our use case first let me define the characteristics of our app. We have:
a) A BTF based on fragments:
a.1) The transaction/data control scope = Use Existing Transaction if Possible/Shared
a.2) It contains a single fragment
a.3) The fragment contains a table based on an ADF BC View Object (VO)
a.4) The VO has a view criteria defined at design time, implemented via the Application Module (AM)
a.5) The table allows the user to filter the data
a.6) The BTF does not include any task flow returns or parent actions
b) A consuming BTF based on pages:
b.1) The transaction/data control scope = Always Begin New Transaction/Isolated
b.2) It contains 2 pages with navigation rules to move between them (back/forward)
b.3) The fragment from "a" is included on both pages in "b"
b.4) When navigation occurs between the pages, it is invoked via buttons in this BTF, not the original BTF via parent actions or task flow returns. This aligns with point a.6. As such when navigations occurs between the 2 pages, the region/task flow binding instance of "a" in the region of the current page of "b" is prematurely terminated. The implication is the instance of "a" doesn't get a chance to do any processing before it is closed.
Note that "a" and "b" are built in isolation of each other. "b" has no inherit knowledge about the components of "a" nor the ADF BC components. The implication is "b" cannot attempt to grab the table UI component, nor manipulate the ADF BC components as it doesn't know anything about the BTFs dropped on its pages.
If the user opens the 1st page in "b" and enters a query-by-example criteria on the table from the region containing the 1st of instance of "a", then the user navigates to the 2nd page, the filter criteria are still set on the 2nd instance of "a". This is expected behaviour as "a" has data control scope = shared implying when the QBE criteria are set on page 1, they are written down to the VO, which when the user navigates to page 2, as it is sharing the same VO the QBE criteria are there to reuse/share on page 2.
In our scenario what we want to do:
1) Is in navigating between the 2 pages, we wish the query-by-example filter criteria to be cleared/reset, such that navigating between pages the filter criteria are empty/fresh
2) However in navigating between the pages we must not lose the design time view criteria (and it's bind variable value) that has already been applied
3) Maintain shared data control scope so we minimize the amount of database connections
The common solution to clearing the QBE filter is as per Timo Hahn's following blog entry: http://tompeez.wordpress.com/2011/10/29/jdev-how-to-reset-a-filter-on-an-aftable/
Yet that solution assumes the code has access to the table UI component. As we need the QBE criteria reset on navigation caused by "b", and such navigation causes a premature termination of "a" there's no chance for "a" to grab the table component and clear the filter criteria before "b" navigates away. The logical solution to this is on entering "a" again, to programatically reset the QBE criteria as part of the initial steps in the "a" BTF. But on entering "a" using Timo's solution, the method call doesn't have access to table UI component as the fragment isn't yet rendered, making this solution not viable.
Another solution we've tried is calling applyViewCriteria(null) then reapplying our view criteria from a VO client interface method, but it appears we aren't clearing the QBE criteria. This worries me a bit because it looks like you can't discern the QBE view criteria from the normal view criteria unless you go through the table UI component methods.
So how do we clear the QBE filter criteria programatically, without clearing (or at least restoring) the design time view criteria, and without relying on the table UI component to clear the QBE criteria?
Phew, I hope that makes sense? Thanks for your help in advance.
CM.
PS. There is an assumption in the title of my post that table Query By Example criteria are stored as ADF BC View Object view criteria. Possibly it's a separate mechanism so please be careful this doesn't lead you astray in answering my post.

Chris,
I don't have time to follow this through right now, but I'm on to something.
I was able to affect the filter via the binding container (at least it's not the UI). See this code:
public void a(ActionEvent e)
   String s = "#{bindings.EmployeesView1Query.queryDescriptor}";
   Object o = JSFUtils.resolveExpression(s);
   FilterableQueryDescriptor f = (FilterableQueryDescriptor) o;
   f.removeCriterion(f.getCurrentCriterion());
}Now, it doesn't do exactly what you want (it actually somehow makes no rows show up in the table), but I believe it's moving in the right direction.
Am leaving for the office (5:40 am), so I'll pass this over to you to have a gander.
John

When using BW Bex query analyzer users cannot change reporting queries ....

Issue: When using BW Bex query analyzer users cannot change reporting queries. Any attempt to change queries results in errors.
Error: BEx Query Designer: Run-time error '-2147221499 (80040005) Fatal Error - Terminating
Impact: Business reporting is currently being negatively impacted because users cannot modify queries, cannot change filters for fiscal period and fiscal year.
OS / MS Office Suite being used: Vista & Office 2007
Backend System: BW 2.0B
Frontend System: Being a large organization, we have a controlled environment wherein all users will have the following applications installed by default:
1. SAP Client Base 7.10
2. SAP BW 3.5 Patch 4
3. SAP BI 7.10 Patch 900
4. SAP GUI 7.10 Patch 12
Does anyone has any idea as to why we are getting this error? Is it a Vista issue? Is it a front-end issue?

Just a thought - did you guys apply any Microsoft security patches before this started happening - we had a similar issue in other SAP application due to MS security update. Raise an OSS with SAP

Examples of "change of address"

has any one seen some good examples of "change of address" cards or flyers?
its for a job for a local telephone franchise.
any tips greatfully accepted. Im thinking that a map is a good idea.

alex_p_howard wrote:
something to impress the client, something catchier than "we have mooved"
I would hope so.

PanelCollection - Query By example Label Change

Similar Messages

Maybe you are looking for