5,926

(0 replies, posted in FA Modifications)

In connecting FA with other mature projects an effort is being made in Order Management where FA's Dimensions feature is being leveraged in a fork of Web2Project.

The following Web2Project Issue Comment summarises Tight vs. Loose Coupling between applications.

Unrelated: A whole lot of cheat sheets are available at DZone (login necessary to download).

5,927

(2 replies, posted in Accounts Payable)

From which version did you upgrade.

Read the Wiki page of config variables and their functionality.

5,928

(1 replies, posted in Setup)

Please read the Wiki.

How did you create the FrontAccounting Company database user? If it is from phpMyAdmin, then check the user privileges there.

5,930

(45 replies, posted in Modules Add-on's)

SimpleAPI Module Wiki Page has been updated with a full test access script set for remote FA server access.

Check Update/Insert permission availability for MySQL user in company used. Make sure that the

FLUSH PRIVILEGES;

was done after user rights changes are done.

Do not use the Browser Back Button, instead use the Back link on the web page.

Wikiied it!

What OS are you on (MySQL in Linux is case-sensitive)?

How did you do the upgrade?

Did you synch the db schemas correctly?

Check out SimpleAPI for FA in the Wiki.

5,935

(1 replies, posted in FA Modifications)

Yes a sortable listing of Suppliers, Customers, Sales and Purchase Orders will certainly be nice.

Possibly an option to have the reports available for an extra destination "Screen" with links to their view/edit pages would be a simple workaround for now pending full fledged menu items for them.

Move to another less taxed country wink or buy/elect a cheaper govt big_smile.

5,937

(23 replies, posted in Wish List)

@ed10: Double quotes is okay. Two single quotes will be a blank value. The double quotes are to ensure closing the string.

To keep with the coding convention, it can be:

hyperlink_no_params("$path_to_root/sales/inquiry/customer_allocation_inquiry.php?customer_id=", _("Go to Allocation Inquiry"));

Should the hyperlink have some parameter to dictate the customer_id? If not, then we use the blank one like:

hyperlink_no_params("$path_to_root/sales/inquiry/customer_allocation_inquiry.php?customer_id=''", _("Go to Allocation Inquiry"));

The blank parameter expanded with spaces for forum display of the above will be ......customer_id='  ' "

5,938

(23 replies, posted in Wish List)

Thanks Janusz, the  $auto_create_branch switch was missing. Looks like backward compatibility did me in! Updated config.php page on the Wiki to reflect all variables as on date in the English version. Offline PDF version available.

Also corrected some small typos and included extra variable / necessary comments in the config.default.php file and am attaching the diff patch from Mer 3119.

5,939

(22 replies, posted in Accounts Receivable)

Thankyou tclim - very explicitly put. Have referenced this post in the SimpleAPI page on the Wiki.

5,940

(23 replies, posted in Wish List)

Default Branch is created automatically when a new Customer is added, but is not automatically associated with the Customer as yet.

Wikied the rest.

5,941

(23 replies, posted in Wish List)

This kind of workflow can use the SimpleAPI extension to create a single web form which posts directly into FA.

If I understand you correctly, in the QB scenario, you did not have the Customer info in QB to start with and after invoicing as well, you do not have a separate Customer record for each customer - just the invoices with several customer names.

FA can simulate the above using a dummy web / cash customer where the Delivery to can be the real customer and his info. That way you need not add customers for each invoice. Just use the dummy one for all such invoices.

5,942

(0 replies, posted in Installation)

Referring to my creation of new page and edits on 21st Nov, it appears that the user who made the changes is listed as admin instead of apmuthu.

Refer history of pages:

https://frontaccounting.com/fawiki/index.php?n=Help.InventoryValuationReport?action=diff

https://frontaccounting.com/fawiki/index.php?n=Help.ReportsAndAnalysis?action=diff

Has the Wiki db been compromised?

Binary Shift values -  php operator

The last 8 bits (LSB) are reserved for System / Later use and hence the <<8 in almost if not all permissions.

5,944

(7 replies, posted in Reporting)

Thanks Joe.

Setting 2 dec places in Items and Inventory -> Standard Costs did the job. Wikied it.

5,945

(4 replies, posted in Reporting)

Any change in status for printing POS payment receipts onto thermal printers / ejecting cash drawers?

5,946

(23 replies, posted in Wish List)

Even in FA it is just one place and one time for each customer / invoice.
Refer Wiki Pages on Add and manage Customers and Sales Quotation Entry (and then convert to Invoice).

Please state the sequence of operations in FA that you used to achieve your end so that we may check on alternative quick modes to achieve the same to match or better QB.

5,947

(7 replies, posted in Reporting)

Yes I figured that out and filed Bug 1906 since the prices_dec field in the #_users table was not being respected for displaying the Unit Cost in the Inventory Valuation Report (rep301.php) as seen from the attachement in the first post in this topic for one item that has 10 decimals in it's Unit Cost.

5,948

(7 replies, posted in Reporting)

Attempting to fix includes/current_user.inc by replacing Line 310:

function price_decimal_format($number, &$dec)

with

function price_decimal_format($number, $dec)

by omitting the pass by reference, the Unit Cost column now has no decimals.

Even any forced value of $dec in Line 312 does not provide any decimals at all in the above attempted fix.

C.po

What happened on browser?

5,950

(7 replies, posted in Reporting)

FA v2.3.13 Mer 3109

File: reporting/rep301.php lines 148 to 158 place the individual detail entries for the Inventory Valuation Report. The decimal formatting is not respected as the deprecated

&$dec

is used.

Lines 310 - 312 of includes/current_user.inc:

function price_decimal_format($number, &$dec)
{
    $dec = user_price_dec();

clearly do not take in the $dec from the function parameter.

This results in the kind of multi-decimal output in the report snapshot attached.