Installing and working with synthetic data in Exchange
- Borja Moro Moreno
About synthetic data
Data set designed to be injected into your domain to provide you with certain data you do not have.
This can have a variety of applications, such as allowing a correct use for another Exchange content for which you lack the necessary data, performing an occasional task you don’t usually perform, preparing for a future work area your unit might get involved with, or as part of a predefined use case to cover a specific situation.
There are some key aspects to consider about Synthetic data that only the owner can configure:
Size: there is a size limit of 10MB for the file that contains the data to be injected.
Type of injection: synthetic data can be injected either as a one-time occasion or continuously. This means that after injecting the last event present in the file, the process will either stop or start injecting once again from the beginning of the file.
Frequency: this is the event injection frequency, which is set by default in one event every second. This frequency can be customized at a minimum of 100 milliseconds.
What permissions do I need?
Apart from the Exchange (manage) permission required to access Exchange and install content, the Synthetic data injections jobs permission is also required to launch/stop synthetic data via Exchange.
Launch, navigate, and stop
In the case of Synthetic data, the button to install them is called Launch. After launch, you can access the data table with the injected data by clicking the Open button. The data table will open in a new browser tab so that you can keep your current session while you work with it.
While the data is being injected, the card thumbnail will display a Running green sign and you can manually finish the process by clicking the Stop synthetic data button at the top right of its card or access the Manage installed content area.
If the injection is not continuous, the Running green sign will disappear after the whole file has been injected. This only means that there is not an ongoing injection process, but the data is still available in the table in question.
Â