User Logins

Hey Joseph Elvir ,

It might be possible with Trackers, but even then, Sugar should only keep that information for a period of time (so you won't end up having that information for a while). And also Trackers are normally disabled by default, as there is a global performance hit on the system.

The solution I would try is to create a code logic hook that copies data from the last_login field only on first login.

The simplest pseudocode could be:

If empty first_login_c, use last_login for first_login_c

or if you want to populate this only for newly created users the pseudocode could be:

if empty previous value of last_login and not empty current value of last_login (and maybe also double check if empty first_login_c if something else could populate it), use last_login for first_login_c 

Hope it helps

Hey Joseph Elvir ,

It might be possible with Trackers, but even then, Sugar should only keep that information for a period of time (so you won't end up having that information for a while). And also Trackers are normally disabled by default, as there is a global performance hit on the system.

The solution I would try is to create a code logic hook that copies data from the last_login field only on first login.

The simplest pseudocode could be:

If empty first_login_c, use last_login for first_login_c

or if you want to populate this only for newly created users the pseudocode could be:

if empty previous value of last_login and not empty current value of last_login (and maybe also double check if empty first_login_c if something else could populate it), use last_login for first_login_c 

Hope it helps

Hi Joseph Elvir ,

I'm interested to know more about your use case. How are you planning to use this data point? We're about to release a new version of our User Adoption plugin that supports tracking login sessions, and lets you report on the durations and trends. Your real world use case would be great to help shape our new offering.