Re: ExternalId support in relevant entities

Hello Scott, Jacques, IMO this kind of requirement requires only for few entities not all. So creating a generic pattern like EntityAuditLog or SequenceValueItem which is in general applicable to most of the entity as per requirement may give signal or OFBiz user that this is something which is

Re: ExternalId support in relevant entities

Thanks Scott, I think that if it's well documented the EntityIdentification could be a good solution to this problem Jacques Le 02/05/2019 à 22:24, Scott Gray a écrit : I'd tend to agree with Pierre here, following the {entity}Identification pattern is probably a better approach long term

Re: ExternalId support in relevant entities

I'd tend to agree with Pierre here, following the {entity}Identification pattern is probably a better approach long term simply because the externalId pattern breaks as soon as you need more than one identifier. If the likelihood of multiple IDs is low, then the {entity}Attribute pattern might be

Re: ExternalId support in relevant entities

Current methodology of having the externalId field in the various tables is limiting the capabilities of OFBiz. With this an object can have only 1 externalId value. However, it is quite feasible that an object can be associated with various external systems with each having a different externalId

Re: ExternalId support in relevant entities

Nice enhancement +1, I would like to add Shipment entity into the list. -- Kind Regards, *Pawan Verma* | Technical Consultant HotWax Systems Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore, M.P. 452010 Linkedin: *Pawan Verma

ExternalId support in relevant entities

Hello team, As far as my understanding, externalId in OrderHeader is used to save orderId reference of any other system into our system. If this is the only case, we should also maintain something similar on following entities as well as consistency and they will be in need in case of a