-1 for the proposal. For a product identification code will be one of one type. The universal data model book by Len Silverston suggested the same.
Best Regards, -- *Rishi Solanki* | Sr Manager, Enterprise Software Development HotWax Systems <http://www.hotwaxsystems.com/> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore, M.P 452010 Linkedin: *Rishi Solanki* <https://www.linkedin.com/in/rishi-solanki-62271b7/> Direct: +91-9893287847 On Sat, Apr 27, 2019 at 4:03 PM Michael Brohl <michael.br...@ecomify.de> wrote: > Hi Aishwary, > > can you elaborate a bit more why a history of GoodIdentification is needed? > > It is used for identification numbers as ISBN, EAN etc.. Those numbers > are rarely subject to change for the same product. > > I don't see any use case for history tracking so I would appreciate some > examples. > > Thanks, > > Michael Brohl > > ecomify GmbH - www.ecomify.de > > > Am 27.04.19 um 09:11 schrieb Aishwary Shrivastava: > > Hello, Devs > > > > We should add support of fromDate and thruDate in the GoodIdentification > > entity for tracking and history purpose. > > > > As of now, if we need to update any Good Identification record for a > > product, then we have to replace its value and this history isn't > > maintained. > > It will also enable the user to maintain multiple goodIdentifications of > a > > product. > > > > Best, > > *Aishwary Shrivastava* | HotWax Systems <http://www.hotwaxsystems.com/> > > > >
