Sage 200 - UKI

Today we discovered Sage200CRM will be supported in Sage 200 2017 (there was no confirmed date for depreciating Sage200CRM). Can we have a feature comparison between Sage200CRM and CRM Connector? for example No. Feature Sage200CRM Connector1 Sage2...

Sage 200 v2015 is not going to be end of life for a few years. So when will sage apply the changes to the installer to allow the S200 server component install to work on Windows 10 Pro (v2016 install is fine). As Sage 200 developers we use Virtual...

It seems arbitrary that Issue and Reverse Issue cannot be recorded when a WO has had the full Quantity Required recorded as Completed. Costing for the WO does not seem to be posted until the Works Order is closed. It would be good to provide an op...

When Completing finished goods on a works order that is linked to a Sales Order there is nothing to prevent a user completing the goods to a different warehouse to that of the Sales Order Line. This then causes allocation/despatch errors as the st...

To be able to expand the works order status to show different stages of the process. At the moment there is Entered, Allocated, Part-Allocated, Issued, Part-Issued, Complete and Closed. Would it be possible to add, In-Build or other statuses so at...

When stock is added against a works order costs are not posted to the nominal until the full order is completed. This is problematic because some works orders are large and can span over three weeks. This means that relevant costs are not posted i...

I have been informed that logged issue no 8176 was resolved as cleared because the marketing team have requested the change to prevent the Home Page setting from working the first time a user logs into Sage each day. It use to work on our old vers...

We have a problem where if someone is posting a receipt and SAGE then crashes, multiple receipts are posted under one URN. The net effect of this is the Sales Ledger is out due to the multiple posting however only one transaction is posted to the ...

When a report is exported to csv file in SAGE 2015, bracketed numbers (as defined by the windows regional setting for negative numbers) are not exported as negative. It was correct in SAGE 2010.

Can the functionality of the bulk issue flag be changed so the works order down dates the stock quantity within the stock module for the required for the works order and attributes the costs as expected to the works order, but picking lists, stock...