Method Community

Now checking Windows Firewall.  I think this may be the cause.  Typically a message gets thrown when Windows Firewall is the problem but I suspect the Server 2008 R2 (R2 is a BIG change to 2008), may have some rules that apps aren't expecting to see.

I am having trouble getting the Method Integration Engine to sync from a freshly installed Windows Server 2008 R2 machine. I am using the same QB data file (Enterprise v 11.0) and the status console of the Engine reports that the Company file is open, but I cannot get the Engine to report any further status.  It tends to show "waiting ...

[quote user="rhelmer"]How would I exactly go about customizing the screen to  have multiple ship to's per mentioned above?[/quote] Could you create a different job for your customers?  Each job has a separate ship-to address so you may be able to get around this limitation by creating jobs.  If this doesn't ...

If you need some more information while customizing for Price Level, this post from another thread should help: [quote]Price levels can be classified into two categories (a) fixed (b) per item. When you create a price level (this has to be done in QB btw) it is saved in PriceLevel table in Method. If the price level is a per item price level, ...

[quote user="richard@skoosh"]any ideas?[/quote] Yes, I think there's some confusion on the : character on the customer name.  The : character denotes a job for a customer.  So if Fred Wilson is the customer and the job is for Roofing then it would look like Fred Wilson:Roofing.  What you can't do is use a : in the ...

[quote user="scottaskinosie"]no mater what I try I cant get this to translate over to our CRM site[/quote] Out of the box we do not support price levels as this is a limitation by the QuickBooks SDK.  You would have to customize to bring this functionality over from QuickBooks completely. Here's a quote from another thread on ...

any ideas?

Yeah your right i just spoke with the staff and the took me through the ordering system but we didn't put the colons in, basically we stick the address of the customer in on the form, and then in additional set it as a job of another. e.g. foxtons (an estate agent) is hte job agent (who we are doing it for) then when we go into field ...

Same deal there ""Property:9 Chel Clois Sloane Av SW3 3DL" has a colon in it. It's just taking the raw data that exists for that customer, nothing fancy going on behind the scenes. I bet if you look at this customer's account, you'll see the "Customer Name" in Method is ""Property:9 Chel ...

we have'nt been using colons and hte address is spread over 2 fields another example is   QuickBooks returned an error when adding/modifying a accEntity record. The error was: There was an error when storing "Property:9 Chel Clois Sloane Av SW3 3DL" in the "customer name" field. QuickBooks error ...