Search options (Page 66 of 246)

@joe: is it worth adding in this core feature?

The list of changed files is available in an Announcements post from previous version to current one and from current one to bleeding edge master set. Just use those files to overwrite the counterparts in the working fileset one after the other. Take a look at the differences in the en_US-new.sql file between the existing and new versions using a diff tool like WinMerge. Generally there may be minor schema differences (not in your instance) and some extra records / change in defaults especially in the sys_prefs table. Synch with your working tables and chosen Chart of accounts accordingly.

The method you listed will need to migrate your files from the company/# folders as well besides affecting the dependencies - files, tables and security choices - of various addons like languages, themes, extensions, etc.

Not displaying the reference number in such forms and then automatically generating it and populating the appropriate tables with it was discussed but that detracted from the freedom to make any non standard transaction reference by the end user and hence given up.

This happens when two or more transactions of the same type are being created and submitted (by different users or the same user from different browser tabs/windows) either simultaneously or one after the other after all had opened the entry form for creation.

When each instance opens an entry form for record creation, the current accepted dispensation makes the next available reference number as the default value in the form. This will be the same in all such form instances across users / browser instances as long as the last record for the transaction type reference has not changed. When the first one submits the record it is taken without any error. When the second one is submitted, it is  bearing the old "next reference" still and hence is rejected as it had been allotted to the one which was submitted first. Whilst it is possible to allot the real next reference that obtains at the time of submission, it was thought to be best presented to teh end user for choice of reference number instead - it may be implemented in private FA dispensations by allotted the next reference directly though and the code for it has been placed in the forum and possibly in the wiki adn the end user can make a choice.

The best way forward to have made a sys_prefs flag for prompting the enduser for choice of new reference or automatically take on the next available one. Although this affects a plethora of forms, it can be implemented directly in the add method of the relevant class definition.

@joe: If taken into the core with the appropriate default, it will save a few heart stops.

Treat the VAT Office as a supplier/vendor (even though citizens who do not get their taxes worth are entitled to consider them dacoits selling thin air ). Make each VAT claim a supplier's invoice. Make each re-payment from the VAT Office as a Debit Note first and then fulfilled by their re-payment by allocation.

@joe: any SOP for it?

You need to install the it_IT locale in Ubuntu on the console first.

Windows or Linux server?

Try to display the sql after the sql. The where clause addresses the issue of absence of voided entry.

What I meant was for on-the-fly cost estimation. In your case, you would create a separate manufacturing work order and then zero the output and treat it as fulfilled and keep it like a template for future use.

Sales => Customer Payments => make the customer deposit and not through journal.
Then Sales => Allocate Customer Payments or Credit Notes => and allocate what you want to the XYZ invoice.

As long as each tax is named uniquely, they should all be added correctly. What does the UI now show? Make sure that the tax on tax is configured as desired. Maybe you want a Tax Group to be assigned.

Provide sample cost estimation sheet and what fields from it need to go into what fields in the which form in FA.

Unzip the attached file into your <FA_webroot>/lang folder.
Just add a stanza for your language in lang/installed_languages.inc.
Now you are good to go.
Preferences => Italian