Parameter
Parameters Screen
The Parameters screen allows you to view and configure global and project-specific settings that control how AnalyticsCreator behaves. These parameters define default paths, naming conventions, data loading rules, and technical limits used during development and deployment.
Each parameter includes a description, a default value defined by the system, and an optional custom value that overrides the default for the current project. Changes made here are saved per project and influence how ETL, DWH, and deployment processes are generated.
The grid is divided into the following columns:
| ID | Column | Description |
|---|---|---|
| 1 | Parameter | Lists the internal name of the parameter. Each parameter controls a specific configuration aspect, such as naming, paths, or deployment behavior. |
| 2 | Description | Provides an explanation of the parameter's function and expected values. Many parameters accept Boolean values (0/1), text, or numeric ranges. |
| 3 | Default Value | Displays the system-defined default setting applied when no custom value is specified. Defaults are optimized for standard deployment scenarios. |
| 4 | Custom Value | Specifies an optional user-defined override of the default setting. This can be used to tailor behavior for specific projects or environments. |
Search Criteria: Use the search bar at the top to quickly locate parameters by keyword. This feature filters the parameter list dynamically.
Commonly Used Parameters
Below are examples of frequently used parameters and their purpose:
| Parameter | Description / Usage |
|---|---|
| AC_LOG | Controls the logging level of deployment and processing. Value range: 0 = No log, 1 = Basic log. |
| ATTRIBUTE_DEFAULT_DISPLAY_FOLDER | Defines the default folder where attributes are displayed within BI models. |
| AZURE_BLOB_CONNECTION_STRING | Connection string used when exporting data or metadata to Azure Blob Storage. |
| CSV_MIN_STRING_LENGTH | Specifies the minimum string length for CSV file imports. |
| CSV_SCAN_ROWS | Number of rows to scan when inferring data types from a CSV source (default: 500). |
| DACPAC_MODEL_STORAGE_TYPE | Defines DACPAC model storage type: 0 = File, 1 = Memory. |
| DATAVAULT2_CREATE_HUBS | Specifies whether hubs are automatically created in DataVault2 models (0 = No, 1 = Yes). |
| DEFAULT_CALENDAR_MACRO | Defines the name of the default calendar macro used for date-related transformations. |
| DEPLOYMENT_CREATE_SUBDIRECTORY | Creates a subdirectory for every generated deployment package (0 = No, 1 = Yes). |
| DEPLOYMENT_DO_NOT_DROP_OBJECT_TYPES | Specifies which SQL object types should not be dropped during redeployment (comma-separated list). |
| DESCRIPTION_INHERIT_TABLECOLUMNS | Controls description inheritance from table columns to dependent objects (0 = None, 1 = Always, 2 = Never). |
| DESCRIPTION_PATTERN_CALENDAR_ID | Defines autogenerated naming convention for calendar ID fields (e.g., Date2ID). |
| DESCRIPTION_PATTERN_DATEFROM | Sets naming convention for date-from attributes (e.g., Start of validity period). |
Screen Overview:
Usage Notes
- Parameter changes take effect immediately after saving and are stored within the current project configuration.
- Some parameters are evaluated at generation time (ETL, DACPAC, or script generation), while others affect runtime behavior.
- Hovering over a parameter name displays a tooltip with additional details (when available).
- System parameters cannot be deleted, but custom overrides can be cleared by removing their custom value.
Tip: Always review parameter documentation before modifying default values to ensure consistent deployment behavior across environments.
