Search options (Page 46 of 245)

You may want to make a separate comment like entry below the tallied values in a different column so as not to confuse accountants.

Updated Dutch (nl_NL) translations. See Links above.

180 strings left to translate.

Thanks. Wiki-ed it.
Screenshot upload to wiki - settings awaited.

Are you all getting this error in your reports or in the screen display / drilldown view itself?

@joe: Has the BS/PL got their Cr/Dr switched on closure of Fiscal Year?

Should we not check if real_name is blank instead of a single space?

Make a Kit item of your "product and service" sold to your customer.
Since you know all the costs - landed cost - book it all a the price of the product bought from the Supplier.
Do not directly book the Supplier Invoice to the COGS. Do it through the Supplier Account where you can allocate the payments too.

1. Supplier Advance Proforma Invoice.
2. Advance to Supplier: Dr Supplier, Cr Bank
3. Cr - Import, Delivery, Custom Duties, etc,, Cr - Supplier for Direct Goods Cost, Dr. Purchases Expenses for Goods+Costs
4. Take into stock: Cr Supplier, Dr Stocks
5. (Optional) Allocate Payment to Supplier: Dr Supplier, Cr Supplier
6. Make Kit Item of Unit Goods and variable units of Install Service Charges
7. Invoice Kit Item to Customer - Dr Customer, Cr Sales
8. Payment from Customer - Cr Customer, Dr Bank
9. (Optional) Allocate Payment from Customer - Dr Customer, Cr Customer

@joe: anything more standard?

Once the Barcode type and value field are ascertained, you can use TCPDF to generate them as needed.

In the sql/en_US-new.sql standard chart, the fields with the word description in them are defined thus:

# grep description en_US-new.sql | grep -v KEY

  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(60) DEFAULT NULL,
  `reason_description` char(100) NOT NULL DEFAULT '',
  `description` tinytext NOT NULL COMMENT 'usage description',
  `description` tinytext,
  `description` tinytext,
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(200) NOT NULL DEFAULT '',
  `description` varchar(60) NOT NULL,
  `supplier_description` char(50) NOT NULL DEFAULT '',
  `description` tinytext,
  `description` varchar(60) NOT NULL,
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` tinytext,
  `description` varchar(50) DEFAULT NULL,
  `description` varchar(60) NOT NULL DEFAULT '',
  `description` varchar(200) NOT NULL DEFAULT '',
  `long_description` tinytext NOT NULL,
  `description` varchar(200) NOT NULL DEFAULT '',
  `long_description` tinytext NOT NULL,
  `description` tinytext,
  `description` varchar(60) DEFAULT NULL,
  `description` char(50) NOT NULL DEFAULT '',

In FA v2.5 alpha, it may be useful to classify the description field differently and standardize their field length / type uniformly.

In the following files that refer to supplier_description, there is no truncation occurring in the code (except where function text_row() is used):

inventory/purchasing_data.php
inventory/includes/db/items_purchases_db.inc
purchasing/includes/purchasing_db.inc
purchasing/includes/db/po_db.inc
reporting/rep209.php

Hence, a mere increase in field size is sufficient ordinarily.

However, where a form field restricts input size / max width using the function text_row() defined in includes/ui/ui_input.inc, changes in 4th (size) and 5th (max width) arguments will also be needed. This is so only in the first file listed above.

Please try with a windows machine and the latest Firefox. Also post the URL for the right and wrong PDF paths.

Refer my chart repo for any changes from the official package.

There is no data for the 0_security_roles table in it.
Refer my commit.

@joe: can correct it in the official package.

Change settings in browser for PDF viewer to be native viewers or specific programs - Acrobat / SumatraPDF.