Dev - store specific introduction & discontinuation dates for products

[Si Chen-2]

Hi.

We need to implement a feature where products have different
introduction & discontinuation dates for each store.  I was thinking of
creating a new entity ProductStoreDates with productStoreId*,
productId*, introductionDate, discontinuationDate.  Would this be a good
thing to put back into the framework?

Si

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Andrew Sykes]

Si,

I'm not sure why you would need this.

You already have from and thru dates on the ProductCategoryMember.

So assuming you keep the Category unique to the ProductStore, the
functionality you're describing is already there.
--
Kind Regards
Andrew Sykes <[hidden email]>
Sykes Development Ltd
http://www.sykesdevelopment.com

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[David E. Jones]

This sort of store-specific (or perhaps catalog-specific?) setting does come up every so often. In addition to these dates another one that sometimes comes up is a primary category for each product on a per store/catalog basis, and the same for the primary parent category ID. These can be used to back-trace a category path to the root browse category when only the productId is available (helpful for bread-crumbs and such on a product detail or category detail page).

-David


Si Chen wrote:

> Hi.
>
> We need to implement a feature where products have different
> introduction & discontinuation dates for each store.  I was thinking of
> creating a new entity ProductStoreDates with productStoreId*,
> productId*, introductionDate, discontinuationDate.  Would this be a good
> thing to put back into the framework?
>
> Si
>
>  
> _______________________________________________
> Dev mailing list
> [hidden email]
> http://lists.ofbiz.org/mailman/listinfo/dev

... [show rest of quote]

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev

[Si Chen-2]

Ok, so I'll make it more generic of an entity then so we can use it to store the other stuff as well.

Si

David E. Jones wrote:

This sort of store-specific (or perhaps catalog-specific?) setting does come up every so often. In addition to these dates another one that sometimes comes up is a primary category for each product on a per store/catalog basis, and the same for the primary parent category ID. These can be used to back-trace a category path to the root browse category when only the productId is available (helpful for bread-crumbs and such on a product detail or category detail page).

-David


Si Chen wrote:
  

Hi. 

We need to implement a feature where products have different 
introduction & discontinuation dates for each store.  I was thinking of 
creating a new entity ProductStoreDates with productStoreId*, 
productId*, introductionDate, discontinuationDate.  Would this be a good 
thing to put back into the framework?

Si

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
    

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev


  

... [show rest of quote]

 
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev