Search options (Page 74 of 97)

The bugfix has been included in 2.2 final.  Invalid reconciliations made due to the bug in 2.2RC can be fixed manually after selecting '00/00/0000' bank statement date. Thank you for the bug report.
Janusz

Which one report was blank?

Try to read and understand previous post once again. Nothing more to be added.

This is set in session variable (see ui_globals.inc). To have this used permanently you have to store it in users or company table.

Janusz

Yes, despite the help you need to make directories writable you should anyway consult your webhosting tech support about the warning with ftp_put. This is definitely not related to FrontAccounting, but it is some problem in webhost ftp administration panel.

Janusz

Credit note is issued when you e.g. return goods to supplier. Something like negative supplier invoice.

Oh, yes I overlooked your previous post.
When access scheme was created we have assumed that minimal access rights (if granted at all) to some module transactions (in this case sales) is reading them all.  This of course depends on company requirements, but in most cases it is enough. Therefore we have not divide access levels more, and all sales transactions inquires are under SA_SALESTRANSVIEW access area.
If you want to have more grained access, you have to read access_levels.txt file in doc directory, where the access levels system is explained, and make needed changes in php code (files customer_inquiry.php and access_levels.inc at least).

Regarding the customer list in sales order entry screen - this should be replaced by customer name on display, and customer id (set on user login) should be used when order is saved. Exact implementation is up to you and depends on design decision how user-customer relation is coded.

Janusz

If you don't know how to do this, ask your administrator to change the access rights to the company/... folder. This have to be writable by www server.

Setup/Create Company option is accessible only for admins of first registered company, so you will have no access to this when logged into another company, but this have nothing to do with your problem with reports.

Please check company/2/pdf_files directory access rights. This should be writable by all.
Janusz

As far as I understand you want to grant access for customers to some part of company database, and give them ability to entry and inquire data related to his customer transactions. If this is your aim,  I have to say some of listed 'activities' cannot be passed to customer without breaking company data veracity:

Place the order - ok
Update the order - ok
Cancel the whole order or partial order -ok, until the order is accepted.
Accept the goods - this should be done on customer side, not in supplier company database. View access to list of orders already sent makes more sense
Send rejected goods back - this should be registered at the moment of real goods receival by company staff.
Make payments - what do you mean? Currently payments are only registered in FA, and this should be done by responsible company officer having access to bank account  data, not the customer for obvious reasons.
Accept payment back for the sent excess, rejected goods - this is done on customer side, not in supplier database

Despite problems described by joe,  the only real activities which could be made accessible for customers for now is sales order entry/edition/query. The rest needs additional implementation.

Janusz

Standard way of dealing with this situation  is just credit invoice issue. We could consider removing the constraint for item quantities being positive, but this could be done only as an option depending on related company setting. So maybe yes, but not in 2.2 final - it's too late for database changes. 

Janusz