Search options (Page 71 of 247)

FA treats each fixed asset as a single entity for that very same reason - if one is damaged/sold etc.

The FA interface can be made to acquire a set of assets in a single block but get stored as single assets.

It is possible you upgraded your FA which now requires all tables to be InnoDB.

One work around is to convert all tables in the database into MyISAM type from InnoDB - FA 2.4.x should still work fine.
The current stock FA v2.4.x does not use any of the InnoDB features like references and cascades yet.

SELECT CONCAT('ALTER TABLE ', TABLE_SCHEMA, '.', TABLE_NAME,' ENGINE=MyISAM;') 
FROM Information_schema.TABLES WHERE TABLE_SCHEMA = 'DBNAME' AND ENGINE = 'InnoDB' AND TABLE_TYPE = 'BASE TABLE';

Replace your FA database name in 'DBNAME' above and then execute the output sql statements.

Alternatively enable InnoDB engine in your my.cnf or my.ini file and restart the MySQL server:

default-storage-engine=innodb
default-table-type=innodb

The default Sales Invoice in FA does not show the Financial Year. See attachment. If you customised your invoice then you will need (to get your programmer) to make the changes.

Can try to avoid making several changes in the core reports to include the pdf inc file if possible.
Attached is one instance of a function that may no longer be required or one that can be selectively incorporated with if(!function_exists(... at creation time and it's complement at usage time.

Make each land purchase a separate asset if a different seller is involved and / or individual payments are made to different persons. All land particulars can be attached as documents to the transaction and listed summarily in the memo fields accordingly.

Have a cron job clear the tmp folder where the cache gets stored or disable caching in the apache server config.

Refer:
http://bertanguven.com/disable-caching-of-assets-in-apache
https://stackoverflow.com/questions/11532636/how-to-prevent-http-file-caching-in-apache-httpd-mamp
https://gist.github.com/JamieMason/3245483

1. Yes, it can be done.
2. Editing the language translation .po file and compiling it into a .mo file after replacing Vendor with Supplier, etc will do the job.
3. Make a custom invoice of reporting/rep107.php and place it in your company/#/reporting folder for overriding it and adjust the Invoice into three parts - one above the other - within the same A4 page.
4. The themes do not affect the reports or the translations - yes you can make your own theme.
5. No, FA does not have approvals at this time - make your own extension for it.

If you want assistance, post your bounty offer in the Job Offers board.

@nikhunjpatel1222: Do we have different GST slabs for the same item in a single jurisdiction where a TaxGroup for different location based rate will not suffice?

Is @poncho1234's solution sufficient for the Indian GST?

Looking at this from the security point of view, a complete de-branding / re-branding is essential.

Do a Google search for "FrontAccounting 2.4.4 - Login" and it will ferret out all the native FA code based installs. Do that for older (known vulnerable) versions and it might be a security nightmare.

Even if you do what you want to do, make sure there is a flag in the Company Preferences (sys_prefs table) to turn them off without having to wade through the code base. If most will then hide it, the exercise would prove useless.

Popularising FA is best done by word of mouth and through articles / reviews / courses across nations in all languages.

To be truly effective, the Chart of Accounts and Language extensions should be up-to-date and all schemas in synch. Transifex is where I hammer it out.

Also the FA pkg repo should be up-to-date so that the extensions will install correctly and work as desired. In fact, the extension packages were signed for that very purpose.  For now, users are left to manually install from the FA24extensions repo.

Refer the Wiki and see if the Intersection of lowest tax and additive tax slab for customer (destination location) will satisfy it. The Tax Config page too has examples.

Those who have implemented the Indian GST can share their implementations.

GST in India is still evolving and may be totally changed with any change in Government.

Some links to Indian Taxes for Accounting Software are:

https://github.com/anoopmb/FrontAccounting-2.3.26-CORE

https://github.com/Dolibarr/dolibarr/issues/7221

Contact any paid support entity to resolve your issue that will most probably need manual intervention or post a bounty in the Job Offers board.

The document stands delinked from the transaction. Manually delete it physically if it is a permissions issue. It is possible that one may want to link it to another transaction otherwise.

The code for deletion is in lines 145 to 154 in  admin/attachments.php:

if ($Mode == 'Delete')
{
    $row = get_attachment($selected_id);
    $dir =  company_path()."/attachments";
    if (file_exists($dir."/".$row['unique_name']))
        unlink($dir."/".$row['unique_name']);
    delete_attachment($selected_id);    
    display_notification(_("Attachment has been deleted.")); 
    $Mode = 'RESET';
}

The unlink statement clearly is supposed to delete the file.