Are you successfully auditing Email Address changes?

[datasponge]

Please respond if you are successfully auditing email address changes from any module even if it is simply a Yes.

Or if you tried it and couldn't get it working just answer No.

Of course, more info is greatly appreciated, but right now I just want to determine if this is possible before putting more significant effort into it and I haven't gotten any response to earlier threads. See

http://www.sugarcrm.com/forums/showthread.php?t=31656

and

http://www.sugarcrm.com/forums/showthread.php?t=31557

Thanks

Phil

[datasponge]

I take it no one is auditing email addresses?

Phil

[clint]

Entirely possible this is a bug in 5.0. We completely reworked the email address db schema in 5.0 and its possible that auditing of email addresses is now broken.

I'll have one of the engineers look into this.

[franklin_sugar]

Hi Phil,

Currently, email address auditing is not supported in the current release.

In general, any relationship auditing is not supported now.

Thanks,
Franklin

[datasponge]

Hi Franklin,

That was the impression I was getting from my experiments and digging into the structure.

Thanks for the definitive answer.


Now, since this is valuable enough that Emails were one of the original fields defined for auditing per Clints post from a while back, and since Email change auditing was apparently supported in previous versions . . .

What is the plan to support auditing linked/related data fields? When?

Thanks

Phil

[wjohnson]

Franklin,

Is the plan for the future to have no relationship auditing?

I think it would be nice if there was a page in the wiki letting users know what features they may be currently using are scheduled for future removal.

Will

[clint]

Franklin,

Is the plan for the future to have no relationship auditing?

I think it would be nice if there was a page in the wiki letting users know what features they may be currently using are scheduled for future removal.

Will

Hi Will -

It is not our plan in general to remove features. What happened in this case is that we had to trade off the feature of auditing email addresses for a more scalable database schema design.

The schema that we had in previous releases for email addresses was causing significant scalaibility and performance issues. So we had to redesign the schema so that email addresses are stored in their own database table and are now related to the parent object (lead, contact, account, etc) as opposed to being a field on the parent object.

Unfortunately we do not yet support auditing relationship changes and had to make the tough choice of dropping that feature in exchange for better performance.

We do plan to add relationship auditing in an upcoming release. We do apologize for the inconvenience.

Regards,
Clint

[cyberrodent]

As of Sugar 5.2c (May 2009) I am still seeing that this relationship is not auditing. This is a serious gap that IMO sugar should plan on fixing ASAP. I hope they have someone reading this list

[maggie.d]

As of Sugar 5.2c (May 2009) I am still seeing that this relationship is not auditing. This is a serious gap that IMO sugar should plan on fixing ASAP. I hope they have someone reading this list

I hope there is too. We recently upgraded from 4.5.1 to 5.2.0k; and it now no longer works for us. I've been directed to Bug '26130, dated November 2008, which indicates that the target release version is 5.5. I've just tested version 5.5.0RC4 but the Contacts module is still not showing changed email addresses.

Tracking email address changes is essential for maintaining a useful database, and this loss of functionality is bad news for Sugar and its users.

PLEASE can this be brought back for the full 5.5 release????

Regards,
Maggie