How can I override the date_entered value using the edit view/action (logic hook)?

[jjwdesign]

Our sale manager gave me a task today that sounded reasonable, until I started to try to figure it out. Here's the background story. We have a bunch of leads that come in during the week from a mall booth display. We'd like to record "exactly" what days the leads came in on (time is not that important). Unfortunately, sales people often bring in the leads on the next day or on the following Monday, to be imported into the system. Our sale administrator usually handles the imports and conversions so our sales team can focus on the opportunities.

The problem we are having is that the date_entered and the day the lead was generated is not always the same. We've got a ton of leads with the wrong date_entered values.

So, how can I allow our Sales Administrator to update the date entered.
- Without SQL updates
- Without importing (as it's already imported)

I thought about setting up an override field in the Lead and then using a logic hook to overwrite the data_entered, but it doesn't seem to be working. Maybe there's a better approach

 function updateDateEntered(&$bean, $event, $arguments) {
        // Update the date_entered field based on entered_override_c field.
        if (!empty($bean->entered_override_c)) {
                $bean->date_entered = $bean->entered_override_c;
                $bean->entered_override = '';
                $bean->save(FALSE);
        } // if isset
} // end of updateDateEntered 
  

Thanks,
Jeff Walters

[kuske]

date_entered cannot be set in a hook but you can set it yourself, e.g. for cases you could set it like that:

          $db = & PearDatabase::getInstance();
         $query = "UPDATE cases set date_entered ='".$bean->entered_override_c."' WHERE id='$bean->id';";
         $result = $db->query($query, true,"Error setting date_enterd: "); 
  

[jjwdesign]

Thanks for the reply Kuske. Well, actually... I think I made it work. I'm using v5.2 CE. I was researching the forum posts and ran across a couple of interesting post. One showed how to set the date entered and date modified as importable.

Extension - Custom Vardef
/custom/Extension/modules/Leads/Ext/Vardefs/update_entered_vardefs.php

 <?php 
$dictionary['Lead']['fields']['date_entered']['importable'] = true; 
$dictionary['Lead']['fields']['date_modified']['importable'] = true; 
?>  

Then, using a "before_save" logic hook you can set the value. The second post I found. pointed out the user date format perferences. It requires some date/time traslations, but it can be done. See code below.

     function updateDateEntered(&$bean, $event, $arguments) {
    global $current_user, $sugar_config;
    $udf = $current_user->getPreference('datef');
    if ($udf == "") {
        $udf = $sugar_config['default_date_format'];
    }
   // Update the date_entered field based on entered_override_c field.
   if (!empty($bean->entered_override_c)) {
            $bean->date_entered = gmdate("Y-m-d", strtotime($bean->entered_override_c))." 16:11:11";
            $bean->entered_override_c = '';
        } // if not empty
    } // end of updateDateEntered 
  

I'm not sure if the custom vardef is needed, but it will help with my imports in the future. I'm also not sure if this creates any serious security issues. Even if it does, it's only leads. This way will also allow you to audit the fields to see who makes changes.

Cheers,
Jeff Walters