Best practises for refreshing a test environment from a production environment

Hi !!

When you need to refresh your test environment from your production environment, do you open a ticket at Infor to have this service performed, or do you do it yourself?

If so, what methods do you use?

Do you only deal with M3? or do you include IDM, ION etc.?

I think it could be enriching to share on this topic. What do you think?

Regards

Find more posts tagged with

Comments

Dominique Lagger

Hi Denis

We only copy M3 table data from production to test. We therefore use the Business Engine Data Management > Import from Database function in the M3 Administrations-Tools. We also work with M3 table templates: We don't want to copy all the tables e.g. we don't copy the tables CSYPRF, CSYDPM (CRS945) so that when we print out documents from the test environment, the customers don't get these test emails.

IDM and ION configurations will always be created in the test environment first in order to test it and then we export/copy them to our production environment.

Best Regards

Dominique

Denis MARETTE

Thank you, Dominique, for your FeedBack. That makes sense.

Do you exclude systematically only this 2 tables ?

I know that the BE Data Management excludes some other tables on its side event if they are included in the template.

fosto

Hi Denis,

in addition to the two tables, when I make a Copy CONO, usually I omit the following tables for the area:

scheduling: CSHCAD,CSHCAL,CSHCTL,CSHDAT,CSHFLD,CSHFNC,CSHHED,CSHLIN,CSHPGM

users: CMNUSR,CSYUSR

roles and security: CMNPSU,CMNPUS,CMNROL,CMNRUS (users and roles should be managed by INFOR OS)

software locks: CRLOCK

MBMInitiator: CBMINH,CBMINF,CBMLOG,CBMSTA

Bye

Fabio

adeisenroth

In addition, we exclude CSYPRT (CRS290 printers) and CVERTX (vertex settings for sales tax). We also use BE Data Management import from database.

Dominique Lagger

Hi Denis

We have the following programs/tables that are exluded for the copy:

MNS060	COSDOC
MNS204	COUTSV
MNS205	CSFDEF
MNS216	COSRVI
CRS945	CSYPRF
CRS949	CSYDPM
MNS250	CJBCMD
MNS320	CJBCTL
MNS151	CSYUSR
SHS010	CSHDAT
SHS010	CSHCTL
SHS010	CSHHED
SHS010	CSHLIN
CRS882	MBMTRD
SES400	CMNPSU
SES401	CMNPUS
CRS290	CSYPRT

But this is a "living" list. We want to have a slim test environment (meaning we want to have as less data as possible on there) because in the concierge usage report the test environment also counts to the statistics.

Our CMS300, CSYLOG tracking table is huge (and generates errors in the copy process), I may want to eliminate that table for future copies as well.

Best Regards

Dominique

Thomas Taylor

hi Denis,

On the M3 side, as most have said, there are certain tables we do not copy down either. Our list is very similar to the combinations added below, mainly due to things like unique details for an environment (Security/scheduled jobs/users).

When on premise it was certainly easier to control for us and we had a timed schedule of refreshing environments. A lot of the tables we simply moved to the side and copied back in.

One thing to consider is what else you need...for example, do you need all text tables? In our lower environment(s) we do not need every single detail, so we do not want lot of the text files files. Those can be large in our environment and without them saves time and space. I guess you know but those tables are named xxYTXH tables and then the corresponding Line tables zzYTXL. May not be relevant for you guys but was/is for us.

Same as Dominique for ION and IDM. ION always come up from below environments so we dont copy down again and with IDM, yeah we dont need the documents to be exact.

regards

Tommy

magnus-tallqvist

While on the topic of refreshing test/dev tenants. Please do not forget to reactivate the tables you use in M3 function search after the refresh (via the M3 function search admin page). It is quite common that this is missed and then search can behave very strange....

Denis MARETTE

Thank you for these very interesting additional information.

Denis MARETTE

Thank you for this reminder

David Tollet

Hi @dmarette , also, in case of env refresh, don't forget to purge and reload the datalake tables (use purge function in DataFabric, and intial load by using EVS002MI.Initiate - DTLK=2).

Denis MARETTE

That's another good point. Thanks @David

Copyright © 2025 Infor. All rights reserved.