Painful task. Adjust the font size to be really small and then name your items really short. Avoid all decimals if possible. Adjust the column widths! Make a copy of the reporting/rep107.php and place it in your company/#/reporting/ folder where # is your company number. Now edit the latter to suit your needs.

Reports cannot ordinarily add records.
Only the Web UI forms can do it like generating a sales invoice or allocating a supplier payment to a purchase invoice.

Provide an example of a report where you get entries generated.

1,778

(6 replies, posted in Setup)

Setup => Company Setup => Use Dimensions => choose 0, 1 or 2 Dimensions. The default in most charts is just 1.

In the Dimensions => Dimension Entry, the start and end dates can be the same as the fiscal year. his is where you will want your divisions to reside in a single dimension Type.

In Items and Inventory => Items, assign each item to  a specific Dimension where desired.

The Wiki is quite explanatory.

If you forget to set the dimension in each entry form correctly, all the Profit and Loss Accounts pertaining to it will appear messed up.

1,779

(6 replies, posted in Setup)

All company information are in the sys_prefs table as records. Dimensions can be used in any classification of profit centres - dated ranges too are accommodated but departments / divisions are the general usage.

The dashboard is now integrated with FA in v2.4.x and the __construct() is implemented in the themes for the constructor. Replace the Exclusive theme files with the ones from the FA24extensions repo and see whether it works.

It is possible that several records can be added to the table for each report especially when select queries are enabled. Generally there are no update / insert SQLs captured during output of standard reports.

Turn on the debug and sql_trail flags in the config.php file.

All Charts of Accounts in the FA24extensions repo have been updated with the new flag ref_no_auto_increase in the sys_prefs table data.

You will need to adjust the font size and column size to fit in clearly and the paper size too can be set in the FrontReport object property while instanciation. All possible sizes are in the switch case statement in the constructor of the FrontReport class from Line 73 onwards in reporting/includes/pdf_report.inc.

1,785

(14 replies, posted in Translations)

Committed.
Includes the missing 25 stings as well (two letter abbreviations retained in English).

1,786

(14 replies, posted in Translations)

@mlance_2: Thanks. I have updated it and included it in Transifex and committed it to the FA24extensions repo. It is about 70% done and is for the latest po file in FA 2.4.4 last updated towards the end of FA 2.4.3.

Any further updates, you can carry out from the attachment. Please note the carriage return and line feed differences (CRLF => LF). Transifex FA24 has the install po as well done about 63% taken from your core translations.

1,787

(20 replies, posted in Items and Inventory)

The $info variable is populated when the api24/src/Inventory.php file got included (see line 65) and the class Inventory was instantiated in api24/index.php in line 73. The latter file calls the function stock_adjustment_add() without any arguments in line 129 where the $info gets populated from $_POST of the Ajax Request. In all of these cases, we see that the $info['type'] and $info['increase'] do not appear in any validation and hence the validations in the api24/inventory.inc file for these elements can be removed as well.

Committed.

Does this satisfy your stock transfer?

1,788

(20 replies, posted in Items and Inventory)

You are right. We need to remove the type and increase parameters. It is documented at the end of api_changes.txt.

Committed.

Verify if any more endpoints are needed to satisfy: ST_LOCTRANSFER / ST_INVADJUST / ST_LOCTRANSFER

1,789

(20 replies, posted in Items and Inventory)

The API extension for FA 2.3.x is here.

The API24 version is attached herewith. Looks like you are using the one from the official / source repos that may not be updated.

The functions you alluded to have since been updated in the FA24extensions repo and attached here.

1,790

(20 replies, posted in Items and Inventory)

Have a look at the API24 in the extensions repo.

Have a look at the Inventory => Add New Item page and view the form field names and see how they relate to the various sql statements above.

1,792

(1 replies, posted in Announcements)

This is indeed a very nice move.
Handing the baton to the next generation developers who have shown their mettle.
Much better than corrupted democracies foisted on one and all!

1,793

(5 replies, posted in Manufactoring)

Check your database name and prefix in the config_db.php file and then check that the said tables exist.

Since there is more than one issue in the topic referred to in @stefan's link, the specific post is here.

1,795

(37 replies, posted in Installation)

Manually create the database and then proceed to create the new company or permit the db user used to create new databases.

Try to explicitly put in:

error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED

What do you mean by "coming blanks"? If you mean that they are the form for entry of data, then you may not have the same files from a single FA version.

Which version of FA are you using and what platform versions are you on (OS/MySQL/PHP)? The latest GitHub FA version is v2.4.4+.

1,798

(9 replies, posted in Setup)

You can upgrade to FA 2.3.26 first and see if this issue is resolved in it. This will also make you ready for moving onto FA 2.4.x later.

Have you tried Quick Entries?

Attached are the changed files from FA 2.3.19 to FA 2.3.26.

Pay attention to the sql/en_US-new.sql and config.default.php file changes and implement those in the latter in your config.php file. Also read each release page in the forum for any other changes / sql data changes.

It would be nice to refresh the Extensions repo with the latest changes as in the FA24extensions repo. Tamil / Hindi translations are yet to be refreshed.

1,800

(9 replies, posted in Modules Add-on's)

The GST / VAT are addressed in the locale translation files.
There are some computational changes you have introduced - in what way do these changes affect the output?