Hi,
We've experiencing something strange concerning the 'existing product' lookup in Opportunities and Quotes.
Opening the lookup in Opportunities took more then a minute while in Quotes it only takes a second.
We can't change the view of this field and they are both linked to the same view 'Product Lookup View'.
So you would expect the same query, but it ain't.
This is what the profiler has shown us ...
The Quote Products page does use the view definition as stated in the product entity.
The Opportunity Products page does a select of all columns and doesn't apply the filter of businessunit, instead using a pricelevel filter.
QuoteProducts :
select
top 251 "product0".Name as "name"
, "product0".ProductId as "productid"
, "product0".qten_ERPid as "qten_erpid"
, "product0".ProductTypeCode as "producttypecode"
, "product0".qten_InternationalproductId as "qten_internationalproductid"
, "product0".qten_BUId as "qten_buid"
, "product0".qten_InternationalproductIdName as "qten_internationalproductidname"
, "product0".qten_BUIdName as "qten_buidname"
, "a_2058f5d59010e211990d0050568b6c4a".qten_CataloguePage as "a_2058f5d59010e211990d0050568b6c4a.qten_cataloguepage"
from
Product as "product0" (NOLOCK) left outer join qten_internationalproduct as "a_2058f5d59010e211990d0050568b6c4a" (NOLOCK) on ("product0".qten_InternationalproductId = "a_2058f5d59010e211990d0050568b6c4a".qten_internationalproductId)
where
(("product0".StateCode = @StateCode0 and "product0".qten_BUId = @qten_BUId0)) order by
"product0".Name asc
, "product0".ProductId asc
OpportunityProducts :
select
DISTINCT top 251 "product0".qten_PDFLinkGR as "qten_pdflinkgr"
, "product0".VendorName as "vendorname"
, "product0".StatusCode as "statuscode"
... All columns all listed here
, "product0".qten_GrossPriceUnitIdName as "qten_grosspriceunitidname"
, "product0".SubjectIdName as "subjectidname"
from
Product as "product0" (NOLOCK) join ProductPriceLevel as "productpricelevel1" (NOLOCK) on ("product0".ProductId = "productpricelevel1".ProductId and (("productpricelevel1".PriceLevelId
= @PriceLevelId0))) order by
"product0".ProductId asc
It this a known issue and how can we correct this?
Regards,
Sven Peeters