Search options (Page 80 of 246)

You cannot get the price and price after tax from the inventory item call.
You need to make a tax call and some other calls - check out the various API constructs as to what will get you what you want. If there is a value in some table's field that is not there in the standard API calls, let us know.

Read the Report Signature heading in the Wiki and the corresponding post.

It currently appears to be coded into these 3 places. In others $rel and the $selector are used. In yet others, the search box context is used.

@joe: What is the intended way of using it?

The latest version is attached herein and complies with changes in the 2017-12-19 core commit for VARLOG_PATH and VARLIB_PATH (the latter is exclusively used herein as per relevant core inclusions).

CHANGELOG

Look at overwritten Lines 109,110 in api24/sales.inc:

$info[$sale_index]['ov_discount'] = $trans['ov_discount'];
$info[$sale_index]['ov_discount'] = $trans['Total'];

The above has been corrected and committed in my repo.

Also the VARLIB commit in the core has not been updated as yet in this module but committed in my repo.

The URLs for sales (TRANS_TYPE = 10 for Sales Invoices) are like:

http://www.example.com/frontac24/modules/api24/sales/<TRANS_TYPE>
http:// www.example.com/frontac24/modules/api24/sales/<TRANS_NO>/<TRANS_TYPE>
http:// www.example.com/frontac24/modules/api24/sales/<TRANS_NO>/<TRANS_TYPE>?page=<PAGE_NO>

Note the order of the attributes in the last 2 URLs above.
The api24/config_api.inc has the constant RESULTS_PER_PAGE defined in it.

Both work okay in my version. For Transaction Number 2 in Transaction Type Sales Invoice (10) the output is:

{
 "ref":"002\/2017"
,"comments":""
,"order_date":"05\/07\/2017"
,"payment":"4"
,"payment_terms":{
    "0":"4"
   ,"terms_indicator":"4"
   ,"1":"Cash Only"
   ,"terms":"Cash Only"
   ,"2":"0"
   ,"days_before_due":"0"
   ,"3":"0"
   ,"day_in_following_month":"0"
   ,"4":"0"
   ,"inactive":"0"
   ,"5":"1"
   ,"cash_sale":"1"
 }
,"due_date":"05\/07\/2017"
,"phone":""
,"cust_ref":""
,"delivery_address":"N\/A"
,"ship_via":"1"
,"deliver_to":"Donald Easter LLC"
,"delivery_date":"05\/07\/2017"
,"location":"DEF"
,"freight_cost":"0"
,"email":""
,"customer_id":"1"
,"branch_id":"1"
,"sales_type":"1"
,"dimension_id":"0"
,"dimension2_id":"0"
,"line_items":
 [
  {
     "id":"6"
    ,"stock_id":"101"
    ,"qty":1
    ,"units":"each"
    ,"price":"300"
    ,"discount":"0"
    ,"description":"iPad Air 2 16GB"
  }
 ]
,"sub_total":300
,"display_total":300
}

@boxygen: The database integrity will be affected as 1 Sales Order is related to 1 or more Customer Deliveries but 1 Customer Delivery  pertains to just 1 Sales Order as the latter has the Cust_Branch defined in it.

@stefan: Sales Order Tracking will then have to be manual on the description / memo fields.

The best way is to make a new Sales Order for another cust_branch and edit / move over the subset of items that need to emanate from that other cust_branch to it and effect delivery from it.

Take a backup.
Enter one such depreciation record.
Take another backup and see what SQL INSERTs/ UPDATEs are needed.
Restore from first backup.
Make SQL statements for all depreciations and then import them into the DB.

A non alphabetical first char being omitted before sorting....
Thanks - hope this helps someone.

There was no difference in FA 2.3.26 - wonder what made this necessary now.

A sales order is specific to a Customer Branch in FA as of now.

Try to upgrade to the latest GitMaster version since there have been several bugfixes since the FA 2.4.3 release version. You can overwrite with the changed files and adjust for the new constants in the config files and small changes in the db data (sys_prefs table).

Check if the customers have any credit bills pending.

A brand new South African Chart of Accounts has been prepared on your request (upload the chart to the sql folder) and added to the FA24extensions repository. Kindly provide feedback.

ZAR Currency - Rand / Cents
VAT 14%
Fiscal Year from 1st March till last day of Feb of next year
1 user: admin
Initial admin password: password

The Chart from the Official repo has some field order and other DDL issues besides having no P&L Account - essentially broken. It is stated to be a 5 digit Chart but in actuality it is a 6 digit one. Hence, if you use it, then be prepared to customise it to work. Otherwise, use the one linked above.