Our business has been using Infusionsoft for about 1.5 years now and yeah like everyone we've experienced the up updates, down servers, glitches, patches, data errors and such. But it's starts to wear thin when the 1 function we bought into the program for FAILS.

All we want is our LEADSOURCE ID to work and yet it doesn't (since update 1.16.3.10) and no one has delivered a solution.
Yes I've put in a CASE and I've even had promises of a patch and then a update that have both haven't been fulfilled. It's been 22 days now without leadsources being applied to contact records, hence no reporting or idea what working or not working.

I just need somewhere to be able to state my complaint and have action taken according to the importance.

Who can help?

Anton
Soundtherapyinternational.com

Anton,

How are you using the Leadsources? Creating new Contacts manually, Web Form submissions, setting it with an Action Set, setting it with the Mass Update report action, the API... Something else?

Also, something that may be related - there is a Permission for whether or not a given user is allowed to change the Leadsource set for a given Contact.

Lastly, what is your Case #?

OK thanks for your interest Miked.

Leadsources don't set from webforms , nor do they set by mass update. Apart from manually updating each new contact as it come in it just doesn't function.

I've got complete user permissions so that's not the problem...infusion has identified/admitted there is a problem they just haven't solved it.


If you can access my case it's 22677

Cheers Anton

I have escalated your case for our developers to look at.

After looking into this, here is what I have discovered:

- when 1.17.2.x is released, the Mass Update action will allow you to override Leadsources. Use carefully!

- Web Form submissions will SET a Leadsource but will not overwrite an existing one. I tested both adding and updating existing contacts.

So, if an existing contact did not already have a Leadsource it would set it. BUT, I noticed an odd quirk... If you had that contact open already and submitted the form in another window / tab the change was made in the database but refreshing the screen with the contact open would not make it show up. I had to force a reload from the database by clicking on that contact in the Recently Viewed list on the side bar. Then the Leadsource showed up.

Hope this helps. If you have more concerns, please provide as many details as you can.

Yes I've been told before that I will have to wait for the 1.17 update.
Still I can't see why the leadsource ID field has been affected that i can't get it to populate from a webform...regarless of a new or old contact.
So every contact that is coming in has N/A as a leadsource.
It all fell over when you guys updated way back on the 5th Aug I think it was 1.16.3.9 perhaps.

Hey put me back on that then ...at least it works. Why am I the the only one effected? how does everyone else assign leadsource by webform?

Anton

Hey Miked,

OK what do we do next ?... 1.17.2.4 is now the curret version and I've still got the problem that the webforms are not populating a Leadsource.
Can I get a little help?

I guess I need more information from you. I've tested this and it appears to be *working.

How, exactly, are you using the Web Form? And how, exactly, are you testing it? Please be as specific as possible.


*working, in this case, is defined as:
- if the person does not have a Leadsource already set, it will set it
- if the person DOES have a Leadsource already set, it will NOT set it (as designed)

If you log into my app soundtherapy and try any webform in any manner you like (even try creating a new on from scratch) I bet you can't get it to simply set the leadsouce field to anything other than N/A.

Yes I creat new contact records when testing to simulate new leads coming in.

You name it I've tried it ...my app just mustn't function like everyone elses. Can't tell you why, but since the update around the 5th of August everything has been stuffed.

Anton

Thank you for the additional information! We were able to track down the problem.

It seems that the Action Set action to Set a Contact Field to a Specific Value is not working in this instance. At least, not for Leadsources.

I talked to the Team Lead for our CRM Dev Team about this and he is now very aware of your issue and the ticket I created for you.