David_Haddad

This is not a "how do i do this" question. I know the workarounds and use packages. I'm just curious why this limitation has always existed? Is it that it cannot be implemented using the current database structure, or is it purposeful?

SIFanatic

Originally Posted by David_Haddad

This is not a "how do i do this" question. I know the workarounds and use packages. I'm just curious why this limitation has always existed? Is it that it cannot be implemented using the current database structure, or is it purposeful?

I believe (and I may be completely wrong...) that it eliminates the possibility of accidentally adding an item that isn't intended (since an accessory is simply a link-through to another item that usually contains a price).

Then of course, there is the question of... why would you want to have an accessory within an accessory?

gnichols

Originally Posted by SIFanatic

Then of course, there is the question of... why would you want to have an accessory within an accessory?

Take a Tandberg 6000 MXP codec, which, if you want to add MultiSite (MS) as an option requires you to have added the Natural Presenter Package (NPP). Hence NPP has, as an option, MS, (aka an accessory to an accessory)... ALSO, while this could get scarily and infinately deep, MultiSite also requires full bandwidth for full functionality, so in this instance, you could be accessorizing an accessory's accessory.

Now granted, this is probably the exception, rather than the rule, but I just wanted to show that it is possible and why you might want to have an accessory to an accessory.

./g

bfourney

There have been a few times when this would have made life easier. For instance you create a SKU for custom cables that has the wire & connectors listed as accessories and you want to add that custom cable as an accessory to a product - it won't work. There are many more complex situations where it would be beneficial - adding equipment racks for instance.

With the new view in SI text I don't see why products couldn't show their accessories the same way. When you click the accessories tab accessories of accessory products would simply be listed under the main product. This way you could both overcome the current limitations, and see any potential issues directly in the product explorer.

I wonder what would happen if the parent item were an accessory of the accessory item, would it create an infinite loop?

Originally Posted by SIFanatic

Then of course, there is the question of... why would you want to have an accessory within an accessory?

curt.hayes

A simple example of this limitation is a clamp kit (-C) to a Mid-Atlantic rack shelf. Because I use a clamp kit w/every rack shelf, I can't accessorize equipment w/rack shelves for this reason. I've also run into this when accessorizing things like TV wall brackets and IR emitters.