Originally Posted by jpol
|
|
I saw that report... I guess I am trying to understand how the actual "Line Item Details" report is brought together. I would like to impliment it's funcationality into a custom report I already have done and running. For instance, today, I put in a part with a rack shelf. It just so happened that the next part in line was the line item for actual rack shelves. Then I'm asked what's up... it's hard to explain to clients why 5 are being priced, and one isn't. On top of that, clients who shop our prices, see $1028 for a TV that costs $899 and ask why I charge so much, not seeing the "*" and putting 2 and 2 together. I can get the information to go away and not be displayed, I just can't get the custom report to break out the accessory and make it a line item by itself or include it in a quantity already existing.
|
Disclaimer: I tend to be overly explicit, please don't confuse it with being condescending. Thanks.
There are a bunch of colliding concepts here. Right now, effectively two things can be added to a project (Packages and Equipment).
A piece of Equipment is a physical Item.
A package is conceptual item.
Here's a quick reference project:
Package 1 (conceptual item)
Pkg Equipment Item 1 (physical item)
Pkg Equipment Item 2 (physical item)
Equipment Item 1 (physical item)
Accessory Equipment Item (physical item)
When a proposal runs, there are two items in the proposal:
- Package 1 (Price = sum of price of items in package * discount)
- Equipment Item 1 (sum of price of equipment item + price of accessory items
When the Line Item detail runs, there are 4 items:
- Pkg Equipment Item 1 (Price = its price * discount of the package it exists in)
- Pkg Equipment Item 2 (Price = its price * discount of the package it exists in)
- Equipment Item 1 (Price of the Equipment item)
- Accessory Equipment Item (Price of the Accessory item)
When the Line item report runs and you group the data (Location, Zone, whatever), the items fall where they fall.
So, if you extend the example out a bit and get a little more concrete:
package 1 (discount 10%):
Pkg Item 1: Manufactuer: Sony, Model: 123, Price: $100
PkgItem 2: Manufactuer: Sony, Model: 456, Price: $50
Equip Item 1: Manufactuer: Sony, Model: 123, Price: $100
Accessory 1: Manufacturer: Sony, Model: 456, Price: $50
This is an extreme example, but I think it illustrates your issue.
When you run the Proposal, again you get two items:
package 1, $135 (price * discount)
Equip Item 1, $150
When you run the line item, you get:
Pkg Item 1: $90
Pkg Item 2: $45
Equip Item 1: $100
Accessory 1: $50
Remember Pkg Item 1 is the same type of item as Equip item 1 and the same for the other two items.
Now, if Package 1 is in location A and the Equip Item 1 (and the accessory) are in Location B and you run the line item grouped by location, you get:
Location A
Sony 123: $90
Sony 456: $45
Location B
Sony 123: $100
Sony 456: $50
Same items, different prices (legitimate reasons)
I think the issue is fairly complex. You have the same items with different prices in a project (for legitimate reasons), that depending on how you group the data, show up in different sections of the report (highlighting the different prices). You have heirarchically related items that you may or may not want to show via the relationship.
To loop back to your main question, I think if you're OK with all your items being broken out, you can change the recordset pattern of your custom report to "//dtr:Items/dtr:Item" and that will iterate over all the items. you'll probably have to remove the "Level 2" sub report from the main report (it may break, but certainly won't work regardess).
Ultimately, if you're looking for the data to be structured like this (a mix between flat and hierarchically related items):
Package 1: $135
Equip Item 1: $100
Accessory 1: $50
I don't think it can be done (right now).
Anyway, I know that was long (and probably rambling), but I think it was good to try and dive into how items are organized, etc. and how the reports respond to the organization of the items.
-R