User Exits
Use at your own risk! Do not use user exits unless they are provided by your implementation partner. Changes can affect the results and are a source of error if used incorrectly.
Overview
User exits allow you to upload and save user-defined SQL-code. This allows you to change analyses to meet specific requirements. They allow you to customize the behavior of the dab AnalyticSuite (SQL). You can maintain several variants in a user exit and switch between them as required.
In the overview you see all Analytic Steps. You can add one or more User Exits for each Analytic Step. If the name of the Analytic Step is black, then a User Exit exists for this Step. If the name is grey, then there is no User Exit.
You can also search for a specific Analytic Step, only show Steps which already have an User Exit or sort the list in alphabetical order (from A to Z and vice versa).
Edit
Select an Analytic Step on the left side. You can create one or more variants for one User Exit. The standard variant is called Default and can also be used.
Click on the Edit button, to enter SQL-code. Afterwards you can either save your adjustments or cancel them.
Upload
In order to upload User Exits, the file must meet two requirements:
- Name: similar to the name of the User Exit
- Extension: .sql (other extensions are not supported)
It is also possible to upload multiple User Exits simultaneously.
With the Upload button, you can select a file from the browser and upload the SQL-code it contains.
If the field doesn't contain any SQL-code before an upload, the SQL-code of the file is written there.
If the field already contains any SQL-code before an upload, the SQL-code from the file and from the field will be compared.
Deletion
The deletion of an User Exit may affect Analytic Groups, if the User Exit is linked there, and therefore can affect active (scheduled) Tasks. The deletion cannot be undone.