CiviCRM Community Forums (archive)

hey all

i'm trying to get michaelmcandrew's fix working in 3.0. i don't care about households, just orgs so i don't mind removing the household option and replacing it. the files are different in 3.0 so i haven't been able to get it working. has anyone else?

exactly what i'm looking for; i'd love a patch!

Hi everyone here.

I've just removed the workaround I had on the site I put it on. My one was more trouble that it was worth and it didn't really address some of the more fundamental issues they wanted addressed.  It's likely that the client will sponsor getting this sorted out 'properly' in an upcoming version, i.e. take a step back and look at uses organisational address, main point of contact for an organisation, current employer etc.

I thought I'd mention it here because this work is if all goes to plan I'd like to have this in 3.2 / 3.3 and if you / your clients are up for helping sponsor this, please let us know on this post.

Ta,
Michael

Nope.. and not in 3.1 either. It's currently on the 3.2 roadmap pending sponsorship.

http://wiki.civicrm.org/confluence/display/CRM/CiviCRM+v3.2

http://issues.civicrm.org/jira/browse/CRM-4572

Hi,

Dave wrote me about it a bit ago:

The current "spec" for this is here (draft):
http://issues.civicrm.org/jira/browse/CRM-4572

... and our estimated effort is 50 hours (@ approx $80 / hr USD discounted rate since this is work for core).


I'm still waiting some clients to see if they can sponsor a bit. Your help is definitely more than welcome, and likely to make the difference between being able to get it for the 3.2

What can you put on the table ?

you can contact me privately as well.

X+

Emily - based on the current "spec" for handling upgrades, I "think" things will be ok:

5. Upgrades
Upgrade will need to handle existing "Use Household Address" cases in the DB and migrate them to the new sharing model. For each individual contact with contact.mail_to_household_id NOT NULL, write the ID of the linked household address record to the new address.master_id column.

Doesn't seem like it will matter whether the contact records stored in mail_to_houshold_id are households or organizations - we'll need to grab their address record and link it to the individual. Of course, proof will be "in the testing" so you should stay tuned and test an upgrade carefully during 3.2 release cycle (assuming the feature does get implemented).

Hi,

I have a couple of clients that are willing to sponsor this.  Most of my clients work with organisations and individuals.

They asked me to ask if there is any appetite for expanding the scope of the 3.2 roadmap to include these top three requested associated organisation - individual usability improvements:

* integrating this with the 'current employer is' workflow: when you select current employer is, you should be prompted to say whether you want to use the organisation address.  Otherwise, you create the individual, then say they are an employee, then say that they should use the address.  IMCO (in my client's opinion what should happen is you select the current employer is, and the a work address is automatically populated (which would be the expected behaviour).  You can then un-tick to override to create a different work address, and / or create a home address for this contact.

* Be able to create an employee directly from the organisation page (with relationship and address already set).  Doing it the other way round is a bit clunky.  Compare the current situation: I am at an organisation page, I see that a contact I know isn't present.  I have to click on new contact, fill in the personal details, then select the current employer, then select use organisation address.  It would be great if from the organisation page, i can click 'add employee' and everything (relationship and work address is pre-populated).  Then all I need to do is add the name, email and the be directed to the page to make any final adjustments.

* be able to set a primary contact for an organisation (this one will need more thinking through before implemenation but)  This is the complement of being able to set a current employer for an organisation and is useful for those times in which you want to send out information to named individuals at one organisation.

OK these move slightly away from the orginal post, but are in the spirit.  Interested in your thoughts.  Will start rounding up some money.

Michael