We have spent thousands on integrating the infusion API with our membership site and the latest upgrade completely destroyed all of the work we have done. We now have to find another work around with the FEAR that the next update will do the same.

Things are changed and moved around with no warning, new upgrades break old work arounds. Infusionsoft so far doesn't do what it is supposed to do. In the marketing for infusion soft you talk about solving my problems, I now have more new ones and they are bigger than ever.

If the support was there I would gladly work through the problems but the changes come so fast that even they can't keep up.

We have tried tickets and support no one seems to be able to help. Am I alone here or are others finding that there are some problems here.

Sorry to hear this, I am looking into a way to integrate our membership site with Infusionsoft as well but would not want to start down a path that would get reversed with each new update. Maybe someone in Tech Support who sees this can address the issue.

What exactly is the problem you are experiencing? If you don't feel like posting the details, please shoot me a PM.

We have certain contact record fields that get "posted" to our server. These fields control membership status etc, etc. As of the "upgrade" action sets are no longer able to change these entries automatically (ie card failure actions don't turn them into "unpaid" members) and don't get posted to the site and updated - or worse yet are the currently free members that pay, and they don't get their membership access that they paid for - now they are mad at me.

It sounds like you are trying to use the "Set a Contact Field" Action Set action to set custom contact fields... Specifically, off of a Credit Card trigger. Am I right?

It was certainly not intentional to remove that functionality. Sounds like a bug to me.

...

Went ahead an ran a test of this. My Action Set still sets the custom field. So what I would recommend is that you create a Case over on the Fusebox for Support to look into this in further detail.

Sorry you are having trouble.

Thanks for the input, we are not using "Set a Contact Field" Action Set action to set custom contact fields as custom fields do not get posted (although they should), we were using the default contact id field, specifically - contact type and Lead source as they will post.

Oh, I see. You are using the "send an http post to another server" action.

I just ran a test and it posted contact data for me. But I am working off a build that has not been released yet. The good news for you is that means if it hasn't already been fixed it probably will be in the next maintenance release.

I still recommend that you open a Case over on the Fusebox and have Support look into this with you, though.

You're not alone. I've been waiting MONTHS to get a bug resolved that has to do with fulfillment reports that we happen to run every 30 days. Isoft says it take long to test due to timeframe -- i suggested they set up a test fulfillment campaign with a 1 day increment. This isn't rocket science. Still no answer. ARRRGGGG!

Hi, folks --

Mike is a team member on the team who investigates these types of bugs. We met just a moment ago and it appears that the HTTP Post is running slow.

There are a handful of customers who reported this and we're looking into it. Sorry for the inconvenience (and thanks for your patience)!

--Joe

I can understand everyone's frustration. While working with ISoft, I had several issues that went unfixed. I reported most of these through e-mail and seldom got a response.

However, any time that I called ISoft, even if it meant 45 minutes on hold, someone could usually help me by giving me a work around.

ISoft may want to address the lack of tech support and if nothing else, place more man-hours on known tech issues.

Just a personal opinion.