It would be great if the opportunity products be mapped as well, so that we could use them as constraints in opportunity related filters and triggers. This would required that the opportunity product and the product tables be mapped, so that we could select products by their name. The product name, product family, product code and product description should be usable, as well as any custom field.
Some specific operators would be needed such as "is only", in addition, to the "is", "is not", "contains", etc...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.