Can I view the SugarCRM "record ID Number" within the customer module. 

Hi Katie DelValle,

I understand this request in terms of including the ID in the import file so it checks for and does not create records with those duplicate IDs.

In the pursuit of getting this information for that import file, you have asked about displaying the ID number in the record. I think I am missing a step in this approach, though, because you mentioned wanting to avoid exporting, which means it is unclear how the ID number information displayed in the record is going to get from the screen into the import file.

Keep in mind a few things:

1. Import only looks for record ID when it checks for duplicates. It would require a custom coded solution to check a different field for duplicates.

2. The record ID number is displayed in the URL of the record when viewing it, so it is already onscreen if your user has their browser displaying the URL bar.

With very minimal custom coding, you can make a calculated custom field that displays the ID number in the record the following way:

1. For Accounts, create a custom text-type field in Studio called id_num_c

2. Calculate this field with the following interim field variable: $name

3. Save this new field in Studio

3. In the code, locate/edit the file at:

custom/Extension/modules/Accounts/Ext/Vardefs/sugarfield_id_num_c.php

4. Edit the line:

$dictionary['Account']['fields']['id_num_c']['formula']='$name';

5. Change it to:

$dictionary['Account']['fields']['id_num_c']['formula']='$id';

6. Or install through Module Loader a custom file to the above file directory path with this definition change.

I hope this helps!

I will give this solution a try. The main reason why we were hoping to have the number displayed in the record is because for our sales process the sales reps will add in their pre-sales notes in Sugar. Once the sale is awarded the customer information is manually entered into a separate billing system - which then imports data to Sugar using the company name to check for duplicates. At the end of the day this has ended up creating a lot of duplicates. 

I'll come back and update the thread if this works! Thanks again. 

Instead of relying on manual entry which is subject to human error, I would suggest you look for a solution that actually integrates your Sugar and Billing, thus avoiding duplicates and manual entry.

For example, assuming your Sales person finishes their part with a Won Opportunity. When the Opportunity is Won you could push data from Sugar to your Billing system to indicate that the sale is pending. When Billing then finalizes their side you can push back data to say it's done.

You can leverage SugarAPIs both built-in and custom to do this, and you can maintain a mapping table of SugarID and BillingID so that when Sugar pushes to Billing you can look up the ID of the Billing system based on the SugarID and vice versa. That way if one or the other does not exist you know that the record needs to be created and you can do so as part of your syncing process.

Just a thought, but it does require some programming and careful design dependent on your Billing system.

Francesca

Instead of relying on manual entry which is subject to human error, I would suggest you look for a solution that actually integrates your Sugar and Billing, thus avoiding duplicates and manual entry.

For example, assuming your Sales person finishes their part with a Won Opportunity. When the Opportunity is Won you could push data from Sugar to your Billing system to indicate that the sale is pending. When Billing then finalizes their side you can push back data to say it's done.

You can leverage SugarAPIs both built-in and custom to do this, and you can maintain a mapping table of SugarID and BillingID so that when Sugar pushes to Billing you can look up the ID of the Billing system based on the SugarID and vice versa. That way if one or the other does not exist you know that the record needs to be created and you can do so as part of your syncing process.

Just a thought, but it does require some programming and careful design dependent on your Billing system.

Francesca

That would be great if we could integrate our billing system but we have a pretty specific billing system and it required a lot of custom development just to get the data to sync from billing to Sugar. We always had the dream of getting it to also sync the other direction but we've been finding it's a lot more complicated than we hoped for -- so hasn't been done yet. 

It's a great idea though!!