jpol

In SI4.6, I used to be able to use a part I created (say ABC Note) where ABC is the manufacturer and Note is the model. I entered the part once and said "install TV, the second was "install dvd", a third to "install cable receiver". When you would run the report, though it was the same manufacturer and model, it would be handled as seperate items since the description was different.

In the new SI5, has anyone figured out a way to do this? It keeps grouping all these together with a Qty of "3" instead and displaying the description of whatever one is on top (I guess), so I loose the notes for the other two itmes.

RickC

Originally Posted by jpol

In SI4.6, I used to be able to use a part I created (say ABC Note) where ABC is the manufacturer and Note is the model. I entered the part once and said "install TV, the second was "install dvd", a third to "install cable receiver". When you would run the report, though it was the same manufacturer and model, it would be handled as seperate items since the description was different. In the new SI5, has anyone figured out a way to do this? It keeps grouping all these together with a Qty of "3" instead and displaying the description of whatever one is on top (I guess), so I loose the notes for the other two itmes.

In SI, items are keyed by Manufacturer, Model, Category. I'm going to assume these are Labor items you're talking about above (but it doesn't have to be).

Given the way items are keyed, you do get a quantity of 3 for Manufacturer: ABC, Model: Note, Category: labor.

Most likely, it's last in wins for the description. The report engine is grouping on ItemHash (which is value based off manu, model, category. See thread: Sorting products in report for more info).

One way to approach this would be to create separate items:

Manufacturer: ABC
Model: Note: Install DVD
Category: Labor

Manufacturer: ABC
Model: Note: Install TV
Category: Labor

Manufacturer: ABC
Model: Note: Install Cable Receiver
Category: Labor

I know that this would take a bit of work on your end (initially), but that would do it for you and would subsequently not require you to modify the description for each instance as you dropped it into the project.

Hope this helps.

-R

jpol

so is there a way to edit the ItemHash for manu, model, description? There has to be a config file I can go edit. I'll sign a relese like when i asked to download and edit my MasterTable. This is huge for me... we use a "Note" part (for instance) to enter notes into a specific zone for our installers. This is bigger than just making a few extra parts.

RickC

Originally Posted by jpol

so is there a way to edit the ItemHash for manu, model, description? There has to be a config file I can go edit. I'll sign a relese like when i asked to download and edit my MasterTable. This is huge for me... we use a "Note" part (for instance) to enter notes into a specific zone for our installers. This is bigger than just making a few extra parts.

There is no way to configure how the itemhash is generated. that's an iteresting idea (maybe a bit of a loaded gun, but interesting). It is based on strictly on how we key items in MMPD (manu, model, category) and the items a parent item may contain).

That said, I gave this a try and it seemed to work, but you'll want to verify for yourself. Here's what I did:

1. Created a new report based on the Proposal (any variant of the proposal will work).
2. In the Report Wizard, I added a required Sort for Description.
3. When the layout was loaded in the Report designer, I selected the section named "grpItemHeader".
4. In the Properties Window, I changed the DataField property from "dtr:Itemhash" to "dtr: Description" (no space between the "dtr:" and "Description", big grin smilie () is injecting itself...). (This tells the report engine to break on changes in the description now (create a new section instance in the report).
5. Saved, published, and run the report.

Here's why it should work for you: Groupings are nothing more than Ascending Sorts, Adding a required grouping, further sorts the items by description see: Sorting products in report for details on how the sort stack is built.

Now the items are sorted correctly and the report section is set to break on changes in the description.

A couple of things to consider:

• Different items with the same description that ended up sorted next to each other, will get grouped. This will probably only happen in VERY rare occasions based on the other sorting that happens before this (itemhash in particular).
• If these "Note" items exist in packages or are accessories to equipment items, custom "Level2" and "Level" sub reports will have to be created to break on description instead of Itemhash. The sub report controls in the parent reports will have to be bound to the custom sub reports.
  
  If you need to do this, here are the things that you need to consider:
  • Determine which proposal variant you are going to base your report off of and modify the corresponding level reports (If you're using the "Proposal with Images" as your base, use the "Proposal Level 2 (and 3) With Images" as the sub report bases.
  • Modify the Level 3 report first, then level 2 report. This is because the Level 2 Report binds the level 3 report to a sub report control. So you'll need to change the binding. No need to create a level 2 custom report, publish it, create a level 3 custom report, then re-open the level 2 report to bind in the new level 3 report. The sub report control in the level 2 report for the level 3 items is in the "grpItemFooter" section, it's a small sliver...
  • Once the sub reports are created, bind them into the main report (the sub report control for the level 2 report is in the grpItemFooter section of the main proposal). This doc, while a bit different, discusses binding sub reportshttp://downloads.d-tools.com/si5/rep...ct_Summary.pdf

This should get you pretty close to what you're looking to accomplish.

-R

jpol

Originally Posted by RickC

There is no way to configure how the itemhash is generated. that's an iteresting idea (maybe a bit of a loaded gun, but interesting). It is based on strictly on how we key items in MMPD (manu, model, category) and the items a parent item may contain). That said, I gave this a try and it seemed to work, but you'll want to verify for yourself. Here's what I did: Created a new report based on the Proposal (any variant of the proposal will work). In the Report Wizard, I added a required Sort for Description. When the layout was loaded in the Report designer, I selected the section named "grpItemHeader". In the Properties Window, I changed the DataField property from "dtr:Itemhash" to "dtr: Description" (no space between the "dtr:" and "Description", big grin smilie () is injecting itself...). (This tells the report engine to break on changes in the description now (create a new section instance in the report). Saved, published, and run the report. Here's why it should work for you: Groupings are nothing more than Ascending Sorts, Adding a required grouping, further sorts the items by description see: Sorting products in report for details on how the sort stack is built. Now the items are sorted correctly and the report section is set to break on changes in the description. -R

Awesome!!! This works perfect. You don't know how much time and effort this simple fix just saved! Thanks!!!!