Search options (Page 83 of 247)

The cursor should be in the field which needs the barcode and then it should be scanned into it.

Assume you received the balance, make a GRN for it and then return those that were not delivered and make a debit note for it.

At the moment, you can use the memo field for tracking such info and link them to other tables that will have the relevant data.

As long as the Qty Dec and the Prices/Amount Dec are the same the report is okay.

@joe: The variable $dec is first used in Line 157 but assigned only later at Line 164 and that too as a Quantity Unit's Decimal (get_qty_dec()) and used correctly in the next 3 lines for Quantity values but wrongly in Line 179 for Total Amount. Another variable, say $dec1 should be assigned user_price_dec() much earlier and used for the first and last occurrences of the current $dec. While at it, whitespace on Line 138 can also be removed.

The rep105 should be retained as is and the amount can be optionally added under the "Del Date" field.

@Alaa's implementation is attached herewith.

@joe: should we add this into the Sales Orders Report in the core by placing the amount under the Del Date?

Read the Wiki.

Add Items.
Add Suppliers.
Add Purchase Orders.
Now Print PO Reports.

Yes, Firefox even latest one too is in the same state. All ALT-[Key] combinations just choose the tab menu shortcuts if available and if not, choose the first available matching shortcut for the Key and does not allow cycling through all available matching shortcuts for the same Key.

On logging into FA, we are at the Sales Tab. If we type ALT-P, we go to the next tab, Purchases instead of cycling through the menu items on the current tab:

Invoice Prepaid Orders
Customer Payments
Sales Persons

The solution is to keep the ALT key depressed while repeatedly pressing the menu option Key till the one needed gets highlighted and then release the keys to go to that page.

Read this post.

Packing Slip is the way out.

FA does that automatically when the year gets closed.

It is best to make mobile themes self sufficient instead of tinkering with the FA core. The FA core can abstract hardcoded constructs in it into the theme where pertinent. Some elements will need different widths / font sizes to accommodate strings in other languages.

Swiftkey for Android auto injects emoicons based on context which will not be suitable for FA.

A mobile/responsive theme is available in some forks which have morphed FA considerably making it difficult to keep updating it when the core changes.

Creating additional user roles can be documented in the wiki with intent and purpose explained.

@joe: The viewport can be added if it does not violate strict browser settings.