multiple account owners!

[cerhorn]

We are a multi-division company, and salespeople from each division operate completely independent of each other. They also sell to the same accounts. On accounts where there is more than one "owner", what have other people done to designate 2 owners? We are using Commuity edition 4.5.1.

We have considered adding a field to the account record to show the other salesperson, but not sure how this would work in security - both people need to be able to update the account record.

I guess we could create separate account records for each division, and then have them roll up to a corporate account record as members, but that seems like needless duplication.

Suggestions?

[eggsurplus]

I'd suggest using Teams and assigning each sales team to the record. From what I understand TeamsOS and Sugar's Teams for Ent/Pro only allow one team assignment per record. I've made something that mimics this ability to assignment multiple teams to records by using the built in roles. It may or may not be what you're looking for: http://www.sugarforge.org/projects/roleowner/

[cerhorn]

Thanks!

Actually, if I can use this to make multiple owners of a record I don't need teams.

[cerhorn]

Well, I thought perhaps I could add RoleOwner without first loading TeamsOS. That didn't work, and it seems to have updated something that now prevents the module loader from starting. I get a SQL error in a where clause that is looking for a column that doesn't exist.

Am I assuming correctly that this was caused by loading RoleOwner without Teams? Can I repair somehow?

[eggsurplus]

I was unaware of any issue but I will test it to see what is going on. It won't work with TeamsOS though.

[cerhorn]

I'm not sure I understand completely how roleowner is supposed to work. Is there something published that would walk me through an example?

I would simply like to assign multiple users to a role, then assign the role as the owner of an Account record. This would solve my problem......

[cerhorn]

I was unaware of any issue but I will test it to see what is going on. It won't work with TeamsOS though.

I fixed this by truncating the upgrade_history table. At least now I can run module loader.

[eggsurplus]

So do you think it was just that one more module install put it over the edge and cleaning the upgrade history table allowed it some room?

[cerhorn]

No - the sql error I got showed that it expected a column in the upgrade_history table that didn't exist in this version (4.5.1b). I believe the column missing was upgrade_history.deleted. I took a chance that truncating the table would give me a chance to get module loader and upgrade wizard to work.

I think I need to upgrade to the latest version..........