Search options (Page 1 of 13)

I've pushed my textcart repository on github there

   https://github.com/elax/fa-textcart

The latest version fixes the Purchase order update problemes. However, this version of textcart is meant to work with my fork of FrontAccountting (which includes a few non-compatible features). An up to date version of text compatible with FA 2.3 should be easily doable by uncherry picking what is specific to my FA fork.

The main update from the version you should have is the ability to set cart parameter (like customer, date, reference) etc from the text cart.

I'm happy to answer any question.

Textcart author here,

What do you exactly mean by it doesn't work ?
There is no version specific to work with 2.4.x planned, however I don't think there are fundamental changes between 2.3 and 2.4 which will stop it from working.
I don't use FA 2.4.x but a fork of 2.3.x and I have no plan to upgrade at the moment, therefore I am not planning to upgrade textcart to 2.4. However, I'm happy to provide guindance or help to make it work on 2.4.x

/elax

I think I already made similar comments, but even though Mega menu are the trends, have to click twice to be able to do everything is a deal breaker for me (and my users).

(I use the executive theme with a dashboard and everything related the current APP on the left).

/Elax

Sorry guys, I've been quite busy recently (I'm still) and don't come often on this forum.
Can someone summarize the situation ? I only use 0-VAT for journal entry and payment/deposit
so some bugs in sales or supplier invoices are possible.

/Elax

Are you familiar with git ?
If it's to just to have a look checkout this commit as it is (eventually in another directory).
I don't know if the files have been modified by FA team since i modified them, so I don't know if you can just copy them.
The best would be to merge my branch 2.3.33.

/Elax

What do you mean ?

I pushed my patch there https://github.com/elax/frontaccounting/tree/gl_tax_support. It's based on FA 2.3.17 so might want to rebase it to the current version, however, to see how it looks and what it does, you can just use as it is.

This patch, as well as allowing 0-VAT transaction, allows to modify net amount if needed, and check that EVERY transaction is properly VATed :ie that the total amount of non-tax account, matches the sum of net amount of tax account.

The way is works, is by adding a new column in payment/deposit/journal entry which correspond to net amount.
For non tax account, nothing change (and the cell in the new column is empty). For tax account, you can specify the amount (as before) AND the net amount (or taxable amount). Both values are automatically prefilled depending on the VAT rate and the total of net amount, already entered in the form.

For example, let's say you buy some stationary for £100 (ex VAT).
the first GL line is

Account          | Amount | Net Amount |
Stationanry     | 100.00  |                   |

When you enter the line corresponding to the VAT account, it will be automatically prefilled to 20 and 100 (this can be modified) so you'll end up with
Account          | Amount | Net Amount |
Stationanry     | 100.00  |                   |
VAT 20%         |  20.00  |         100.00|

If you select a 0 VAT account, it will be prefilled with 0, 100.  etc ...

At the moment, it doesn't work with quick entry but only for normal payment/deposit and journal entry.
Modifying the way quick entry work to have a 'net amount' option shouldn't be a problem.
At the moment, when I use 0-VAT quick entry, I just add manualy the 0-VAT line (because the validation tells me that I forgot
to "balance" the VAT) and everything is fine.

Disclaimer: I just pulled on old branch from by repository, so It might not work. If it doesn't just ask me. I use it on production every day and it works well (but I can't push my production branch, because it contains other patches)

/Elax

I think you are trying to solve problems which don't exist. I agree that FA UI could look slightly nicer, but the only feature which is mising is 'responsiveness'. Everything else is a matter of taste.

You are speaking of UI "principles", but the first principle is probably "to make the user happy", the second , minimize the number of clicks. Your solution is adding  1 or 2 clicks to everything, I don't really see how it follows modern UI principles.

Also, the problem of "digging" under 2 or 3 level of submenu, features you don't use often is: you don't remember where they are and struggle to find them each time you need them.

What you proposed already exists, it was called OpenERP, and now Odoo apparently and as you said, you need 4 clicks to create a new customer (or pretty much everything in fact). I chosed FA vs OpenERP for that reason (and also because it was nightmare to find things in OpenERP).

The question is, why would peoble "buy" the new FA over Odoo ?
It's a bit like saying vim modes sucks, let's create a modeless vim to compete with emacs ... There a market for both editors and there is no need for 2 emacs.

In other, Don't fix it, if it ain't broken ...

/Elax

It's easier and more complicated than that.
You can't deduce automatically the net amount from a 0 Vatted transaction, so there is no point to try to do something automatic.
However, if you know the net amount, it's super easy.

The solution is therefore to ask the user (somehow) what is the net amount. What can be automatically is prefill the net amount which is what my patch does. I'll send it to you but I'm really busy at the moment.
Alternatively, you can ask itronics or Joe the patch, I sent it to them a while ago.

/Elax