Search options (Page 242 of 246)

These are attributes of a product / item - osCommerce, Prestashop and other shopping carts have them.

Here is a simple way to migrate any data into FA, for example:

Import of huge number of Bank Accounts.

1. Take a sql dump (SQL1) of the data only of your existing FA database - no need for the schema. Do this while being logged into FA at the Bank Account data entry form with no other users logged in.

2. Enter one bank account manually into FA.

3. Take another sql dump (SQL2) of the data only of the same database.

4. Now observe the difference between the two SQL dumps - SQL1 and SQL2.

5. Make a set of insert / update statements (SQLsynch) that will simulate the data synch from SQL1 to SQL2.

6. Import the CSV of you bank accounts into some table schema that has all the relevant data for SQLsynch statements.

7. Using SQL statements or Excel CONCATENATE formulae, create a set of SQLsynch statements for the whole set of bank accounts.

8. Execute this newly created SQLsynch statements set in the database.

Viola! If all went well, you've managed to import the whole set of bank accounts into FA!

Now make a php script to acquire the CSV from your source and populate the current version of FA and submit it to the project so that others will benefit from the migratory effort.

SQLyog Ultimate has a data synch wizard that will make the SQLsynch statement generation a breeze.

Based on the value of a config variable say $Advance_Recurring_Invoice = false; in config.default.php or a sys_prefs table value settable in Company Setup (preferable), we choose to have Line 145 in sales/create_recurrent_invoices.php as:

$overdue = date1_greater_date2($today, 
            ((isset($Advance_Recurring_Invoice) &&  $
              AdvanceRecurringInvoice) ? $last_sent : $due_date)) && 
         date1_greater_date2($today, $begin) && 
         date1_greater_date2($end, $today);

This may have to reflect in some reports as well........

May need a check to see if $last_sent exists in the first place.....

Thankyou Andreas. Your work is simply fantastic. PUT may allow encryption, POST may not. If you can get PUT to work, then we can not only ensure standard REST, but also progress with the protocol changes as it occurs.

I am trying to fathom and document the external server side to be able to interact with SimpleAPI.

Maybe another SimpleAccessAPI project would dovetail to interface with FA thru the SimpleAPI extension.

This, I hope will be the basis for a full fledged Open Source POS connector / system that FA currently lacks natively.

Multiple branches maintaining transactions pertaining to their branch only (Dimension / Profit Centre) can synch / post to a central head office FA for consolidation or choose to synch fully every few minutes or in realtime (bandwidth and latency issues) so that all can work locally and yet use all of the same data.

Also compiled (GTk, VB, C++, etc) clients for FA would soon be possible.....

Makes sense. Except that .htaccess files were being maliciously overwritten and the *.inc files got exposed on the browser. Now incorporated the contents of the .htaccess file into the main apache conf file itself and removed the .htaccess file in Debian Squeeze to work as expected.

Thanks. Wikied the info.

Updated the SimpleAPIModule Wiki page with a read example that can be executed from an external server.

SimpleAPI - can synch different FA instances as well - looking at High Availability clusters across data centres and local power outages!

Thanks Joe. Maybe in v2.4, if the said field is not used, it can be removed.

Mercurial Changeset 3084.

Is this fix needed in Line 460 in the current version of the said file purchasing/po_entry_items.php ?

The field ov_discount in the table supp_trans is set to be NOT NULL for good reason - arithmetic cannot be done on NULL values. Hence setting it to 0.0 is correct. If it is not used as stated in the comments, then the field should be removed.

The same field name and NOT NULL state is observed in the debtor_trans table as well. Any similar inserts failing on it?

Check includes/page/header.inc file if any hardcoded changes might be a temporary workaround.