Search options (Page 70 of 247)

Read the Fixed Assets Wiki.

Fixed Asset Categories.

For those intending to upgrade from FA v2.4.2 directly to FA v2.4.4, the changed files zip is attached herewith. The FA 2.4.4 post release fixes will have to be added on separately afterwards from previous post. Take note of DB changes in the charts of accounts and those that pertain to fixes in the addon modules apart from the new entries in the config.inc.php (refer config.default.php changes) / sys_prefs table entries.

Place the files from the 2.4.2 to 2.4.3 changed files in a folder. Now overwrite them with the files from the 2.4.3 to 2.4.4 changed files and then take the files from the Post 2.4.4 release changed file set and overwrite as well. Now you will have the complete set of files that are needed to bring your FA v2,4,2 up-to-date with Git Master codebase that you can use to overwrite your FA 2.4.2 install with. Any changes in the standard chart sqls can be ported to each of your companies. Mostly records in the sys_prefs table.

Refer this post.

Post your specifics and the bounty for it and hopefully someone will take it up. Alternatively, learn the ropes.

For those using FA 2.3.x - this will need to be backported.

Looks like this has been so for a couple of months atleast:

Create an SQL for it and then add an icon to one of the listings or make a custom report. May be present in some dashboard widgets.

FA supports sub-ledger concept.

Thanks @PaulShipley.

Apache 2.4 config for https:

<virtualhost *:443>
  ServerName fa24.local
  DocumentRoot "C:\Users\shipl\htdocs\fa24"
  <directory "C:\Users\shipl\htdocs\fa24">
    Options Indexes FollowSymLinks Includes ExecCGI
    AllowOverride All
    Require all granted
    SSLRequireSSL
  </directory>

  Header always set X-Frame-Options SAMEORIGIN

  SSLEngine on
  SSLCertificateFile "C:\Apps\xampp\apache\conf\ssl.crt\fa-selfsigned.crt"
  SSLCertificateKeyFile "C:\Apps\xampp\apache\conf\ssl.key\fa-selfsigned.key"
</virtualhost>

Not that I know of.

A simple php file can be created to interface with your PBX, extract the caller id, lookup FA crm files for the contact's number and extract the customer id and then call up the ledger folio record for the customer using the appropriate FA link with it in the URL. That way a pop up will get triggered when a call is answered (eg., AsteriskPBX). For vTigerCRM, this is done in my vTiger repo on GitHub for interfacing with AsteriskPBX.

CSV / Excel data can be parsed into MySQL.
To make sense of any application working with any db, take a sql backup of the schema, data and then make one transaction of each type in turn taking backups of the data each time and study the differences and you will then discern which table/fields have been affected (insert/update/delete). Then build an ERD from it.