Search options (Page 239 of 245)

Normally it would not be a problem for me, as I use only the English language. In the case of changeset 3090, it s a replacement of a translate string - that has to be uniformly carried over to all affected files and the empty.po as well.

In the case of 3091, the new strings can come in during an FA release - if it was done at once, then those using non-English languages can also partake of debugging - we need as many eyeballs as possible on the code to get it up to speed. It will also help those translators in getting the strings translated well before the FA release.

Otherwise, such translate string changes should be withheld till the FA release whence it would update the empty.po as well.

A policy on this score would augur well when more than the current couple of committers comes to pass.

What is the other software and what is the sample output format of your sales that you wish to import? Contact the consultants in the Wiki for any custom interface scripts.

Application agnostic CSV import would be nice - templates for each Application to import from.

Lookup Fiscal Years in the Wiki.

If the intention is to keep the changes private, then, it is better to create a separate table for your new fields with a 1:1 relation to the invoice table and keep your changes as an extension. That way, when the base code changes, your extension functionality will be retaianed and extra table(s) fields will not get erased.

Submitting the changes back to the code base is advisable to avoid re-jig of functional code / table(s) at each upgrade.

If there are many lines (yes the order of the lines would matter and a form field in each line would be needed which will take care of it), then we can apportion amounts in any way we choose like loading costs to larger value items or to rounded costs, etc., and possibly with some items not having any shipping costs at all (enter 0 value).

The "N-1" approach was to alleviate the need to manually compute the balance if the total was entered and only one line had the new field blank.

Thanks Joe for fixing it in Mercurial Changeset 3087.

A 4th option to manually apportion the amount!

Fixed in v2.3.12+ Mercurial Changeset 3066 on Sep 17th 2012.

Refer Post 3471 and examples in the Wiki.

synPOS v0.9.3 was the last released version on 2006-11-07.

POSxp looks promising and seems current.

Will check out the REST clients listed. I just wanted to know the way the API would distinguish between similar Select Specific, Edit and Delete URLs since all requestes would come thru the URL parts only. At least the Edit would have a POST array, the Select Specific and Delete requests would be similar.