Lookup view for existing products does not use parent Price List view in CRM 2011

Proposed Lookup view for existing products does not use parent Price List view in CRM 2011

  • 2012年3月26日 13:04
     
     

    Normally if you choose products in opportunity, quote or order you get the look up webpage in the entry form with the products related to the pricelist of the owning-entity

    I now noticed that for a reason i don't know this doesn't work for opportunity and order, but still works for quote.

    In the lookup for quote the view mentions "Products in Parent Price List"

    In the lookup for order and opportunity i get the view: "Product Lookup View"

    In the respective forms I have the same configuration for the "existing Product" field.

    In the field properties of the form I can not chose any list. It is greyed out and Fix on "Product Lookup View" and View selector Off

    What can be the reason for this behavior and how can I change this ?

すべての返信

  • 2012年3月26日 20:56
    回答者:
     
     回答の候補

    Hi,

    I came across this issue about 9 months ago (see this forum post). I am still unsure of the exact cause, but the fix is to create an unmanaged solution in a vanilla organisatoin, in your case add the order product and opportunity product then export the solution and import into your organisation that has the issue.

    I hope that helps,

    Rob


    Microsoft Certified Technology Specialist (CRM) GAP Consulting Ltd Microsoft Community Contributor Award 2011

  • 2012年5月14日 12:40
     
     

    Hi,

    I detect this issue last week. In my scenario I registered a JavaScript function on the on-change event of the existing product lookup in the quote product form. After this the selected view is the "Product Lookup View". Then I remove the JavaScript’s and publish the solution again and the view stills the "Product Lookup View". To roll back the CRM to his normal behavior (having the "Products in Parent Price List" selected) I had to apply your workaround. So when you register code on the onchange of this "special" lookups CRM loses his normal behavior. Do you think that you scenario can be similar to this one?

    Regards,

    João Zorro