It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by apmuthu
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 
or buy/elect a cheaper govt 
.
@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=' ' "
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.
Thankyou tclim - very explicitly put. Have referenced this post in the SimpleAPI page on the Wiki.
Default Branch is created automatically when a new Customer is added, but is not automatically associated with the Customer as yet.
Wikied the rest.
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.
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.
Thanks Joe.
Setting 2 dec places in Items and Inventory -> Standard Costs did the job. Wikied it.
Any change in status for printing POS payment receipts onto thermal printers / ejecting cash drawers?
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.
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.
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?
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
&$decis 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.
Check the SQL schema diffs between before and after backup/restore
lang\new_language_template\LC_MESSAGES\empty.po
needs to be copied to
lang\C\LC_MESSAGES\C.po
Beware of case sensitivity and all paths are relative to the FA folder in the webroot.
This is probably specific to Win7 installs.
Copy over the empty.po as C.po.
Create a faillog.php file in the webroot.
It is most certainly a permissions issue on the folders.
Which versions of XAMPP / Uniform server are you using?
Refer Forum Post for both the changed file sets (v2.3.12 to v2.3.13 and from v2.3.13 to Mercurial 3109) and overwrite your existing files.
There are no db changes.
Just check the difference between your config.default.php and your config.php file for newer options and update config.php accordingly. Use WinMerge2 for the job if you're on Windows.
Since the release of FA v2.3.13, a few fixes have been made especially those that deal with module installation requiring sql updates. Attached is the Mercurial Build 3131.
Weight can be a unit of the item and it will be shown in the invoice if the price of the item is based on the Weight then it would appear in the Quantity column.
Create a new Currency called Coupon (CPN) and set the exchange rate!
An Access role for the Customer can be adjusted if necessary and a user created and assigned the said role. Placing an order but not being able to edit the order after it has been delivered / invoiced is the need that must be ascertained of role's functionality before trusting it.
Thanks Joe, it would have taken me quite a while fathoming the logic and code hierarchy to set this one right. The fix has come extremely fast!
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.