Hello Deepak, We might need to change good identification value anytime due to change in the third-party system or due to other reason. So to track the previous/old value we may need to maintain it by date constraint. At a time only one identification will be active for a product of the same type.
Best, *Aishwary Shrivastava* On Sat, Apr 27, 2019 at 1:17 PM Nicolas Malin <nicolas.ma...@nereide.fr> wrote: > I'm mixed about that idea. > > GoodIdentification like PartyIdentification are useful to search on > multiple identification shared by other system. Add life-stamp will add > complexity the resolve quickly a element. Like a name 99% case it's more > important to have the current identification list. Maybe a history > entity (as GoodIdentificationHistory) would be more simple to implement > and sufficient to your problematic ? > > Nicolas > > On 27/04/2019 09:22, Arun Patidar wrote: > > +1, looks good to me. > > > > This will require changes in existing CRUD operations related to > > GoodIdentifications. Also may need migration service or SQL scripts. > > > > > > -- > > Best Regards, > > Arun Patidar > > www.hotwax.co > > > > > > > > On Sat, Apr 27, 2019 at 12:42 PM Aishwary Shrivastava < > > aishwary.shrivast...@hotwaxsystems.com> wrote: > > > >> 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/> > >> >
