Method:Classic General Q&A

Re: Grid Error Message

SMDC_Sam — Wed, 17 Aug 2016 15:03:59 GMT

Yes, I spoke with Shadi this morning and we could not reproduce the problem.

To clarify, I added a custom field to the table, but never placed it on any screen. After changing my mind and removing the new custom field from the table, both the stock and custom screens gave an error message.

Re: Grid Error Message

Method_Ben — Wed, 17 Aug 2016 15:00:00 GMT

Hi There SMDC_Sam,

Looks like you've already spoken to a member of our support team since you initially posted this - But just wanted to follow up and see how things are going.

Firstly - you mention that 'We were initially attempting to add a field for a Purchase Order number to our invoices before we realized that QuickBooks has that field and Method was just not showing it'
Where were you seeing this field? At this time - 'PO' is not a field that is contained on a stock QBO or Method Invoices Table. was it a custom Field perhaps?

Certainly strange that the stock screens broke however! I understand they were working again when our team reached out, but Keep an eye on it and let me know if it breaks again and Ill be happy to take a look.

Thanks SMDC_Sam.

Regads,

Ben

Grid Error Message

SMDC_Sam — Mon, 15 Aug 2016 14:58:27 GMT

Hello all,

We have encountered an odd error with the 'Invoices' grid. We were initially attempting to add a field for a Purchase Order number to our invoices before we realized that QuickBooks has that field and Method was just not showing it (a totally different issue, also very frustrating). We added the field to the table, but never added it to the screen. After realizing the other issue we deleted the field from teh table without ever having added it to the screen/grid. After this the grid displayed an error message (both on our customized screen and the stock version) saying "Invalid column name PO...". The only way we got the grid to display correctly was to re-create the "PO" field that we had created and deleted before.

Has anyone encountered something similar? It's odd enough that a field that was never used in any screens would do this, but the fact that it breaks the stock screen tells me something is wrong. We emailed support and have yet to get a response.