How to separate products that are pairs - D-Tools Forum

10-16-2007, 03:30 AM

I have speakers that come as pairs and they are set up in my database that way. When I pull the item into visio, it only gives me one speaker and if I try to duplicate it I just get a second pair. Is there an easy solution to this problem? I really don't feel like reading 500 pages worth of user manual to find out.

**Kevin Mikelonis** · 10-16-2007, 03:46 PM

An issue since the beginning of time!

The manual may address this, but its really a question of best practices that work within your business structure and who you want to have managing this.

2 best options:

1. Price all speakers in your database as each, add a notation to your description 'priced as each, sold in pairs'

This method causes the back office to manage the purchase orders more closely and monitor how your manufacturers deal with each and pairs when processing P.O.'s which is a good thing as I am all for holding manufacturers and distributors accountable for the P.O.s and prices I issue to them.

2. Create a copy of each speaker in your database that is sold in pairs then:

-Mark the MFG of the copy in such a way that you know it is not an item you would order
Example: 'NILES-DNO' where DNO equals 'Do Not Order'

-Set the cost and price to zero and check the ignore cost/list box

-Make the new 'dummy' item a default or automatic accessory by checking the 'recommend' box only (leaving 'prompt' and 'recommend' unchecked to create a default or automatic accessory item does not work in SI5 at this time)

-Consider your accessory show/hide practices so you know what to expect regarding the appearance of this 'dummy item' in your client reports. In our database builds, we make all items in the database hide accessories by default, so things like speakers are only accessorized with items the client is not concerned with seeing in the proposal.

++++++++++++++++++++++++++++++++++++++++++++++++++ ++++++++

I prefer method 1 because all speakers in the database are dealt with in the same way (2 thumbs up for consistency) from a pricing and labor valuation standpoint, and forces a closer look at all purchase orders and incoming invoices which is a good thing.

With method 2, there is more to manage in the database, more exceptions so more chances for errors. The dummy item can be added to a drawing because it came in with the original item.

How you create you projects in SI also needs to be considered.

Are you a 'drag and dropper' dynamically creating projects by pulling shapes into Visio?

OR

Do use text to build the project and then move items from the datamatrix to Visio?

If you use the latter method, good for you, you are done!

If you are a drag and dropper, there is more work to do in the visualizations tab for dummy item.

We do not promote this methodology, so I am not going to elaborate on the extra work required to get there.

Head Tool · 10-16-2007, 06:16 PM

Yea, what kevin said.

10-16-2007, 09:56 PM

Thanks. I was kinda figuring I was going to have to separate the speakers into pairs to get it done. How hard do you think it would be to address the issue in the software? I was thinking that if you created a dropdown in the project creation allowing you to choose 'each' or 'pair' then when you drag the items from the project into visio it would populate with the quantity chosen. I'm sure it sounds much easier than it is.

Sunni