8

Hi.


Whenever customers go from UAT testing phase to cutover phase they need a new environment PROD and a new configured go-live company without transactions.


Using the MASTER company approach assumes that customers and consultants remember to change master data in MASTER company during UAT testing where they find data errors. Also, there are questionable tools on the dark web where you can delete transactional data tables. In theory smart if you remember to delete all transactions, revert the number series and more.


I suggest that MS help on this matter by making it possible to mark a table and optionally each field as being either:

  • Master Data
  • Document Data
  • Journal Data
  • Transactional Data


And then a feature to either:

  • Copy company and select i.e., MASTER DATA, TRANSACTIONS, DOCUMENTS etc. for the copy from TEST to LIVE. This is ok to have in the same database. This is also useful for testing new features to have a transactional blank but configured company.
  • Delete transactional data feature in a company including resetting the number series (and more) for the TEST company to become a LIVE company.

Would be nice to have something similar on admin center copy database - the features are used here today to stop job queues and delete some settings during copy.


Category: General
STATUS DETAILS
New