Method Community

It's a very minor issue, but perhaps a bug... I've noticed that while most fields on my custom screens (quotes, sales orders, invoices, etc) adhere to the formatting conditions I establish (ie using the "$" prefix, along with only 2 decimal places), the Sales Tax Total is a rebel without a cause. On some screens it displays 3 ...

OK, I agree that seems like a much easier solution!

I've got a grid of Sales Orders, that I'd like to order by descending value of their RefNumber field (aka Sales Order #).  I'd assume that when I order these SOs by descending value, they would organize themselves based on the numeric value of their RefNumber. So the order should be something like 100002, 100001, 100000, 9999, ...

In a few number fields I have, I've modified the format to {0:#}, which I believe indicates that I want just an integer number (without a decimal point) to be displayed. This seems to work for all numbers entered into the field except 0, which causes the field to be left blank in the display. I would like to distinguish between the number 0 ...

When I'm using the "Retrieve Value from Table" action to place information in a field on my screen, I notice that the objects on the screen are referenced by the label, and not the object name (or field name).  So, for example, on the Invoice screen, both the Bill To Address and the Ship To Address sections have fields ...

Ah, it appears to be Google Chrome that has the issues.   Just tried both bugs in Firefox and got different results.

Riiiiight. Time for more caffeine.    Edit: Hell, I didn't even need that function. Just used the "Get left" to grab the first 35 characters of the line, then replaced the value on the screen with that. Two actions per shipping line on each screen, lets my users see the exact char cutoff point without needing popup ...

We ship primarily with UPS, and their Worldship program enforces a maximum line length of 35 characters for all lines except the city name, which is 29 characters. Quickbooks allows more characters than that, and this is an issue since our employees are incapable of self-regulating when it comes to line length. I was hoping to have Method enforce ...

There seems to be some bugs with the max field length for text fields in the "Edit Fields" popup when customizing tables. Since it autoemails you for each time it happens, you've probably recieved 50 emails from my end in the last 10 minutes. Bug 1: If I click on a max field length, don't make any changes, then click on another ...

Wasn't sure if that was how it worked, so good to know. The problem was fixed after I deleted my old "PackingSlipRecordID" dropdown in the lineitem table and created a new one, so I must have messed something up on the original dropdown link. Thanks!