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 joe
Hello Sir,
I guess you are referring to an external COA. In the FA core there are 2 COAs, en_US_demo.sql and en_US_new.sql. These 2 COAs only contains two fiscal years, Currently these are 2020 and 2021.
In the next minor release these will be updated to 2021 and 2022.
All the COAs in the Extension repository are maintained by various users and some are probably not updated.
Joe
@Zilvermeeuw,
Thank you for observing this. It has been fixed and committed to stable repo.
/Joe
@boxygen
Thanks for finding this. Fixed and Committed to stable repo.
Joe
@dz,
Thanks for finding this.
This has been fixed and committed to stable repo.
Joe
@boxygen,
Thanks for observing this and fix.
Committed to stable repo.
The fix can be downloaded here and replaced on server.
Joe
Committed to stable repo.
Joe
@Rmendez
I have now implemented the company logo/or name if no logo/ on views, if a checkbox in company setup is marked. I have for a start implemented it in the views you suggested.
I have not yet committed it to stable repo, but will soon. I hope it will be appreciated. It is possible to easily change the content of the header, but I think it should be as small as possible to give space for the subject to be shown.
Joe
Is this the way you want all the Views to look like.
Joe
I've moved this topic to FA Modifications.
I think this will be an options for Company Setup.
Joe
I will look into this asap.
Joe
Yes, now I see it. In this specific case the line was not there. Thanks for observing this.
To retrieve the user unit dec, the function user_qty_dec() is uset, not user_price_dec() 
.
This has now been committed to stable repo. A fixed file can be downloaded here and replaced on your server.
Joe
Strange, I cannot reproduce this. Have tried with 'User Quantity Decimals (-1) and stock with single digit. And tried in PHP 7.1.33 and 8.1. No problems. It works perfectly here. Others having problems?
/Joe
When the 'Protect security settings' is set, the users and the security_roles tables are skipped when restoring. These are the only tables classed as security settings.
@apmuthu
Will you update the Wiki for us. Thank you in advance.
Joe
I cannot reproduce this error. Anybody else?
I have asked Itronics to comment on this. Unfortunately he is very busy with other stuff at present. Hopefully he will enter soon.
Joe
Regarding the upload facility, this is available to all senior members. Just remember to NOT use the quick reply message, but use the 'Post Reply' link instead.
Joe
I have now been looking into this and came to the conclusion that we only add the selection type, Journal Entries.
For reason of backward compatibility, we will not change the 'unsettled transactions'. This will then cause confusing. The 'unsettled transactions' is used in several places now.
Eventually we can change this in a Major update.
The change will be pushed to repo in a while.
Joe
Yes, I can follow your arguments.
Regarding Journal .Entries, you are right. It should be included.
Would you kindly specify the salestypes problem in customer allocations.
Maybe we have the same problems in supplier ledger.
Joe
Hello. I think the meaning of unsettled here is transactions that are due. It has always been set so. Do you want another text, or?
Joe
Work order entry takes the dimensions set on the Created Item. But the Balance Account dimension wasn't stamped. This is fixed and committed to repo.
A fixed file can be downloaded here and replaced in /manufacturing/includes/db.
Joe
@kvvaradha
I hope you are looking at the last committed code from the core.
In the Invoice case we are first testing for $type == ST_SALESINVOICE before the return action (not voiding).
The code works smoothly. And it falls down to post_void_customer_trans with the correct $type and $type_no.
The $type and $type_no are never changed inside the function.
Joe
@kvvaradha
There are no missing breaks. I will explain.
The Customer Payment and the Sales Invoice must fall thru down to post_void_customer_trans($type, $type_no) on line 63 (inside ST_CUSTCREDIT and ST_CUSTDELIVERY.
Joe
Thanks for detecting this.
This has been fixed and committed to stable repo.
A fixed file can be downloaded here.
Joe
FrontAccounting forum → Posts by joe
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.