Method Community

I am using QB desktop Premier. After a period of time using the program, this happens where every cell of the screen that can be typed in turns black and many button labels are missing.  I then need to exit out and log back in.  This happens on both computers I use QB on.   Has anyone else had this problem?  Is there a way ...

Looking deeper, I can see that the link from InvoiceLine to SalesOrder is there sometimes, but not always. For those I get a QuantityOrdered. However, I have lots of sales orders in Quickbooks that are linked to invoices, but the links are not showing up in Method.

I followed the instructions above to add the Quantity from the SalesOrderLine table (using LinkToSalesOrder that is already there) as QuantityOrdered on the InvoiceLine table. The new field shows up in the report designer, but the value isn't showing up in the report. Suggestions?

The following updates are now live for users of Method New Feature Upgrade QuickBooks Authentication to OAuth2. This will upgrade New Signups and Disconnect/Reconnects to the new QuickBooks Authentication. Regards, Laks

Nevermind. I think I figured it out. I just upgraded my PC to Windows 10 and it worked on another PC still on Windows 7. Method Reporting Designer doesn't work on Windows 10?

I am having the same issue but in my report, I am just adding a new label and changing the alignment. What was the resolution on this problem?

The following updates are now live for users of Method QBO Updates Add and Sync a New field ASTEnabled to check whether a QBO account is AST enabled Bug fix Make Class field visible for QBO Sales Receipt Regards, Laks

Great...thanks Paul!

Hey Blake - the servers were updated with a security patch, and for some reason this seemingly has affected nothing except for that one API endpoint.  We're going to look into it in Monday when everyone is back in the office. But in the meantime we have rolled back the security patch, and will reapply it next week.  In the ...

Hello Blake, Thanks for reaching out. We are currently investigating this issue as to what might have happened to the MethodAPIActionSendEmailV3 endpoint. At this point it looks like the issue is specific to that endpoint.