VOWizard-Bug: WHERE Clause not modified on EO add if manually changed befor

VOWizard-Bug: WHERE Clause is not modified on adding a EO (with association) if it was manually changed before
Testcase:
- Create a VO based on 2 EO (Association already defined) --> Jon in WHERE Clause automatically created by Wizard
- Then modify the WHERE clause, e.g. change an equal to outer join.
- All works fine.
- Then add a EO (also Association defined) and chose some attributes.
- Test and wonder why there are much more rows in the result than expected.
- Look into the Query-Tab and control the WHERE clause: Wizard forgot to add the new join... and therefore we get a cartesian product between the old view and the new added EO...
Possible solutions to fix the Bug:
1. add the JOIN ;-)
or
2. at least display a warning that the JOIN is not automatically created!
Regards, Markus
GE Medical Systems

Hi Markus-
Once the where clause has been customized, we don't update it in the interest of not messing up the user's custom code. However, we should probably warn the user in the types of cases you mention above that he will need to update the where clause manually to include the new information. We will add this in a future release.
Thanks,
Ray

Similar Messages

EQUAL condition on WHERE clause not working

Hi,
Can someone please tell me why the following WHERE clause (marked with ***** below) is not finding any EQUAL conditions?
I know that table i_cust_mast is populated with several thousand rows and that there ARE matching rows in KNVP.
Here is the code as I have it:
TYPES:
      BEGIN OF t_cust_mast,
        kunnr TYPE kunnr,
        name1 TYPE name1_gp,
        name2 TYPE name2_gp,
        stras TYPE stras_gp,
        adrnr TYPE adrnr,
        ort01 TYPE ort01_gp,
        regio TYPE regio,
        pstlz TYPE pstlz,
        vkbur TYPE vkbur,
        konda TYPE konda,
        sortl TYPE sortl,
        katr1 TYPE katr1,
        katr2 TYPE katr2,
        katr3 TYPE katr3,
        katr4 TYPE katr4,
        katr5 TYPE katr5,
        katr6 TYPE katr6,
        katr7 TYPE katr7,
        katr8 TYPE katr8,
        katr9 TYPE katr9,
        katr10 TYPE katr10,
        bzirk TYPE bzirk,
        vkgrp TYPE vkgrp,
        kdgrp TYPE kdgrp,
        klabc TYPE klabc,
        kondaa TYPE konda,
        kalks TYPE kalks,
        pltyp TYPE pltyp,
        hityp TYPE hityp_kh,
        hkunnr TYPE hkunnr_kh,
        datab TYPE datab,
        datbi TYPE datbi,
        lzone TYPE lzone,
      parvw TYPE parvw,
        kunn2 TYPE kunn2,
        kunn2a TYPE kunn2,
        kunn2b TYPE kunn2,
        kunn2c TYPE kunn2,
        kunn2d TYPE kunn2,
        kunn2e TYPE kunn2,
        kunn2f TYPE kunn2,
        kunn2g TYPE kunn2,
        parza TYPE parza,
        ktokd TYPE ktokd,
        loevm TYPE loevm_x,
      END OF t_cust_mast .
    TYPES:
      BEGIN OF t_part_func,
        kunnr TYPE kunnr,
        parvw type parvw,
        kunn2 TYPE kunn2,
        parza type parza,
      END OF t_part_func .
    TYPES:
      t_t_cust_mast TYPE STANDARD TABLE OF t_cust_mast,
      t_t_part_func TYPE STANDARD TABLE OF t_part_func.
    DATA: i_cust_mast TYPE t_t_cust_mast,
          i_part_func TYPE t_t_part_func.
CONSTANTS: c_type_a TYPE msgty VALUE 'A'.
FIELD-SYMBOLS: <x_cm> LIKE LINE OF i_cust_mast.
Get Customer Master Data
SELECT
   hkunnr hname1 hname2 hstras hadrnr hort01 h~regio
   hpstlz ivkbur ikonda hsortl hkatr1 hkatr2 h~katr3
   hkatr4 hkatr5 hkatr6 hkatr7 hkatr8 hkatr9 h~katr10
   ibzirk ivkgrp ikdgrp iklabc ikonda ikalks i~pltyp
   khityp khkunnr kdatab kdatbi h~lzone
   hktokd hloevm
INTO TABLE i_cust_mast " up to 50 rows
FROM kna1 AS h
JOIN knvv AS i ON ikunnr = hkunnr
JOIN knvh AS k ON hityp = c_type_a   " 'A'
                AND kkunnr = ikunnr
                AND kvkorg = ivkorg
                AND kvtweg = ivtweg
                AND kspart = ispart
                AND k~datab <= sy-datum
                AND k~datbi >= sy-datum.
IF sy-subrc = 0.
    SORT i_cust_mast[] BY kunnr.
ENDIF.
Get Partner Function Data for each Customer Master Record
LOOP AT i_cust_mast ASSIGNING <x_cm>.
    SELECT hkunnr hparvw hkunn2 hparza
      INTO TABLE i_part_func
    FROM knvp AS h
      WHERE h~kunnr = <x_cm>-kunnr.        ***** WHERE clause not finding any matches *****
ENDLOOP.
Thanks!!!
Andy

TYPES:
      BEGIN OF t_cust_mast,
        kunnr TYPE kunnr,
        name1 TYPE name1_gp,
        name2 TYPE name2_gp,
        stras TYPE stras_gp,
        adrnr TYPE adrnr,
        ort01 TYPE ort01_gp,
        regio TYPE regio,
        pstlz TYPE pstlz,
        vkbur TYPE vkbur,
        konda TYPE konda,
        sortl TYPE sortl,
        katr1 TYPE katr1,
        katr2 TYPE katr2,
        katr3 TYPE katr3,
        katr4 TYPE katr4,
        katr5 TYPE katr5,
        katr6 TYPE katr6,
        katr7 TYPE katr7,
        katr8 TYPE katr8,
        katr9 TYPE katr9,
        katr10 TYPE katr10,
        bzirk TYPE bzirk,
        vkgrp TYPE vkgrp,
        kdgrp TYPE kdgrp,
        klabc TYPE klabc,
        kondaa TYPE konda,
        kalks TYPE kalks,
        pltyp TYPE pltyp,
        hityp TYPE hityp_kh,
        hkunnr TYPE hkunnr_kh,
        datab TYPE datab,
        datbi TYPE datbi,
        lzone TYPE lzone,
      parvw TYPE parvw,
        kunn2 TYPE kunn2,
        kunn2a TYPE kunn2,
        kunn2b TYPE kunn2,
        kunn2c TYPE kunn2,
        kunn2d TYPE kunn2,
        kunn2e TYPE kunn2,
        kunn2f TYPE kunn2,
        kunn2g TYPE kunn2,
        parza TYPE parza,
        ktokd TYPE ktokd,
        loevm TYPE loevm_x,
      END OF t_cust_mast .
    TYPES:
      BEGIN OF t_part_func,
        kunnr TYPE kunnr,
        parvw type parvw,
        kunn2 TYPE kunn2,
        parza type parza,
      END OF t_part_func .
    TYPES:
      t_t_cust_mast TYPE STANDARD TABLE OF t_cust_mast,
      t_t_part_func TYPE STANDARD TABLE OF t_part_func.
    DATA: i_cust_mast TYPE t_t_cust_mast,
          i_part_func TYPE t_t_part_func.
CONSTANTS: c_type_a TYPE msgty VALUE 'A'.
FIELD-SYMBOLS: <x_cm> LIKE LINE OF i_cust_mast.
Get Customer Master Data
SELECT
   hkunnr hname1 hname2 hstras hadrnr hort01 h~regio
   hpstlz ivkbur ikonda hsortl hkatr1 hkatr2 h~katr3
   hkatr4 hkatr5 hkatr6 hkatr7 hkatr8 hkatr9 h~katr10
   ibzirk ivkgrp ikdgrp iklabc ikonda ikalks i~pltyp
   khityp khkunnr kdatab kdatbi h~lzone
   hktokd hloevm
INTO TABLE i_cust_mast " up to 50 rows
FROM kna1 AS h
JOIN knvv AS i ON ikunnr = hkunnr
JOIN knvh AS k ON hityp = c_type_a   " 'A'
                AND kkunnr = ikunnr
                AND kvkorg = ivkorg
                AND kvtweg = ivtweg
                AND kspart = ispart
                AND k~datab <= sy-datum
                AND k~datbi >= sy-datum.
IF sy-subrc = 0.
    SORT i_cust_mast[] BY kunnr.
ENDIF.
Get Partner Function Data for each Customer Master Record
LOOP AT i_cust_mast ASSIGNING <x_cm>.
    SELECT hkunnr hparvw hkunn2 hparza
      INTO TABLE i_part_func
    FROM knvp AS h
      WHERE h~kunnr = <x_cm>-kunnr.
ENDLOOP.

How to use "where" clause in modify statement

Hi
can any1 telll me is it possible to use a where clause in a modify statemetn. I want to use modify statemetn to insert a new recoed in a database table.
Regards
Sabahuddin Ahmed

MODIFY itab - itab_lines
Syntax :
... itab FROM wa TRANSPORTING comp1 comp2 ... WHERE log_exp.
With these additions the MODIFY statement assigns the content of the comp1 comp2 ... components of the wa work area specified after TRANSPORTING to all lines in the itab table that meet the logical condition log_exp. The wa work area must be compatible with the line type of the internal table.
The TRANSPORTING addition has the same effect as changing individual lines. The WHERE addition can only be specified together with the TRANSPORTING addition. After WHERE, any logical expression can be specified in which the first operand of each individual comparison is a component of the internal table. All logical expressions are therefore possible, with the exception of IS ASSIGNED, , and IS SUPPLIED. It is not possible to dynamically specify a component using bracketed character-type data objects.
While for standard tables and hashed tables all lines in the internal table are checked for the logical expression of the WHERE statement, for sorted tables, optimized access can be achieved by checking at least one opening part of the table key for parity using AND linked queries in the logical expression.
Example
Change the contents of the planetype component for all lines in the sflight_tab internal table in which this component contains the value p_plane1 to the value p_plane2.
PARAMETERS: p_carrid TYPE sflight-carrid,
            p_connid TYPE sflight-connid,
            p_plane1 TYPE sflight-planetype,
            p_plane2 TYPE sflight-planetype.
DATA sflight_tab TYPE SORTED TABLE OF sflight
                 WITH UNIQUE KEY carrid connid fldate.
DATA sflight_wa TYPE sflight.
SELECT *
       FROM sflight
       INTO TABLE sflight_tab
       WHERE carrid = p_carrid AND
             connid = p_connid.
sflight_wa-planetype = p_plane2.
MODIFY sflight_tab FROM sflight_wa
       TRANSPORTING planetype WHERE planetype = p_plane1.
reward if useful

Rtrim in where clause not returning correct data

A select statement specifying
where rtrim(field_name) <> ''
is not returning any rows even though there is data on the table with field_name not blank.
If this particular where clause is omitted the data is returned and rtrim(field_name) is populated correctly.
This is occurring across different tables and in both 10.2.0.4 and 11.2.0.1 databases. I can't find any references to this being a bug.
Has anyone else come across this ? Can anyone explain why this is happening please ?

An empty VARCHAR2 is considered NULL by Oracle.
sql> select 1 from dual where trim (' ') = '';
no rows selected
sql> select 1 from dual where trim (' ') != '';
no rows selected
sql> select 1 from dual where trim (' ') is null;
1
1

NVL in where clause not working with UNIX parameters

Apparently this in a where clause does not work in UNIX scripts...
.... and trans_date between to_date('&1','YYYY/MM/DD HH24:MI:SS')
and to_date(NVL('&2','31-DEC-4712'),'YYYY/MM/DD HH24:MI:SS')
and to_date(NVL('','31-DEC-4712'),'YYYY/MM/DD HH24:MI:SS')
ERROR at line 14:
ORA-01858: a non-numeric character was found where a numeric was expected
How do I get around a null in UNIX? This works fine if both parameters are populated. Thanks.

Jason ORCL wrote:
Apparently this in a where clause does not work in UNIX scripts...
.... and trans_date between to_date('&1','YYYY/MM/DD HH24:MI:SS')
and to_date(NVL('&2','31-DEC-4712'),'YYYY/MM/DD HH24:MI:SS')
and to_date(NVL('','31-DEC-4712'),'YYYY/MM/DD HH24:MI:SS')
ERROR at line 14:
ORA-01858: a non-numeric character was found where a numeric was expected
How do I get around a null in UNIX? This works fine if both parameters are populated. Thanks.it's nothing to do with unix at all - your date value doesn't match the format mask that you've entered:
'31-DEC-4712' doesn't map to 'YYYY/MM/DD HH24:MI:SS' in any universe unfortunately.

Queryeditor using fields more than once in where clause not possible?

I have to create a select query with a WHERE clause using a field multiple times.
I can't get this to work. For example:
SELECT ALL
EMSDTALIB.EMSPPA.PAIDNR,
EMSDTALIB.EMSPPA.PANAAM,
EMSDTALIB.EMSPPA.PAVLTR,
EMSDTALIB.EMSPPA.PATITL,
EMSDTALIB.EMSPPA.PAADRS,
EMSDTALIB.EMSPPA.PAHSNR,
EMSDTALIB.EMSPPA.PAHSNT,
EMSDTALIB.EMSPPA.PAPCA1
FROM EMSDTALIB.EMSPPA
WHERE EMSDTALIB.EMSPPA.PABEDR=1 AND EMSDTALIB.EMSPPA.PADTUD=0 AND
(EMSDTALIB.EMSPPA.PADVBD='001' OR EMSDTALIB.EMSPPA.PADVBD='003' OR EMSDTALIB.EMSPPA.PADVBD='006')How do I get this to work?
Regards,
Roland

Hi Roland, Luca, ICON_SS,
I just tried similar queries using the latest release bits and it works fine.
My Queries that worked fine are :
SELECT ALL DASUSR1.PERSON.PERSONID, DASUSR1.PERSON.NAME, DASUSR1.PERSON.JOBTITLE, DASUSR1.PERSON.FREQUENTFLYER
FROM DASUSR1.PERSON
WHERE ( DASUSR1.PERSON.NAME='Able, Tony' OR NAME='Black, John' )
SELECT ALL DASUSR1.PERSON.PERSONID, DASUSR1.PERSON.NAME, DASUSR1.PERSON.JOBTITLE, DASUSR1.PERSON.FREQUENTFLYER
FROM DASUSR1.PERSON
WHERE ( DASUSR1.PERSON.PERSONID=1 OR PERSONID=2 OR PERSONID=3)
I would suggest you to Download & Install latest Creator bits released 9/27/2004, if not already done.
Appreciate your valuable feedback,
Sakthi

Query, where clause not working.

Hi,
Query is:
select vbeln posnr matnr
from vbap
into table it_ivbap.
it_ivbap is internal table. i got records when i executed this query.
gave a where clause
select vbeln posnr matnr
from vbap
into table it_ivbap
where vbeln = '5049'.
it is not returning any records. i tried with all the possile values of vbeln
what I am doing wrong.
Thanks in advance.

Hello,
Change like this,
select vbeln posnr matnr
from vbap
into table it_ivbap
where vbeln = '0000005049'. " Check here
Regards,
vasanth

Two where clauses not working together

Good afternoon,
I have a query where I want to find out all unsorted stock (AA, BA, UP & BS) in certain depot's (Carbide dept, Harryworks and Adwick)
When I run these where clauses seperately they work but when I combine them they don't work where am I going wrong?
SELECT tblGRNItem.GRNPrefix + Convert(Varchar(10),tblGRNItem.GRN) AS GRNNumber, tblGRNItemStatus.ShortDescription, tblStorageLocation.Location, tblGRNItem.GRNItemNo, tblSupplier.SupplierName, tblGRNItem.MaterialDescription,tblGRNItem.NettWeight, tblGRNItem.LocalPrice, tblStaff.Initials, tblGRNItem.EstProductionHoursPerPO FROM tblGRNItem INNER JOIN tblGRNItemStatus ON tblGRNItem.GRNItemStatusID = tblGRNItemStatus.ItemStatusID INNER JOIN tblStorageLocation ON tblGRNItem.StorageLocationID = tblStorageLocation.LocationID INNER JOIN tblGRN ON tblGRNItem.GRNID = tblGRN.GRNID INNER JOIN tblSupplier ON tblGRN.SupplierID = tblSupplier.SupplierID INNER JOIN tblStaff ON tblGRNItem.SorterID = tblStaff.UserID
WHERE tblGRNItemStatus.ShortDescription LIKE 'UP' OR
tblGRNItemStatus.ShortDescription LIKE 'BA' OR
tblGRNItemStatus.ShortDescription LIKE 'AA' OR
tblGRNItemStatus.ShortDescription LIKE 'BS'

I don't understand the terminology you are using. Examples would help.
What do you mean by "works?" What does the query do that "doesn't work" and what does "works" mean? "Works" can mean anything from it includes too many rows or it excludes rows.
Give an example of running the where clause separately (and what is the result you get, either with actual results, representative results or describe the results); give an example of running with the where clauses combined (what is the result ...).
Russel Loski, MCT, MCSE Data Platform/Business Intelligence. Twitter: @sqlmovers; blog: www.sqlmovers.com

Use of CS operator in SELECT... WHERE clause not allowed

Hi all gurus,
quite a dumb question, but since I'm facing the issue... I need to access a standard DB table with some selection criteria , in particular I'd like to extract all the entries where the field NAME contains a specific substring.
Since the CS operator seems not to be supported as far as the compiler tells, what's the best (efficient/effective) way to perform such a task?
Thanks,
M.

Keshav.T wrote:
Range table
Thanks Keshav, I hoped there's an alternative way to do that without using range structures/tables... and also, to overcome the case sensitive problem.
I'd go for that if no alternative arise.

Programmatic setting of where clause not working.

Hi,
I am using Jdeveloper 11.1.2.2 .
I am trying query some rows from the VO by setting the VO in the programmatic way as given in this documentation : http://docs.oracle.com/cd/E15523_01/web.1111/b31974/bcquerying.htm#CHDEBEAF
But it is returning no rows. While I tried to query through the SQL Command Line it is querying the rows.
Is there any conditions that only bind variables declared in the VO can be queried in the programmatic way ? I tried that also. It is still not returning any rows.
Thanks,
Nigel.

in the line of fire wrote:
The best way to understand sql related issues is to enable debugger logs, where you can see actually what query is then executing. It really helps. Try it.I tried to run in the debugger mode, but there is no query execution seen. It is not throwing any errors, just its not returning the rows in the database.

Prompted value corrupts SQL WHERE clause - bug?

Using 10.1.3.4...
I implemented a simple pivot based request that navigates to a second request when the user drill down on one of the fields. This field is set to "value is prompted" in my second request. (I chose navigate method above drill (dimensions) for a few reasons not really important to this posting, mainly to do with format of requests at different levels)
All good and the drill down works well, parameters are passed correctly, except then I noticed that totals in my second request doesn't accurately tie back to my first request. After some research I found a very odd reason for this, my WHERE clause is getting corrupted - which almost looks like a bug in OBIEE and were wondering if anybody else has seen this behaviour from OBIEE and know a work around (before I try the Oracle support channels)
From Answers the request SQL is (I'll highlight the lines getting messed up):
SET VARIABLE DISABLE_CACHE_HIT = 1;
SELECT
BUSINESS_UNIT.Segment saw_0, BUSINESS_UNIT."Business Unit" saw_1, OPPORTUNITY.CLOSEPROBABILITY saw_2, OPPORTUNITY.CLOSEPROBABILITY saw_3, YEAR(OPPORTUNITY.ESTIMATEDCLOSE) saw_4, OPPORTUNITY_ADDON.TCV_IN_USD/1000000 saw_5, OPPORTUNITY_ADDON.WEIGHTED_TCV_IN_USD/1000000 saw_6, CASE OPPORTUNITY.CLOSEPROBABILITY WHEN 100 THEN OPPORTUNITY_ADDON.TCV_IN_USD/1000000 ELSE 0 END saw_7 FROM "Sales"
WHERE (OPPORTUNITY.STAGE NOT IN ('Lost', 'On Hold')) AND (YEAR(OPPORTUNITY.ESTIMATEDCLOSE) >= YEAR(CURRENT_DATE)) AND
((({color:#ff0000}OPPORTUNITY.CLOSEPROBABILITY > 25) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) <= 4)) OR ((OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4{color})))
ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6, saw_7
Which results in the following SQL request (from NQQuery.log)... The prompted value (BUSINESS_UNIT.Segment) is added correctly to the WHERE clause, but see how the remainder get's changed:
SQL Request:
SET VARIABLE QUERY_SRC_CD='Report',SAW_DASHBOARD='/shared/01 - Financials/_portal/4. Pipeline',SAW_DASHBOARD_PG='Pipeline',SAW_SRC_PATH='/shared/01 - Financials/4. Pipeline/Pipeline - Current - T2',DISABLE_CACHE_HIT = 1;
SELECT
BUSINESS_UNIT.Segment saw_0, BUSINESS_UNIT."Business Unit" saw_1, OPPORTUNITY.CLOSEPROBABILITY saw_2, OPPORTUNITY.CLOSEPROBABILITY saw_3, YEAR(OPPORTUNITY.ESTIMATEDCLOSE) saw_4, OPPORTUNITY_ADDON.TCV_IN_USD/1000000 saw_5, OPPORTUNITY_ADDON.WEIGHTED_TCV_IN_USD/1000000 saw_6, CASE OPPORTUNITY.CLOSEPROBABILITY WHEN 100 THEN OPPORTUNITY_ADDON.TCV_IN_USD/1000000 ELSE 0 END saw_7 FROM "Sales"
WHERE (BUSINESS_UNIT.Segment = 'Enterprise') AND (OPPORTUNITY.STAGE NOT IN ('Lost', 'On Hold')) AND (YEAR(OPPORTUNITY.ESTIMATEDCLOSE) >= YEAR(CURRENT_DATE)) AND
((({color:#ff0000}OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4)) OR ((OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4{color})))
ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6, saw_7
Which definitely explains why my totals do not add up when drilling down. Interestingly, if I run my second request without the prompt from Answers, the SQL request works like a charm:
SET VARIABLE QUERY_SRC_CD='Report',SAW_SRC_PATH='/shared/01 - Financials/4. Pipeline/Pipeline - Current - T2',DISABLE_CACHE_HIT = 1;
SELECT BUSINESS_UNIT.Segment saw_0, BUSINESS_UNIT."Business Unit" saw_1, OPPORTUNITY.CLOSEPROBABILITY saw_2, OPPORTUNITY.CLOSEPROBABILITY saw_3, YEAR(OPPORTUNITY.ESTIMATEDCLOSE) saw_4, OPPORTUNITY_ADDON.TCV_IN_USD/1000000 saw_5, OPPORTUNITY_ADDON.WEIGHTED_TCV_IN_USD/1000000 saw_6, CASE OPPORTUNITY.CLOSEPROBABILITY WHEN 100 THEN OPPORTUNITY_ADDON.TCV_IN_USD/1000000 ELSE 0 END saw_7 FROM "Sales"
WHERE (OPPORTUNITY.STAGE NOT IN ('Lost', 'On Hold')) AND (YEAR(OPPORTUNITY.ESTIMATEDCLOSE) >= YEAR(CURRENT_DATE)) AND
((({color:#ff0000}OPPORTUNITY.CLOSEPROBABILITY > 25) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) <= 4)) OR ((OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4{color})))
ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6, saw_7
Anybody had the same problem before?

Here's the excerpt (it's relative to crashing, but I think it should also address the bug):
# PRESENTATION SERVER CRASH AFTER UPGRADING TO 10.1.3.4 (Doc ID 756541.1)
crash when they run the reports containing Pivot Table. This has been a known issue with version ... subsequently upgraded to version
Doc Type:ALERTModified:2/10/2009

Dynamically changing the WHERE clause in detail VO in Master Detail

Hi, I want to develop a search functionality, results will be in a table, which will have an inline table displaying the details per row found.
I have a MD defined trough viewlink. I do change the master VO at runtime (set the entire SQL), based on the criteria entered by the user.
Is there a way to change the VO at the detail end of the link at runtime - that is what I haven't been able to do.
I have read that the ADF framework creates internal VO for each master row, whenever accessed trough accessor (which is not I am trying to do). I haven't been able to find a way to get a hold of the REAL VO at the detail end and have its WHERE clause changed.
Changes to the "VO instance in AM" (same one used as a definition in the detail end in the ViewLink def) does not seem to reflect the detail VO.
I have a MasterView, DetailView, MasterDetailLink (MasterView->DetailView).
MasterDetailLink is used to create a table with inline detail table. At runtime:
1.get MasterView (from AM), change query trough setQuesry() - works.
2.get DetailView (from AM), change query trough addWhereClause() - does not work (no exceptions) - the results I am getting DO NOT reflect the conditions of the where clause, I mean the clause have not been addedd.
I 've looked at the logs (debug enabled) and it seems to me that there no "activities" related to the detail VO, even after the where clause of the VO from step 2 is changed.
Looks like there is a separate VO which I would like to get a hold of :)
Thanks, and sorry for the long explanation

After you have added a new where clause on the detail VO, try re-executing VO's query by DetailVO.executeQuery()
If it doesn't work try re-executing the MasterVO's query after you have added the where clause on the detail

Where Clause in Table Lookups for Data Load

Hello,
In Shared Components I created in Data Load Table. In this Data Load Table I added a Table Lookup. On the page to edit the Table Lookup, there is a field called Where Clause. I tried to add a Where Clause to my Table Lookup in this field but it seems that it has no effect on the Data Load process.
Does someone know how to use this Where Clause field?
Thanks,
Seb

Hi,
I'm having the same problem with the where clause being ignored in the table lookup, is this a bug and if so is there a work around?
Thanks in advance

ADF dynamic where clause for VO query using BC

I'm hoping someone can help me out. I have a read only view object that I want to filter results based on some user choices. For example the user may want to see all results or they may only want to see a much smaller subset. This is for an error dashboard, the smaller subset maybe by application or maybe by application and by error severity. I think I can use a dynamic where clause but I'm not sure, Can someone get me started down the right path, or post an example that I can see.

Hi user,
You can use a dynamic where clause for this, but maybe there is a more practical option. Maybe you can have a fixed where clause, but using a bind parameter, like:
vo.application like :applicationParam. This makes an executeWithParams method available that you can call from your page, and use in the bindings. This parameter you can populate with the results of for example a poplist, with a default value of '%'.
When you do want to use a dynamic where clause, you will need to add a method to the java code of your application module, and make this method available for the client. In this method, you can use findViewObject to retrieve your VO, use VO.setWhereClause to set the whereclause to what you want, and then call VO.executeQuery. This method can then again be called from the page.
Success,
Jeroen van Veldhuizen

Missing Where Clause

Are there any specific known reasons why a WHERE clause would be removed from the Crystal SQL statement before being sent to the database?
I am aware that the results of some Crystal formulas in the RecordSelectionFormula will not resolve properly and therefore all secondary processing has to be done at the client.
I have also done some searching and found some range parameters causing problems.
Neither of the above cases are at play here. The report was fairly simply at one point, then the owner of the company asked for some "small changes" and now about 18 months and about 20 small changes later, and it is running slow (takes 4 to 5 minutes for 6-8 pages). I looked into it and found all 80,000 plus records are returned to show only 300 or so.
I went back to look at an old one from over a year ago and it passed the WHERE clause but there have been about 3 subreports, several calculation formulas and other formatting changes done since then. The last 5 or so versions have no WHERE clause. I have no idea when the slow down was introduced as the client never mentioned it until I asked about it. I ran it recently in full and thought it was taking a long time. Their computers are faster but I still think it is too slow and should be using a WHERE clause.
So is there some sort of checklist I can use to review to see if I can clean up the report and make it run faster?
CRXI R2 and Pervasive database
TIA, rasinc

Hi rasinc,
Since you can see a SQL Statement this means you are using ODBC or an OLE DB connection to Pervasive, the Native Btrieve driver does not show a SQL statement.
Not sure if this will work with an ODBC connection but worth a try.
Try adding this registry key:
HKEY_CURRENT_USER\Software\Business Objects\Suite 11.5\Crystal Reports\Database\QueryEngine - AllAtOnce_BackwardCompatible = 1
It's a string type.
Are you using CR XI R2 SP 4 FP 6?
None of those updates will/would be in that version Ludek mentioned.
Another thing is ODBC Connection will attempt to use it's own indexing, have a look at the key fields and try adding indexes to the DB so they can optimize the filtering.
And does checking on Perform Grouping on Server help.
The WHERE clause can be removed if the SQL being asked for cannot be converted into Pervasive SQL or the CR ODBC Driver is not capable.
You could turn on ODBC tracing and see what CR is passing, may help but likely the same as what you are seeing in the Designer. Compare the 2 between the old and new and see, may help determine what cause CR to remove the filter.
May even be ODBC driver issue with Pervasive. They may have suggestions also.
Don

VOWizard-Bug: WHERE Clause not modified on EO add if manually changed befor

Similar Messages

Maybe you are looking for