Search options (Page 106 of 247)

@BraathWaate: Good to rely on core functions like the native get_next_trans_no() in the final fix now committed in my repo.

It is attached herewith.

Each Sales Kit has a separate item_code of it's own in FA. The Sales invoice will only reflect the individual items and not the Sales Kit name. In fact, the item_codes table has some redundancy in the description of the Sales Kit name (see attachment)  that is duplicated for each constituent item in it. This normalisation issue may the cause of it's inability to provide the unique auto numbered item_code to the constituent items of a SalesKit when more than one constituent item exists. As the said table has a separate auto-numbered id field manipulating each entry individually is not hampered when just the id of the record is provided. But when several constituent items are inserted in sequence this will be an issue if the actual item_code is not properly coded into them and the next one is invoked each time.

Wonder which field or what logic distinguishes a SalesKit from a normal item......

@joe: this needs investigation.

Since a different construct was used in sending the email, it may have been possible that the return from the sending routine is different and that return is what needs to be investigated.

Try the fixes in my previous post.

$hide_inaccessible_menu_items is for hiding menu items inside the tabs .
The commenting out of the add_application() is for hiding menu tabs at the top.

The Bank does not care if there is an invoice or not but the Account books do.

The standalone POS's data in an excel sheet needs to be appropriately imported into FA and invoices printed there from.

@BraathWatte/bdika: what a way to "cheat" the system. Needs a pure blooded accountant to wade thru this without getting confused.

I'll now await the outcome.

Refer this post for case sensitivity of the 'SELECT' part of the sql.

Just wiki-ed the presence of the good old secondary repo at http://devel.frontaccounting.com/git/ where some old extensions reside - maybe someone can polish them for use in FA 2.4.x.

Looks like the id's start from 1 each time.

Take a backup from FileZilla before uploading the new files.

Setup -> Backup/Restore will provide the sql backup.
Copying the webroot of FA in FTP mode (or zip the web folder that has the FA code) will save the FA codebase your are using.

The changed files zip is available in the announcement for FA 2.4.2 - see posts #4 and #12.

@itronics, thanks for the reason behind the slight inconvenience of re-submission. When would one want to change the reference the form automatically provides?

The lines 55-67 of includes/references.inc

$refline_placeholders = array(
    'MM' => 'date',
    'YY' => 'date',
    'YYYY' => 'date',
    'UU' => 'user',
     'P' => 'pos',
//     FIXME:  for placeholders below all the code should work, but as the ref length is variable,
//       length specification in placeholder format should be implemented.
//    'C' => 'customer',
//    'B' => 'branch',
//    'S' => 'supplier',
//    'L' => 'location'
);

Hence {UU} is the logged in user.

The method function _parse_next() gets the next formatted reference.