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 poncho1234
After a little more research it seems the ref # is obtained from customer transaction, choosing the last (greatest) value as the last invoice was voided it selects the voided ref # for the next invoice.
The other work around is to manually increase the ref # for the next invoice, but you have to remember to do it which is not ideal.
From the code:-
File: dimensions\dimension_entry.php
172: if (isset($_POST['delete']))
173: {
174:
175: $cancel_delete = false;
176:
177: // can't delete it there are productions or issues
178: if (dimension_has_payments($selected_id) || dimension_has_deposits($selected_id))
179: {
180: display_error(_("This dimension cannot be deleted because it has already been processed."));
181: set_focus('ref');
182: $cancel_delete = true;
183: }
184:
185: if ($cancel_delete == false)
186: { //ie not cancelled the delete as a result of above tests
187:
188: // delete
189: delete_dimension($selected_id);
190: delete_tag_associations(TAG_DIMENSION,$selected_id, true);
191: meta_forward($_SERVER['PHP_SELF'], "DeletedID=$selected_id");
192: }
193: }
194: So it looks like no you can't...
@apmuthu can you please confirm
I need to export customer transaction details (Name, inv#, date, Tax#, amount, total tax, etc.) in - Sales Order Entry, Direct Delivery, Direct Invoice, Customer Credit Notes etc. to a pre-defined formatted XML file programmatically when they are created.
Do any of the existing modules (API, Import transactions, etc) have similar functionality / can be modified?
TL:dr Where do I start?
Any help or advice will be greatly appreciated.
What happens if you run a report only selecting the dimension 1?
Have you made transactions using this dimension?
After a little research, it seems this change was made for 2.3,
Today version 2.3RC1 of FrontAccounting has been released. This is a release candidate, so we would stress in announce it is not ready for production use, but all users are encouraged to made migration tests on it. Please do not test extensions as they are subject to changes before final 2.3 version. Features added after 2.3beta are emphasized.
If you have already installed preliminary 2.3RC release, please just extract 2.3RC1 tarball to your FrontAccounting directory; no additional maintenance is required. Otherwise follow instructions in bundled update.html file.
News in FrontAccounting 2.3
-----------------------------------
Common
- Allow reuse of references previously used on voided transactions
but I cannot find out why it was changed? there seems to be a couple of posts pre 2.3 where users want change invoice???
Do you know the forum post where this was discussed?
I think the code is the following added to admin\db\voiding_db.inc
109: $Refs->restore_last($type, $type_no);
Please note line number is from 3.1 version... it's line 128 in latest version.
@apmuthu, your solution requires that a new invoice be created, this is not always the case, thanks for the suggestion, but I will stick with credit notes
If you create the following invoices:-
Sys. # Invoice #
1 1
2 2
3 3
4 4
5 5
If you then void transaction # 2 you get the following:-
Sys. # Invoice #
1 1
3 3
4 4
5 5
Which for me gives the correct functionality
However if I void the last transaction - #5 and then create a new invoice you get:-
Sys. # Invoice #
1 1
3 3
4 4
6 5
So ignoring ‘Legalities’ and if you have already printed / issued the invoice there are now two invoices numbered #5 (If this invoice was voided and another created after there would be three invoices #5 and so on)
So:
1. This is not consistent.
2. This could be confusing
3. In Colombia this is illegal (In essence invoicing software must show the same functionality as traditional pre-printed invoices, where an annulled invoice would be written or stamped ‘Annulled’ on all copies)
My current work around is not to void invoices, but issue credit notes.
Incorrect Password
The user and password combination is not valid for the system.
If you are not an authorized user, please contact your system administrator to obtain an account to enable you to use the system.
Try again
You are not in Fiscal Years you are in Closing GL Transactions.
Got to Setup, and then Fiscal Years. Which is the 5th one down on the right when using the default theme.
The account names are from the COA
Have you tried the wiki? Before asking a question in the forum its always best to read the wiki first
Please show your calculations
You need to compile .po to .mo
Poedit - Gettext Translations Editor is free open source and you can get it here https://poedit.net/
Apmuthu also gives some tips here
https://frontaccounting.com/punbb/viewtopic.php?id=5242
Pretty sure he's done a tutorial too, but cannot find it? there's more info in the 'sticky's' for the Translation section
What errors do you get when you enable debug? https://frontaccounting.com/fawiki/inde … Accounting
Most hosting companies allow you to choose the php version?
Change all occurrences of 0_ or 1_ to 2_ or what ever number company you want to restore to...
You need to read about database prefix's
What you remove from one account you have to add it to another account, (and vice versa) thats how double entry accounting works isn't it.
You must have a debit and a credit for each journal entry
You need to change the sale type from including tax to excluding tax
What you have done in effect is 4761.9 (5000-238.1) * 5% +
Hi, I think the problem I had was similar to yours, please read this post https://frontaccounting.com/punbb/viewtopic.php?id=6516
If your on a VM try turning off mod-security to see if it resolves?
Why not call Dim 1 "Mar 2017"
At the moment the extremes seem to be Kuwaiti Dinar (KWD) to the Iranian Rial (IRR) if that works they all will. Not sure if your need extra decimal places
I've also found a problem with bloomberg
Directly accessing:-
https://www.bloomberg.com/quote/GBPCOP:CUR
gives:-
The search for GBPCOP:CUR produced no matches. Try the symbol search.
and
https://www.bloomberg.com/quote/CADCOP:CUR
The search for CADCOP:CUR produced no matches. Try the symbol search.
???????
Whilst:
https://www.bloomberg.com/quote/USDCOP:CUR
gives the exchange rate.
So... does anyone else get the same results as me for the above url's?
If you are then Bloomberg does not give full currency exchange rates, if not there is probably regional restrictions.
For google only:-
File: \gl\includes\db\gl_db_rates.inc
219: if (empty($val) || $val+0 <= 0.00001) {changed to
219: if (empty($val) || $val+0 <= 0.1) {works for all currencies tested before
?????
I created a non ssl directory, still getting same results.
Not sure if relevant; but in network, I'm getting this error in firefox:-
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing
exchange_rates.php:6
Nothing similar in chrome
in ie 10:-
DOM7011: The code on this page disabled back and forward caching. For more information, see: http://go.microsoft.com/fwlink/?LinkID=291337
File: exchange_rates.php
HTML1300: Navigation occurred.
File: exchange_rates.php
HTML1524: Invalid HTML5 DOCTYPE. Consider using the interoperable form "<!DOCTYPE html>".
File: exchange_rates.php, Line: 1, Column: 1
HTML1512: Unmatched end tag.
File: exchange_rates.php, Line: 6, Column: 541
HTML1514: Extra "<body>" tag found. Only one "<body>" tag should exist per document.
File: exchange_rates.php, Line: 7, Column: 1
HTML1423: Malformed start tag. Attributes should be separated by whitespace.
File: exchange_rates.php, Line: 19, Column: 299
HTML1409: Invalid attribute name character. Attribute names should not contain ("),('),(<), or (=).
File: exchange_rates.php, Line: 19, Column: 299
Open ssl would affect all exchange rates? Its working for some, but not for others?
Yes, that sounds good.
Comment: Are 29, 30 & 31 'edge' cases?
FrontAccounting forum → Posts by poncho1234
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.