Search options (Page 104 of 246)

@Dynamic: It appears that your install / data had some glitches during the upgrade. Try to migrate the data into a fresh install and provide feedback. The latest snapshot works as expected as the screenshots in my earlier post will show. The db too was checked for successful voiding.

@joe: There are many places where such Transaction # display would be useful and can be changed during a more mature release. The bug to be fixed is the clearing out of the Transaction# from the form field after successful voiding.

Your install has the latest FA master snapshot since it was officially last changed only on 13th Oct 2017 as on date.
The sql from my repo would be useful only for subsequent new companies created.

However, the sql file can be used in conjunction with a diff tool like WinMerge to compare the diffs with respect to your existing FA backup sql file and the latter's schema and data fields for inserts be suitably amended to incorporate any changes and then restored into FA. If there are any transactions using the Account Codes like 0xxx, then they will need to be corrected as per the one in my repo if the config file in the default install is to be left alone.

This is specific to UK, Canada and a few other Charts. The devs have yet to find the time to update their official pkg repos and till then FA Consultants can/will prey on unwary newbies who would have unsuspectingly added quite some data to their affected installs making them prime targets to be held to ransom. Re-creating the company and adding in the few transactions all over again may be the easier and advised way for many.

Update your FA 2.4.2 to FA 2.4.2+ by incorporating in the fixes since it's release (See #4 and #12 in the Announcements post for the release).

Only the Standard en_US new and demo CoAs are in the default install. Install your requisite Chart from the official repo and replace the sql/<Chart sql> file from my repo. The UK Chart in the official repo needs a config setting to allow alphanumeric characters in the Account Code whereas the one in my repo has prevented leading zeroes in them and works with the standard config setting.

That is how it should be. We have only voided the PO Delivery and not the PO itself. A PO does not need to be voided, it can be cancelled in it's Edit screen.

Updated.

The diff of your new file added as compared to the stock FA 2.4.2+ master apart from whitespace changes are::

--- sales/includes/ui/sales_order_ui.inc    Sun May 21 21:49:30 2017
+++ sales/includes/ui/sales_order_ui.inc    Sat Oct 21 22:32:51 2017
@@ -236,6 +236,10 @@
         display_note(_("Marked items have insufficient quantities in stock as on day of delivery."), 0, 1, "class='stockmankofg'");
 
     div_end();
+
+        if(list_updated('stock_id')) //added by faisal phuong
+            set_focus('stock_id');
+
 }
 
 // ------------------------------------------------------------------------------
@@ -265,6 +269,9 @@
     else
     {
         customer_list_row(_("Customer:"), 'customer_id', null, false, true, false, true);
+        If (isset($_GET['InvoiceNo']))
+            hidden('InvoiceNo', $_GET['InvoiceNo']); //Added by Faisal for Invoice Edit
+            
 
         if ($order->customer_id != get_post('customer_id', -1))
         {

Install of an extension and activating it for specific companies can be done only from the default company. All other companies can only then enable/disable permissions for it's security sections for appropriate roles for themselves.

There is another issue that appears. When we try to add one more item to a SalesKit, the SalesKit (the one we are adding to) appears in the selection drop down box and we can actually get into a circular binge! If some other SalesKits are chosen then it may be okay and that too only if this current one is not part of the SalesKit we are adding.....This may not really be a problem if the Sales Kit being added to another Sales Kit gets populated by it's constituent items!

If we can replace the primary key id with the stock_id and item_code as a compound primary key in the item_codes table and re-code all the classes and functions to adhere to it, then maybe we can do what you want. It will probably break a few extensions as well!

@joe: good to have.

Actually the Uniqueness for the said couple of fields is enforced by an index. It could have been the compound primary key in which case your need would be satisfied.
FA for the most part has tables with just one single primary key to make it easy to code record manipulations (select, update,delete).

The fields stock_id and item_code are both generally VARCHAR(20 except a few of the former are CHAR(20) in all tables they are part of. The varied definition is probably an error or some index justification.

grep stock_id sql/en_US-new.sql

  `item_code` varchar(20) NOT NULL default '',
 `item_code` varchar(20) NOT NULL,
  `item_code` varchar(20) NOT NULL default '',

grep item_code sql/en_US-new.sql

  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL,
  `stock_id` char(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` char(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` char(20) NOT NULL DEFAULT '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` varchar(20) NOT NULL default '',
  `stock_id` varchar(40) default NULL,
  `stock_id` char(20) NOT NULL default '',

You're right. The field group_no (Sales Group) is part of the #_cust_branch table and hence there can be only one Sales Group for one branch.

This means that you will also need to have a cust_branch filter if you want to make a report Sales Group - wise.

@joe: your take?