Method Community

Hi Dave, You may have answered your own question. These are custom QuickBooks fields you have created in QuickBooks not Method. Therefore Method must follow the same properties as QuickBooks for these fields. Your alternative is to create custom fields in Method which as you know can have different properties. Hope this helps, Val  

Hi Mike, From the Purchase Order screen in Method if you edit the ‘PurchaseOrderLine’ grid do you see the VAT (sales tax) as an available field/column to add (step 2 of 8)? If it’s there you can customize the screen to use it. If it is not, let us know and we can determine if this is a SDK limitation and get back to you. ...

 Hi Mike, This new feature is now available on our testing environment. Once we do a public publish I'll let you know so you can test it out.

1.  I created 5 new custom fields with data in QB and it synced to Method fine.  2.  Next I changed all 5 data in Methods, and only 1 of the 5 changes synced to QB.  Other 4 ended up in Conflict.      The Conflict message appears to say the Custom Field is not found, but its there. See url ...

I created several new custom fields in QB, and synced to Methods.  Those fields limit the data length to 31 characters.  How can I make that data field length more than 31 characters?  Thanks.

 Hi Mike, I have some good news for you; we have a fix! We've made some changes so from now on the user's language preference, which is built into the browser, will be passed to the report when it runs on the server. That way it would recreate the environment used when designing and previewing in the Report Designer. You can use ...

 Hi Reed, Whether you are the Administrator or not, wouldn't have any bearing on that message. It could be that you are trying to add a customer with the same name.  If you retype the name of the customer in the 'Customer Name' field and click on save then that may cause that message to come up. When you are ...

 Hi Elizabeth, One of developers did some digging and he found that it is one of the Microsoft bugs, which said - Messages may be sent as TNEF with a Winmail.dat attachment if the following conditions are true: You create an adjoining form region on a mail message (IPM.Note). Unfortunately, this is exactly what we are doing ...

 Hey Mike, Our team has looked into this issue and they are not able to reproduce this error, even with the long email address. If you are able to narrow it down to what the root cause was, please post and let us know.  

 Hey Lynn, This is an SDK limitation from Intuit. We are able to read the Price Level data in Method, but if you want to update the Price Levels, you must do it in QB. There is a bit more information in another post that Val has done. http://methodintegration.com/cs/forums/p/141/1988.aspx#1988