Loading leads into the system

[wdroush]

Our current CRM has us load our leads into our system like this:

1. Upload excel file
2. Map it out (column = value)
3. Leads are in database "hidden".
4. User pulls up lead by putting in their reference code, it will load up the lead and make him unhidden.

Is there a way to replicate this functionality in SugarCRM without writing my own module? I have to have this up and running by Wednesday and don't think I can go from a blank slate to writing my own module from scratch (I do a bit of programming, but haven't worked with SugarCRM). Doesn't have to work exactly the same, but a way to import leads via an excel file (CSV or .XLS), and leads get imported via their reference code when a sales person puts it into the system.


I have some understanding of modifying the interface, so I can add the fields, I just need the functionality.

----------------------------------------------------------------------------------------------------------------
Edit:
Answer - The functionality I'm actually looking for is "targets", being as they are targets to a marketing campaign, this allows me to convert them to leads as they call in, it allows for mass importing, tracking and transfer of reference codes, and it keeps them out of the leads system is they never become active, it also allows for tracking of the number of targets coming in from certain marketing campaigns.

[andopes]

3. Leads are in database "hidden".
Actually "hidden" leads should be the marked as deleted ones. If you would like to consider another field to let sugar hid them, so you need to make some code.

4. User pulls up lead by putting in their reference code, it will load up the lead and make him unhidden.
It is possible if you map the own lead id when importing it (reference code), this way sugar will update it, rather than create another one.

Cheers

[wdroush]

3. Leads are in database "hidden".
Actually "hidden" leads should be the marked as deleted ones. If you would like to consider another field to let sugar hid them, so you need to make some code.

4. User pulls up lead by putting in their reference code, it will load up the lead and make him unhidden.
It is possible if you map the own lead id when importing it (reference code), this way sugar will update it, rather than create another one.

Cheers

Well by "hidden" I didn't necessarily mean the field, but just not visible by anyone except the back end, and maybe administrators, they shouldn't clash with live leads, being as we import these by 20k every couple weeks, and lots of them may not even call us.

Basically they're people that we send out mail to, they call, give us a reference code, we pull their information into the lead system based off of this reference code (which is linked to name, address, etc.)... We don't need to load them into leads if there is another system to hold these mailers in, so long as we can migrate them over to a lead via reference code.


So how would I map a reference code? How would I make it so the end user can put in a reference code and pull the lead out of the "invisible" section?

[andopes]

1. Create a check box field to indicate it will be hidden if check box is ticked.
2. Create a custom controller for Leads to redefine the bean Class to hid the leads whose check box field is ticked;
3. Import all Leads with the check box field ticked and the id field filed in with some distinct value;
4. Import a Leads list containing the id and the check box field unticked, remember to select the option "Update" on Import screen, this will update the check box value whose id is the one provided.

Done

[wdroush]

Ok, so looking at that, it may be easier to write a quick module to process an excel file (or even an external application), spit it out into a different table, and have the module create a "pull lead by refid" quick panel on the leads page where it will transfer everything from the references table to the leads table... yes?

Especially considering the lead import system seems to be lacking in stuff such as field mapping.


And I think what you're setting up for me is backwards, I want to import these users first, and then from there sales people will punch in the refcode and that will pull them up and assign the lead to them.


Edit:
Nevermind your way seems way easier, minus having no clue how I'd create my own "bean class", but then I can tweak quickcreate to be my data puller and everything will be perfect. Any good tutorials?

[wdroush]

I think I found a better solution... these are not leads, they are targets of marketing campaigns, and should be used as such.


So I import targets, and then the user can search and create them as a lead. I'm not 100% sure how I want to maintain this (I don't want to allow users to grab targets they don't have a reference code for...), but I think this is a much better solution.


And I don't think I care if they're visible to a whole list of users, to be honest I'll probably block everyone from the campaigns except administrators, and then I'll make some kind of simple script that will allow them to convert a target to a lead or a simple module.