While working on setting up a new instance in my DTAP street (A) I have managed to succesfully deploy the application in the new instance. Since it is brand new there is no data available in the new instance. While it is normal that a different instance has different data, I would like to move configuration data (countries, currencies, import definitions, etc) to the new instance.
I have noticed that there is a way to deploy datasets in the deployment street, however I don’t fully comprehend how this works and what my options are.
Does anyone know the proper way of transferring configuration data between DTAP instances?
We consider 2 different kinds of data: Globally know data or “verspreidingsdatasets” that contain things like countries and currencies and connectioncontacttypes that are usefull for almost all applications.
The second kind of data is more specific to you model: Warehouselocations, rightsprofiles or invoicesettings.
The first kind of datasets already exist and you can send them to your new application:
The datasets specific to your model you need to export from your test or config application in your DTAP street. There are datasets that help to export the most common kind of data, but not for all recods types. Par example there is a dataset to export rights (D744).
You import this dataset to your application and you find it in the exportdefinitions and there set up a new datasource to export your own rightsdataset. This new rightsdataset then can be sent to your acceptance and production environments:
We always use datasets (the lower one in Helena’s comment). For this to work, you configure export definitions which can then be exported as datasets which can then be added via this step in the deployment. Some examples which we use are:
In these export definitions you get total control of what tables (incl. nested tables) need to be exported and you are also in control of all the fields. Also it is possible to have advanced import actions which can be congfigured.
Hi Helena, Thanks for the explination, I actually miss in the story how to create a data definition so that you can distribute it across the DTAP instances. For example, a dataset for exporting activity templates, etc. Can you explain to me how to create a dataset and then distribute it via the DTAP instances as mentioned above?
Click on this dataset > Subscriptions > and add your test/dev application to the list.
Then go to your application > Subscriptions > select the dataset you want to install and click on:
A new installation will be added with the type: datasets. Important note: when you already started an application update, the dataset will be added to this installation.
When you have the export in your application you can start preparing it for Otap distribution.
Prepare OTAP Datasets
Go to Exportdefinitions > [Basis][Ind] Export individueel Activiteitsjabloon > [edit]
Set Save to app server to yes
The overview “Export to deployment” will appear
Click on + to create your specific dataset - think about the Naming convention you want to use.
Fill in the Description (fi: Activiteitsjabloon - Opdrachtbevestiging naar klant (Weborder)
Fill in the Filename in Deployment (could be the same as description)
Click on Add new data source.
Safe
Now go to the parameter and click op Generate.
Edit the New Value to make your selection which activity template(s) you want to be part of the dataset.
Once you have your export in Deployment, you can add your Acceptance and Production applications as subscriptions. See Subscribe to a dataset in this article.
