Skip to Main Content
Sage 200 UKI Ideas Portal

Please note the following Sage 200 Ideas Portal Guidelines apply to the use of this portal.

ADD A NEW IDEA

Clear

Ideas

Showing 19

SQL Triggers

I know it is not allowed to be able to use SQL Triggers on the Sage 200 databases but I believe this should be considered
Andrew Siddles over 1 year ago in Database 2 Will not implement

The Nominal Transaction table must have VAT Code/VAT Period ID fields against each NL Posting

When it comes to reconciling VAT Transactions for a submission period Vs Nominal posted transactions, there is no direct link between the two. It will be useful to have each transaction's VAT Code, VAT Type, VAT Period ID stored in Nominal Transac...
Rustum Khedkar almost 2 years ago in Database 0 Idea Accepted - Gauging Support

Allow separate default nominal codes for Bad Debt and Bad Debt Provision

At the moment the system only has on nominal code for writing off the bad debt or bad debt provision. It would be better if there were separate default nominal codes for these.
Sarah Lancaster over 2 years ago in Default Nominal Accounts 0 Idea Accepted - Gauging Support

Prevent duplication of URNs

On very rare occasions you may see duplicate URNs posted to the Sales Ledger due to environmental issues (deadlocks etc), this could possibly be prevented by setting a constraint on the SLPostedCustomerTran URN field field in the database to preve...
Tim Critchley almost 2 years ago in Database 0 Idea Accepted - Gauging Support

Allow access to the SQL back end on Sage 200 Online

Sage are blocking this and it makes fixing problems very time consuming. The Azure platform will allow it.
Guest about 10 years ago in Access To SQL database on Standard 0 Idea Accepted - Gauging Support

Tracking of cross-sell items

Some method (probably an additional field on the SOPOrderReturnLine table) that would enable the tracking of items added via cross-selling on Sales Orders, and Quotations if cross-sell was enabled on there. This would then allow customers to analy...
Steve Brown about 6 years ago in Tracking of Cross Sell Items 0 Idea Accepted - Gauging Support

User correct DateTimeCreated in the database!!!

We create a number of reports in Sage based on data directly from SQL. We use the DateTimeCreated field in a number of tables to provide KPIs and time triggered reports. DateTimeCreated has always been generated from the Server time that SQL is ru...
Guest almost 9 years ago in Database 1 Idea Accepted - Gauging Support

Default Nominal Accounts. Allow quot;Use Specifiedquot; for any default

Allow the option of nbsp;quot;Use Specifiedquot; for any of the default nominal codes, particularly in the Pamp;L section. This would allow Exchange Differences for examplenbsp;to be posted to an account with a Cost Centre / Dept but not the one s...
Guest almost 11 years ago in Default Nominal Accounts 0 Idea Accepted - Gauging Support

default nominal code for exchange differences

For foreign currency customer accounts when you allocate a receipt to an invoice the automatic posting for exchange differences always adopts the default cost centre and department on the customer account. Potentially this means you have to set up...
Jamie Davies almost 6 years ago in Default Nominal Accounts 0 Idea Accepted - Gauging Support

lock the import ledger file transaction process in nominal ledger

sage will allow multiple users to import at same time which can end up in import imbalances (although added together they do balance) the client would like this process to be exclusive to 1 user to prevent this from happening
joanne scott about 4 years ago in Locking 0 Idea Accepted - Gauging Support