Search results by user ID 6143

Re: Why is the default currency always CAD? Arrrgg

Roper724 — Fri, 25 Sep 2015 20:49:45 GMT

Thanks for the tip. Unfortunately, what this setting apparently does is merely display the converted values to USD.

After making this change, I proceeded to my website to fill out a new Web-To-Lead form which in turn created a new Lead in Method. I then converted the lead to a Customer so that it would then register in QuickBooks Online. When I switch over QBO and look up the new customer, it show the currency as CAD.

This has been a HUGE complaint of mine with QuickBooks for the last 5 years and I thought with QBO they finally fixed it. Wrong.

Maybe QBO would lend you guys at Method a better ear on this topic. It boggles my mind how somebody at Intuit has not realized what a MAJOR BUG this is. I can't event maintain a list of products and services in QBO in USD. The only way I can set the default currency for a customer in QBO is if I set it up manually. Even then, QBO wants to insert Invoice and Estimate products as CAD instead of USD.

C'mon Method Team! I know you guys have some type of backdoor, open channel with those guys -- like the Bat Phone! This needs looking into to!

Thanks for the quick response. Looks like the problem is not with Method but hopefully you guys can pursuade somebody at Intuit to look into this seriously for once.

Why is the default currency always CAD? Arrrgg

Roper724 — Fri, 25 Sep 2015 19:46:15 GMT

I am a Canadian company using QB Online and I am using a Web-To-Lead form to create a new Lead Contact with every download.

I will be converting leads into contacts once they buy.

Here's my problem. My Lead's currency defaults to CAD. In QBO, my default currency is CAD which is a pain for invoicing because I do 99% of my transactions in USD. I am trying for the life of me to change the behaviour of "new leads" or "new contacts" so that the default currency is USD.

Hopefully there's an easy solution. If the answer is "Method is tied to the behavior of QBO", then that sucks! I have no clue who's in the design dept. at QBO because they just assume that Canadian companies will ALWAYS do business in CAD currency. That simply is not the case and I've mentioned this to them before.

Sorry for digressing. Anyway, I hope Method has a good answer (aka: solution) for me. Thanks everyone.

Re: Error posting WebForm server-side using ASP Classic

Roper724 — Thu, 24 Sep 2015 19:18:39 GMT

Thanks James!!!!!!!!!!!!

Maybe I will finally get somewhere. Unbelievable! Will advise...

Re: Error posting WebForm server-side using ASP Classic

Roper724 — Thu, 24 Sep 2015 18:37:23 GMT

Thanks James.

I just copied the plain old HTML page to my server and then filled it in. I get the same error.

I put in a support ticket with my hosting provider to see if they have some crazy security measures in place that are getting in the way. It would not surprise me because I had something similar many years ago, I think it had to do with MS SQL.

Once I hear back from them, I'll take a renewed look at just the plain old HTML form and go from there.

NOTE: I will be very displeased if it's been my hosting provider causing the problem all along.

I will report back with my findings.

BTW: The name is John. I have to change my moniker.

Cheers!

Re: Error posting WebForm server-side using ASP Classic

Roper724 — Thu, 24 Sep 2015 17:51:24 GMT

Thanks James. I fixed the typo for "redUrl" to "retURL" and no difference.

The oid is correct.

I've make sure that my Web-To-Lead form exists within Method and that my ASP code corresponds exactly to the same INPUT items.

My site is SSL encrypted by default so I've inputted both "https" and "http" for the web form authentication (Step 1).

I also want to reiterate that I've tried using the default "destURL" and the one that removes the "timezonerouter" url from the variable. Both fail with the same error.

At this point, there appears to be nothing wrong with my implementation. The "web2lead.asp" file is stored in the folder "/asp/web2lead.asp" off the root of my site. Obviously it fires.

At this point, I'm tired of hitting my head on a brick wall. I would love to see what code you have in ColdFusion. I'm sure I can map it to an ASP context.

Error posting WebForm server-side using ASP Classic

Roper724 — Thu, 24 Sep 2015 01:44:12 GMT

I've read the posts about web forms and it surprises me how difficult such a simple thing could be. Bascially, I used Method to generate a Basic Web-To-Lead form and changed nothing. I then took the source code and took away all of the javascript and the form HTML tags and preserved the "id" values, including the hidden boxes. The next step should be very straight forward. Create an MSXML2.ServerXMLHTTP object, Open the object, set some parameters and send it away.

But for some reason, I keep getting the following annoying error:

We couldn't authenticate web form provider. Please contact web form provider for any additional information.

I read in a post on Method that the "timezonerouter.aspx" might cause some problems. So I tried submitting my test form (web2lead.asp) using it and not using it. The same issue arises.

Now, yes, ASP.NET certainly would be easier by using the Method API's web service. But unfortunately, I have not delved enough into ASP.NET to appreciate if I require code behind pages or a GUI on my page. So while it's ironic that I"m a present-day C# and .NET user, I still use good old classic ASP to get my data stuff done.

Here is my code. Hopefully someone at Method can give me some insight as to what I'm doing wrong here. It should work.

<% @LANGUAGE="VBScript" %>
<% Response.buffer = true %>

'on error resume next

dim destURL
dim payload

' TRIED USING THE TIME ZONE ROUTER -> DOES NOT WORK.
'destURL = "https://www.methodintegration.com/method/timezonerouter.aspx?url=https://www.methodintegration.com/MethodWebForms/submit.aspx"

' SO WE'RE USING THIS INSTEAD AND ACCEPTING TIMESTAMPS IN EST
destURL = "https://www.methodintegration.com/MethodWebForms/submit.aspx"

'Construct the Post Data
payload = "oid=xxxxxxxxxxxxxxxxxxxxxxxx" ' note: THE XXXX's here are put here just for my post to Method Forum
payload = payload & "&formName=" & server.URLencode("Web-To-Lead")
payload = payload & "&redUrl=" & server.URLencode("http://")

payload = payload & "&BillAddressAddr3_Step2=" & server.URLencode("101 Some Street")
payload = payload & "&BillAddressCity_Step2=" & server.URLencode("Toronto")
payload = payload & "&BillAddressState_Step2=" & server.URLencode("Ontario")
payload = payload & "&BillAddressPostalCode_Step2=" & server.URLencode("M5N 2T3")
payload = payload & "&BillAddressCountry_Step2=" & server.URLencode("CA")
payload = payload & "&CompanyName_Step2=" & server.URLencode("ACME CORPORATION")
payload = payload & "&FirstName_Step2=" & server.URLencode("John")
payload = payload & "&LastName_Step2=" & server.URLencode("Doe")
payload = payload & "&Email_Step2=" & server.URLencode("john.doe@somedomain.com")
payload = payload & "&Phone_Step2=" & server.URLencode("9051234567")
payload = payload & "&Description_Step3=" & server.URLencode("these are my comments")

'Construct the useragent and send
set http_obj = server.CreateObject("MSXML2.ServerXMLHTTP")
http_obj.Open "POST", destURL , false
http_obj.setRequestHeader "Content-Type", "application/x-www-form-urlencoded"
http_obj.send(payload)

'Grab the response
strResponse = http_obj.ResponseText

set http_obj=nothing

Response.write(strResponse)
Response.end

%>

IT SURE WOULD BE NICE TO GET THIS WORKING :)

CC on outgoing emails prompts new Lead or Opportunity

Roper724 — Mon, 14 Oct 2013 19:14:12 GMT

It has come to my attention from our staff, that anytime they want to COPY (CC) select company stakeholders on outgoing messages within CRM, they are prompted to add these stakeholders as individual Leads or Opportunities, each and every time. Due to the amount of trouble this creates, our staff are electing NOT to copy them at all because of this BUG in CRM. As a result, these people are being excluded from some very important communications.

I have sent Method CRM an email in hopes they will respond but I thought I would try the Forum as well.

Has anyone else run into this problem? If so, have you found a way around it?

Thanks.

Roper724