Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

Hello Deepak, Nice Idea ! Thanks ! I think that we could have a new entity-auto invoke type, kind of "update-immutable" to manage the immutable case. Then for the specific but existing need of PostalAddress fix (we met the need to fix a postalAddress without creating a new instance), we

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

+1 Deepak!! Rishi Solanki Sr Manager, Enterprise Software Development HotWax Systems Pvt. Ltd. Direct: +91-9893287847 http://www.hotwaxsystems.com www.hotwax.co On Sat, Feb 24, 2018 at 11:44 AM, Deepak Dixit < deepak.di...@hotwaxsystems.com> wrote: > Yes it may confuse but I think its correct,

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

Yes it may confuse but I think its correct, the basic rule is if you want to update postal address (ContactMech) it will expire old one and create new one with update. So Ideally PostalAddress is an immutable object where you can;t do modification in it. if you want to update you need to clone it

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

Hi Gil, Personally, I understand your point of view, but renaming service could have major impact to existing code... May be we could add a parameter to keep or leave history. regards Pierre On 23/02/2018 15:56, Taher Alkhateeb wrote: perhaps updatePostalAddressWithHistory On Fri, Feb 23,

Re: updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

perhaps updatePostalAddressWithHistory On Fri, Feb 23, 2018 at 5:41 PM, gil portenseigne wrote: > Hello, > > While working on a new contactMech type (no spoiler yet, that will come in > some days ;)), I wanted to develop the CRUD services , and stumbled upon >

updatePostalAddress, updateTelecomNumber (contactMechs) missnamed ?

Hello, While working on a new contactMech type (no spoiler yet, that will come in some days ;)), I wanted to develop the CRUD services , and stumbled upon something that bother me. Actually, when we update a contactMech in OFBiz, the service keep history of it, to keep reference for related

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

label improvement, not a big deal ;) > ContactMechs Label > -- > > Key: OFBIZ-6856 > URL: https://issues.apache.org/jira/browse/OFBIZ-6856 > Project: OFBiz > Issue Type: Bug > Components: produ

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

[ https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien NICOLAS updated OFBIZ-6856: -- Attachment: JIRA6856-1412.patch > ContactMechs La

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

) branch 13.07, you should also backport it to branches 14.12 and 15.12. But frankly this is an improvement. > ContactMechs Label > -- > > Key: OFBIZ-6856 > URL: https://issues.apache.org/jira/browse/OFBIZ-6856 >

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

[ https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien NICOLAS updated OFBIZ-6856: -- Attachment: JIRA6856-1512.patch > ContactMechs La

[jira] [Comment Edited] (OFBIZ-6856) ContactMechs Label

fixed in release : Trunk 1727207 13.07 1727212 14.12 1727261 15.12 1727273 was (Author: julien.nicolas): Issue fixed in release : Trunk 1727207 13.07 1727212 > ContactMechs Label > -- > > Key: OFBIZ-6856 > URL: https://issues.apache.

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

anyway > ContactMechs Label > -- > > Key: OFBIZ-6856 > URL: https://issues.apache.org/jira/browse/OFBIZ-6856 > Project: OFBiz > Issue Type: Bug > Components: product >Affect

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

> ContactMechs Label > -- > > Key: OFBIZ-6856 > URL: https://issues.apache.org/jira/browse/OFBIZ-6856 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versions: Trunk, 13.07.02 &g

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

translation for trunk > ContactMechs Label > -- > > Key: OFBIZ-6856 > URL: https://issues.apache.org/jira/browse/OFBIZ-6856 > Project: OFBiz > Issue Type: Bug > Components: product >Affect

[jira] [Closed] (OFBIZ-6856) ContactMechs Label

[ https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien NICOLAS closed OFBIZ-6856. - > ContactMechs Label > -- > > Key: OFBIZ-6856 >

[jira] [Updated] (OFBIZ-6856) ContactMechs Label

[ https://issues.apache.org/jira/browse/OFBIZ-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julien NICOLAS updated OFBIZ-6856: -- Attachment: JIRA6856-1307.patch Patch for 13.07 > ContactMechs La

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

t I was thinking to solve it asap >and think "If I create Jira, it will be visible in the ML Dev".. Yes but some, like me, filter Jira issues in different email client folders, so it's easier to follow and discuss when well separating things (at least for me :)) >

ContactMechs

Is it normal that in facility, the label for contact information is named "ContactMechs". I think it could be a mistake but I'm French and maybe I miss something. Anyway, I think this label must be "Contact Mechs" and if we want to standardize the contact mech label,

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

before but I was thinking to solve it asap and think "If I create Jira, it will be visible in the ML Dev"... Anyway, I'll do it. And... Thank you to remember me this old topic, I was laughing the first time and laugh today again ! :D :D :D I miss Adrian for that too ! > Conta

Re: ContactMechs

across the applications where possible. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/ContactMechs-tp4676462p4676473.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.

[jira] [Created] (OFBIZ-6856) ContactMechs Label

Julien NICOLAS created OFBIZ-6856: - Summary: ContactMechs Label Key: OFBIZ-6856 URL: https://issues.apache.org/jira/browse/OFBIZ-6856 Project: OFBiz Issue Type: Bug Components

[jira] [Commented] (OFBIZ-6856) ContactMechs Label

gmwqsei Thanks! > ContactMechs Label > -- > > Key: OFBIZ-6856 > URL: https://issues.apache.org/jira/browse/OFBIZ-6856 > Project: OFBiz > Issue Type: Bug > Components: product >Affects Versi