on 02-09-2017 10:56 PM
Hi Gina Cowart,
The standard data source "Opportunity Header and Item" itself is a combined data source. So, this is expected behavior. However, you can try creating your own custom join data source by using Opportunity Header and Opportunity Item data sources as join members. You can try creating a report on it as per your requirement. This does not use the union concept of combined data source. Hence the extra line will be eliminated.
You can refer to this case document while creating "2366796 - Best Practices for Modelling Data Sources and Reports - Performance".
Regards,
Trivedhi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please refer to the section Combined Data Sources to understand more better as in why is this shown as #
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Prasanth,
Still this is not a proper way for the representation of Opportunity Pipeline by Product .
How we can give our customers a proper report showing the Pipeline break down by their Products? Something like the report Sales by Product Category (Top 10) - Current Year but with Sales By Products instead of Product Categories!
KR,
A.
If there are opportunities with different currencies, you may see this issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.