Looks like we need to make this feature generic to be based on the fiscal year start and end dates.

1,227

(114 replies, posted in Reporting)

FA 2.3.26 release version has the same rep709.php as the v2.3.25 has. Ignoring whitespace changes, the effective diff between the FA 2.3.26 version and FA 2.4.6+ version is attached to experiment with.

The Wiki lists all resources needed and searching the forums would be a start.
FA24extensions Repo
GL Account Groups Post
GL Sub Ledger Post | Alternative Post

Use Sub-Ledger for properties and brokerage main accounts. The Wiki has only skeletal info on this as of now but some Charts in the official pkg repos and in the FA24extensions repo have examples of such usage.

1,230

(114 replies, posted in Reporting)

The official Dutch (nl_NL) Chart has been updated to match the fields and field orders in the FA24extensions repo.

1,231

(82 replies, posted in FA Modifications)

In the 2.5 alpha, make provisions in the db for the bin concept in the warehousing for inventory - long overdue.

1,232

(114 replies, posted in Reporting)

Official Dutch CoA has some infirmities is excess/missing fields as also some other CoAs. In my unofficial FA24extensions repo, I have corrected all of them thus far:
There was no difference between the official nl_NL-default.sql and the one in my unofficial FA24extensions repo except that the lone fiscal year start date has been advanced from 2017 to 2018 and the presence of a missing sys_prefs flag:

('ref_no_auto_increase','setup.company', 'tinyint', 1, '0'),

It has since been updated in my repo to have the corrections for missing fields, not needed fields as well.

Furthermore, there are some differences between the official chart and the one auto-generated from my script.

Official:
INSERT INTO `0_bank_accounts` VALUES
('1010', '2', 'XYZ Bank betaalrekening', '12345678', 'XYZ Bank', 'Adres bank 1\n1234 AB PLAATS BANK', 'EUR', '1', '1', '9040', '0000-00-00 00:00:00', '0', '0'),
('1000', '3', 'Kas', 'N/A', 'N/A', 'N/A', 'EUR', '0', '2', '9040', '0000-00-00 00:00:00', '0', '0'),
('1020', '0', 'XYZ Bank spaarrekening', '12345678', 'XYZ Bank', 'Adres bank 1 \n1234 AB PLAATS BANK', 'EUR', '0', '4', '9040', '0000-00-00 00:00:00', '0', '0');

Generated:
INSERT INTO `0_bank_accounts` (`account_code`,`account_type`,`bank_account_name`,`bank_account_number`,`bank_name`,`bank_address`,`bank_curr_code`,`dflt_curr_act`,`id`,`bank_charge_act`,`last_reconciled_date`,`ending_reconcile_balance`,`inactive`) VALUES
 ('1060', '0', 'Current account', 'N/A', 'N/A', NULL, 'EUR', '1', '1', '5690', '0000-00-00 00:00:00', '0', '0')
,('1065', '3', 'Petty Cash account', 'N/A', 'N/A', NULL, 'EUR', '0', '2', '5690', '0000-00-00 00:00:00', '0', '0');

Similar data changes in chart class, chart_master, etc.

Official audit_trail:   `stamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
Generated audit_trail:  `stamp` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

Official bank_trans:    `bank_trans_type_id` int(10) unsigned DEFAULT NULL,
Generated bank_trans: No such field in FA 2.4

Official bom:  fields parent, component, loc_code are all CHAR fields.
   Redundant:   KEY `parent` (`parent`,`loc_code`),
   PRIMARY KEY (`parent`,`component`,`workcentre_added`,`loc_code`),

Generated bom: The above fields are all VARCHAR
       No KEY:   `parent`
   PRIMARY KEY (`parent`,`loc_code`,`component`,`workcentre_added`),

Official  budget_trans: No memo_ field after `account` field
Generated budget_trans:   `memo_` tinytext NOT NULL,

1,233

(2 replies, posted in Report Bugs here)

Both links in your post above are the same. Try to inspect the code behind the browser display of the link - you might find another link is some js.

It is possible that the email was being spooled if there are many in the range or that the range is not properly made to be ascending (from/to).

Anyone else getting this issue?

1,234

(114 replies, posted in Reporting)

@joe: In the light of discussions here and in the other thread, please set this issue to rest.

1,235

(114 replies, posted in Reporting)

Applying CoA differences between the official one and mine is trivial as it mostly just has schema changes in field ordering. The real issue comes when using the new pattern of document numbering from FA 2.3.x to FA 2.4.x. If your FA 2.4.x has errors on using my CoA but no errors on using the official CoA, then your official CoA schema will need to be compared with mine in a diff tool like WinMerge or directly in a MySQL client like SQLyog.

The FA userbase would be sad to see a longtime user like you go if you do! We are here to do any hand holding as required.

1,236

(2 replies, posted in Report Bugs here)

@anoopmb: good catch. Needs to be corrected in FA 2.3 as well. Where did you have to use this function?

Whether a new field is necessary and whether the function name should be changed accordingly needs to be ascertained.

Note that this function is not used in FA 2.3.26 and in FA 2.4.6 as well and see if it needs to be removed. Neither is it used in any official theme / extension and those in my FA24extensions repo.

@joe: can commit it.

The menus appear very cluttered (when expanded out) for accounting usage. A nice attempt though and maybe the finished version will be better.

Upgrade to FA v2.4.6+ Git Master and hopefully your issue was fixed.

version.php and at the bottom of your FA Web User Interface.

FA version used?

1,241

(1 replies, posted in Setup)

https://www.youtube.com/watch?v=7qW_ReF60aU
https://www.howtoforge.com/one_machine_mysql_replication
https://www.toptal.com/mysql/mysql-master-slave-replication-tutorial
https://www.digitalocean.com/community/tutorials/how-to-set-up-master-slave-replication-in-mysql
https://dba.stackexchange.com/questions/63159/fastest-way-to-create-local-copy-of-live-innodb-mysql-database

1,242

(3 replies, posted in Banking and General Ledger)

As all your data is in ar_EG, what is the account code for your P&L Account? The sys_prefs table shows it as: 9990. There is also such an account in the chart_master table. Why did you have other accounts after the P&L account like:

,('9990','','الربح / الخسارة للعام','23',0)
,('9991','','م. سولار وبنزين السيارات','22',0)
,('9992','','مصروفات نثرية متنوعة','50',0)
,('9994','','محمد سلطان - دائنون','41',0)
,('9995','','م. كهرباء','50',0)
,('9996','','صيانة عقار','50',0)
,('9997','','م. مياة','50',0)
,('9998','9998','غرامات ','50',0)
,('99982','','اغلاق العام','23',0)
,('9999','9999','م كارته ','50',0);

-- Translation

, ('9990', '', 'profit / loss for the year', '23', 0)
, (1999), M. Solar and Benzin Motor, 22, 0)
, ('9992', 'Miscellaneous sundry expenses', '50', 0)
, (9994', '' Mohamed Sultan - creditors', '41', 0)
, ('9995', '', 'M. electricity', '50', 0)
, ('9996', '', 'maintenance of property', '50', 0)
, ('9997', '', 'M. water', '50', 0)
, ('9998', '9998', 'Fines', '50', 0)
, ('99982', '', 'General Fines', '23', 0)
, ('9999', '9999', 'M Karate', '50', 0);

?

You cannot have sub-ledger accounts across different chart classes.

1,243

(3 replies, posted in Banking and General Ledger)

File not visible in BSNL, India

Fork the project on GitHub and commit your changes with notes - good development model. Your changes can also be pulled into the core for sustainable upgradation.

The following sys_prefs parameters:

default_loss_on_asset_disposal_act
depreciation_period

have their length field value in quotes.
Automated systems looking for these gotchas beware.

The text and tinytext fields have " COLLATE utf8_unicode_ci" now.
The table and field ordering should be the same in both en_US-sql and en_US-demo.sql to make for ease of comparison and error detection. Changes between commits should be easily spottable especially in such core files.
It is okay to keep the comment as "--" for now.

It appears that the dashboard_reminders and dashboard_widgets tables are now present in the new en_US-demo.sql file. The comment character is a condensed "#" instead of the multi line "--". This makes it difficult to compare with the en_US-new.sql which has the "--" as it's comments character. Some sys_prefs items are also missing.

1,248

(27 replies, posted in Setup)

Post your bounty and specs on the Job Offers Board.

1,249

(4 replies, posted in Setup)

Contact UK users like:

@dvarsani
@dls
@kerrsmith
@bailey86
@geoffreywalton
@londondaveuk

Here is a list of Extensions for FA 24 from the Official Extensions Repo as on date:

39 Charts
20 Extensions
41 Languages
16 Themes

# Charts

chart_de_AT-general-2.4.1-3.pkg
chart_en_PH-general-2.4.1-4.pkg
chart_en_US-general-2.4.1-4.pkg
chart_en_CA-general-2.4.1-4.pkg
chart_en_GB-general-2.4.1-5.pkg
chart_en_US-4digit-2.4.1-4.pkg
chart_zh_CN-general-2.4.1-4.pkg
chart_de_DE-general-2.4.1-4.pkg
chart_ro_RO-general-2.4.1-4.pkg
chart_sl_SI-general-2.4.1-4.pkg
chart_pl_PL-general-2.4.1-4.pkg
chart_sv_SE-general-2.4.1-4.pkg
chart_nl_NL-general-2.4.1-4.pkg
chart_nb_NO-general-2.4.1-4.pkg
chart_en_ZA-general-2.4.1-4.pkg
chart_en_AU-service-2.4.1-4.pkg
chart_en_IN-general-2.4.1-4.pkg
chart_en_US-5digit-2.4.1-4.pkg
chart_de_CH-5digit-2.4.1-3.pkg
chart_en_US-service-2.4.1-4.pkg
chart_fr_CA-general-2.4.1-4.pkg
chart_en_SG-general-2.4.1-4.pkg
chart_en_FR-general-2.4.1-4.pkg
chart_id_ID-4digit-2.4.1-4.pkg
chart_en_AU-general-2.4.1-4.pkg
chart_zh_HK-general-2.4.1-4.pkg
chart_ar_EG-english-2.4.1-3.pkg
chart_es_ES-general-2.4.1-4.pkg
chart_ka_GE-general-2.4.1-4.pkg
chart_hu_HU-general-2.4.1-4.pkg
chart_en_US-nonprofit-2.4.1-4.pkg
chart_en_US-GAAP-2.4.1-4.pkg
chart_en_US-demo2-2.4.1-4.pkg
chart_ar_EG-GAAP-2.4.1-3.pkg
chart_ar_EG-general-2.4.1-3.pkg
chart_id_ID-general-2.4.1-4.pkg
chart_de_CH-general-2.4.1-3.pkg
chart_da_DK-general-2.4.1-3.pkg
chart_fr_FR-general-2.4.1-4.pkg

# Extensions

import_transactions-2.4.0-5.pkg
repgen-2.4.0-4.pkg
rep_annual_balance_breakdown-2.4.0-4.pkg
rep_check_print-2.4.0-3.pkg
fronthrm-2.4.0-1.pkg
rep_cash_flow_statement-2.4.0-2.pkg
import_paypal-2.4.0-1.pkg
rep_statement_reconcile-2.4.0-1.pkg
import_items-2.4.0-3.pkg
rep_inventory_history-2.4.0-1.pkg
rep_sales_summary-2.4.0-1.pkg
rep_cheque_print-2.4.0-1.pkg
rep_annual_expense_breakdown-2.4.0-2.pkg
auth_ldap-2.4.0-3.pkg
rep_dated_stock-2.4.0-1.pkg
rep_tax_cash_basis-2.4.0-1.pkg
zen_import-2.4.0-4.pkg
import_multijournalentries-2.4.0-3.pkg
requisitions-2.4.0-3.pkg
osc_orders-2.4.0-3.pkg

# Languages

hi_IN-2.4.2-2.pkg
en_ZA-2.4.1-3.pkg
en_US-2.4.1-3.pkg
ka_GE-2.4.1-3.pkg
de_CH-2.4.1-3.pkg
es_NI-2.4.1-3.pkg
pt_BR-2.4.1-3.pkg
es_MX-2.4.1-3.pkg
es_PA-2.4.1-3.pkg
it_IT-2.4.1-3.pkg
id_ID-2.4.1-3.pkg
en_IN-2.4.1-3.pkg
de_DE-2.4.1-3.pkg
es_ES-2.4.1-3.pkg
nl_BE-2.4.1-3.pkg
bg_BG-2.4.1-3.pkg
es_CL-2.4.1-3.pkg
ur_PK-2.4.1-3.pkg
hu_HU-2.4.1-3.pkg
en_NZ-2.4.1-3.pkg
pt_PT-2.4.1-3.pkg
sl_SI-2.4.1-3.pkg
nl_NL-2.4.1-3.pkg
bs_BA-2.4.1-3.pkg
en_AU-2.4.1-3.pkg
es_CO-2.4.1-3.pkg
sv_SE-2.4.1-3.pkg
pl_PL-2.4.1-3.pkg
fr_FR-2.4.1-3.pkg
zh_CN-2.4.1-3.pkg
ru_RU-2.4.1-3.pkg
nb_NO-2.4.1-3.pkg
ro_RO-2.4.1-3.pkg
el_GR-2.4.1-3.pkg
ta_IN-2.4.2-3.pkg
es_AR-2.4.1-3.pkg
ar_EG-2.4.1-3.pkg
da_DK-2.4.1-3.pkg
zh_TW-2.4.2-1.pkg
sq_AL-2.4.1-3.pkg

# Themes

graypink-2.4.0-1.pkg
response-2.4.0-4.pkg
fancy-2.4.0-1.pkg
greyred-2.4.0-1.pkg
thinker-theme-2.4.0-1.pkg
grayblue-2.4.0-1.pkg
exclusive_db-2.4.0-1.pkg
graylime-2.4.0-1.pkg
modern-2.4.0-1.pkg
exclusive-2.4.0-1.pkg
newwave-2.4.0-1.pkg
bluecollar-2.4.0-3.pkg
studio-2.4.0-1.pkg
elegant-2.4.0-2.pkg
anterp-2.4.0-1.pkg
dynamic-2.4.0-3.pkg