In AnalyticsCreator, a galaxy is a logical container for related star schemas. It is used to group stars into a shared business context, which helps organize larger analytical solutions and manage related data mart structures more clear.
Function
Each galaxy acts as a container for related stars.
Access
Galaxies are used to organize larger analytical solutions by grouping related stars into a shared business context.
How to access
Navigation tree
Galaxies → GALAXY → Right-click → Edit
Toolbar
Data mart → Galaxies
Diagram
Not applicable.
Visual element
Not confirmed.
Screen overview
ID
Property
Description
1
Name
The display name of the galaxy
2
Galaxy
Galaxy group to which the star schema belongs
3
Schema
Database schema in which the galaxy resides
4
Order in diagram
Defines the position of the galaxy in the diagram for layout purposes
5
Description
Optional text describing the galaxy's business context or contents
[
{"id":383461199041,"name":"Getting Started","type":"category","path":"/docs/getting-started","breadcrumb":"Getting Started","description":"","searchText":"getting started this section provides the fastest path to understanding how to set up and use analyticscreator. it focuses on how a data warehouse is generated, deployed, and executed based on metadata definitions. if you are new to analyticscreator, start with the quick start guide. it walks through the full workflow from repository creation to data consumption. recommended path quick start guide end-to-end implementation flow from metadata to deployed data warehouse understanding analyticscreator architecture, layers (stg, core, dm), and design principles installation and configuration system setup and environment configuration typical workflow create repository define connectors run data warehouse wizard refine model synchronize database deploy artifacts execute workflows consume data available sections installation system requirements download and installation understanding analyticscreator quick start guide"}
,{"id":383225948363,"name":"Quick Start Guide","type":"section","path":"/docs/getting-started/quick-start-guide","breadcrumb":"Getting Started › Quick Start Guide","description":"","searchText":"getting started quick start guide this quick start guide helps new and trial users understand how to set up, model, and automate a data warehouse using analyticscreator. it follows the actual execution flow of the application, from metadata definition to deployment and execution, and explains how sql-based warehouse structures are generated and processed. the guide assumes: strong sql and etl background familiarity with layered dwh design (stg, core, dm) core concept analyticscreator is a metadata-driven design application that generates sql-based data warehouse structures, transformation logic, and orchestration components. instead of manually implementing etl processes, developers define metadata, which is translated into executable database objects and pipelines. the process follows a generation-driven approach: connect to source systems import metadata (tables, columns, keys, relationships) generate a draft data warehouse model using the wizard refine transformations, keys, and historization generate and deploy sql artifacts and pipelines execute data loading and processing workflows a key architectural element is the persistent staging layer (stg): source data is stored persistently after extraction supports reprocessing without re-reading the source system decouples ingestion from transformation and historization in practice, staging is followed by a second layer where historization is applied before data is transformed into core structures (dimensions and facts). quick start flow the implementation process in analyticscreator follows a defined sequence: create repository initialize a metadata repository (sql server database) that stores all definitions of the data warehouse. create connectors define connections to source systems (e.g. sap, sql server) and enable metadata extraction. import metadata and run wizard automatically read source structures and generate a draft data warehouse model (stg, core, dm). refine the model adjust business keys, surrogate keys, relationships, historization behavior, and transformations. synchronize generate sql objects (tables, views, procedures) and materialize the structure in the target database. deploy generate and deploy deployment packages (dacpac, pipelines, semantic models). execute workflows run generated pipelines (e.g. ssis, azure data factory) to load and process data. consume data use generated data marts and semantic models in reporting tools (e.g. power bi). what this quick start covers create connectors and define relationships (foreign keys, references) import and persist source data in the stg layer understand historization and persistent staging behavior build and refine core transformations (dimensions and facts) define business keys and surrogate keys create data marts (dm layer) and calendar dimensions generate and deploy sql server, pipeline, and analytical model artifacts"}
,{"id":383985776833,"name":"Repository & Metadata Model","type":"subsection","path":"/docs/getting-started/quick-start-guide/repository-metadata-model","breadcrumb":"Getting Started › Quick Start Guide › Repository & Metadata Model","description":"","searchText":"getting started quick start guide repository & metadata model before any connector, transformation, or data warehouse object is created, analyticscreator requires a repository. the repository is a sql server database that stores the complete metadata definition of the data warehouse. all objects defined in analyticscreator—sources, transformations, keys, relationships, deployment settings, and workflows—are stored in this repository. it acts as the central control layer from which all sql code and artifacts are generated. purpose provide a persistent metadata foundation that defines the structure, logic, and behavior of the data warehouse independently of the generated sql artifacts. design principle analyticscreator follows a metadata-driven approach where the repository contains the full definition of the data warehouse model. the repository is not a runtime system; it is a design-time control layer. all generated objects (tables, views, procedures, pipelines) are derived from this metadata. once generated and deployed, these objects can run independently of analyticscreator. key principle: metadata stored in repository → sql and pipelines generated → deployed to target system inputs / outputs inputs repository name and sql server instance initial project configuration outputs sql server database containing metadata structured definitions of: connectors source objects transformations keys and relationships deployment configurations internal mechanics 1. repository creation when a new project is created, analyticscreator initializes a sql server database that serves as the repository. this database contains all metadata required to define the data warehouse. 2. metadata storage each object in analyticscreator is stored as structured metadata. this includes: source definitions (tables, columns, data types) transformation logic historization settings dependencies between objects the repository is fully accessible and can be queried or extended directly if required. 3. central control layer all design changes are written to the repository. no sql objects are created in the target system at this stage. the repository acts as the single source for: code generation deployment packaging dependency resolution 4. separation of design-time and runtime analyticscreator operates purely at design time. the repository defines what will be generated, but execution happens only after deployment in the target environment (sql server, azure, etc.). types / variants local sql server repository (development setup) shared repository (team collaboration) version-controlled repository (via acrepo / json export) example creating a new repository results in a sql server database that contains metadata tables describing the data warehouse model. conceptually: repository (sql server) ├── connectors ├── sources ├── transformations ├── keys / relationships ├── deployment config no stg, core, or dm tables exist yet in the target system. only their definitions are stored. when to use / when not to use use when starting a new data warehouse project managing metadata centrally working in a team with shared definitions do not use as a runtime system the repository does not store business data it is not queried by reporting tools performance & design considerations repository size grows with model complexity, not data volume changes in metadata trigger regeneration, not direct sql changes direct modifications in the target database can be overwritten during synchronization design trade-off: centralized metadata control vs direct sql flexibility integration with other ac features connectors: stored and managed in repository wizard: reads metadata and generates draft models synchronization: converts metadata into sql objects deployment: packages generated artifacts ci/cd: repository can be versioned and exported common pitfalls treating the repository as a data storage layer manually modifying generated sql instead of metadata ignoring repository versioning in team environments mixing multiple environments in a single repository key takeaway the repository is the central metadata store that defines the entire data warehouse and drives all code generation and deployment in analyticscreator."}
,{"id":385512338635,"name":"Synchronize (SQL Generation)","type":"subsection","path":"/docs/getting-started/quick-start-guide/synchronize-sql-generation","breadcrumb":"Getting Started › Quick Start Guide › Synchronize (SQL Generation)","description":"","searchText":"getting started quick start guide synchronize (sql generation) after the model has been refined, the next step is to synchronize the data warehouse. synchronization converts the metadata stored in the repository into physical sql objects in the target database. at this stage, analyticscreator materializes the designed warehouse structure. tables, views, and generated procedures become visible in the sql server database. this is the point where the model moves from design-time metadata to deployable database objects. purpose generate and materialize the physical database structure from the metadata model. design principle synchronization is the controlled transition from metadata definition to sql implementation. the repository remains the source of truth the target database is regenerated or updated from metadata developers do not manually create warehouse objects in the target database. instead, analyticscreator generates them consistently from the repository definitions. inputs / outputs inputs refined metadata model in the repository target database configuration naming conventions and generation settings outputs generated sql server database objects, including: stg tables persistent staging and historization tables core views and tables dm views and tables stored procedures for loading, historization, and persisting internal mechanics 1. metadata evaluation analyticscreator reads the current model definition from the repository and determines which sql objects must be created or updated. 2. object generation based on the metadata, the system generates sql artifacts such as: physical tables for staging and persistent layers views for generated transformations stored procedures for historization and persisting 3. schema materialization the generated structure is applied to the target sql server database. after synchronization, the database contains the warehouse objects defined in the model. 4. dependency-aware generation objects are generated in the required order so that dependent objects can reference upstream objects correctly. 5. re-synchronization behavior if the model changes, synchronization updates the target structure accordingly. this keeps the generated sql database aligned with the repository metadata. types / variants typical synchronized object types import tables historization tables transformation views persisted transformation tables stored procedures generation patterns view-based transformations table-based persisted layers procedure-driven loading and historization example a refined model contains: one source import table one historized customer table one fact transformation one customer dimension after synchronization, the target sql server database contains generated objects such as: stg.customer_import pst.customer_history core.vw_factsales dm.vw_dimcustomer sp_load_customer_import sp_historize_customer the model now exists as physical sql objects, but data is not yet loaded unless execution is triggered separately. when to use / when not to use use when the model has been refined and validated you want to materialize the current warehouse structure you need to inspect or test generated sql objects do not treat synchronization as execution synchronization creates structure, not loaded business data etl or pipeline execution happens later performance & design considerations synchronization affects schema, not data volume frequent changes to metadata can cause repeated structural updates manual database changes outside analyticscreator can be overwritten design trade-off: consistent generated structure vs manual database customization integration with other analyticscreator features repository: remains the source for all generated objects refinement: defines what is materialized persisting: adds generated persisted tables and procedures deployment: packages the synchronized structures for release common pitfalls assuming synchronization loads data editing generated database objects manually synchronizing before validating keys and joins forgetting that metadata, not the target database, is authoritative key takeaway synchronization materializes the metadata model as physical sql objects in the target database, but it does not execute data loading by itself."}
,{"id":385512401134,"name":"Consume Data in Data Marts and Semantic Models","type":"subsection","path":"/docs/getting-started/quick-start-guide/consume-data-in-data-marts-and-semantic-models","breadcrumb":"Getting Started › Quick Start Guide › Consume Data in Data Marts and Semantic Models","description":"","searchText":"getting started quick start guide consume data in data marts and semantic models after workflows have been executed, the data warehouse is populated and ready for consumption. the final step is to access the processed data through data marts and semantic models. analyticscreator generates structures that are optimized for analytical consumption. these include dimensional models and semantic layers that can be directly used by reporting and bi tools. purpose provide structured, query-ready data for analytical tools and reporting use cases. design principle analyticscreator separates data processing from data consumption. stg and core layers handle ingestion and transformation dm and semantic models provide consumption-ready structures consumers should not access staging or intermediate layers directly. inputs / outputs inputs processed core structures generated dm layer (facts and dimensions) deployed semantic model outputs queryable data marts semantic models with defined relationships and measures data available for reporting tools (e.g. power bi) internal mechanics 1. dm layer exposure the dm layer contains consumption-ready structures such as fact and dimension tables or views. these are generated based on the core transformations and are optimized for analytical queries. 2. semantic model generation analyticscreator can generate a semantic model that defines: relationships between facts and dimensions measures and calculated fields hierarchies and aggregation logic 3. data access reporting tools connect to the semantic model or directly to the dm layer. typical access patterns include: directquery or import into bi tools connection to tabular models 4. refresh behavior after workflow execution, the semantic model can be refreshed to reflect updated data. this ensures consistency between the data warehouse and reporting layer. types / variants consumption layers dm tables or views tabular models external bi tool connections access patterns direct query on dm layer semantic model (recommended) hybrid approaches example after execution, the following structures are available: dm.factsales dm.dimcustomer dm.dimproduct a semantic model defines relationships between these tables and exposes measures such as: totalsales = sum(factsales.amount) a reporting tool connects to this model and visualizes sales by customer, product, and time. when to use / when not to use use when data warehouse has been executed and populated users require analytical access to data reporting or dashboarding is required do not use lower layers when accessing stg or core directly for reporting building reports on non-finalized structures performance & design considerations dm layer should be optimized for query performance semantic models reduce complexity for end users pre-aggregations can improve performance for large datasets direct access to core can negatively impact performance and consistency design trade-off: direct access offers flexibility semantic models provide consistency and usability integration with other analyticscreator features core transformations: provide input for dm layer deployment: creates semantic models execution: ensures data is up to date macros and transformations: influence calculated fields and measures common pitfalls querying stg or core layers directly ignoring semantic model design missing refresh after data load overloading dm layer with unnecessary complexity key takeaway the dm layer and semantic model provide consumption-ready data for reporting tools and should be the primary access point for analytical workloads."}
,{"id":385512401131,"name":"Deploy","type":"subsection","path":"/docs/getting-started/quick-start-guide/deploy","breadcrumb":"Getting Started › Quick Start Guide › Deploy","description":"","searchText":"getting started quick start guide deploy after synchronization, the data warehouse structure exists in the target database. the next step is deployment, where analyticscreator generates and distributes deployment artifacts to the selected environment. deployment packages the generated database objects together with orchestration components such as pipelines and analytical models. this allows the data warehouse to be executed and used in a target environment such as sql server, azure or fabric. purpose package and deploy generated database structures, pipelines, and analytical models to a target environment. design principle deployment separates structure generation from environment distribution. synchronization creates the structure deployment distributes and activates it in a target system all deployment artifacts are generated from metadata and can be recreated at any time. inputs / outputs inputs synchronized data warehouse model deployment configuration (target server, database, credentials) selected components (database objects, pipelines, semantic models) outputs deployment package containing: sql scripts or dacpac ssis packages or azure data factory pipelines analytical models (e.g. tabular model for power bi) deployed artifacts in the target environment internal mechanics 1. deployment package creation analyticscreator generates a deployment package that contains all required components for the data warehouse. this includes database objects, pipeline definitions, and optional analytical models. 2. target configuration deployment settings define where the artifacts will be deployed. this includes: sql server or azure environment database name authentication details 3. database deployment the generated database structure is applied to the target system. this may include: creating or updating schemas deploying tables, views, and procedures 4. pipeline generation analyticscreator automatically generates orchestration components: ssis packages for on-premise environments azure data factory pipelines for cloud environments fabric data factory pipelines these pipelines define how data is extracted, transformed, and loaded. 5. analytical model generation if configured, a semantic model is generated and deployed. this includes: dimensions and measures relationships between tables compatibility with reporting tools such as power bi 6. deployment logging the deployment process produces logs that show which objects and components were created or updated. types / variants deployment targets on-premise sql server azure sql database azure synapse or fabric environments pipeline variants ssis packages azure data factory pipelines analytical outputs tabular models for power bi powerbi project other supported analytical engines example a deployment is configured with: target sql server database ssis package generation enabled tabular model generation enabled after deployment: database objects are created in the target database ssis packages are generated and available in a visual studio project a tabular model is deployed and available for power bi at this stage, the system is fully deployed but not yet populated with data. when to use / when not to use use when the model is finalized and synchronized you want to move the data warehouse to a target environment pipelines and analytical models need to be generated do not assume deployment loads data deployment creates structure and pipelines data loading requires execution of pipelines performance & design considerations deployment time depends on model size and number of objects pipeline generation adds orchestration complexity but reduces manual work repeated deployments should be controlled via versioning design trade-off: automated deployment vs manual control of environment-specific configurations integration with other analyticscreator features synchronization: provides the generated structure workflows: define execution order within pipelines ci/cd: deployment packages can be integrated into pipelines repository: remains the source for regeneration common pitfalls deploying without validating the model incorrect connection configuration assuming deployment includes data loading not selecting required pipeline or model components key takeaway deployment packages and distributes the generated data warehouse structure, pipelines, and analytical models to a target environment, but does not execute data loading."}
,{"id":385512338634,"name":"Run Data Warehouse Wizard","type":"subsection","path":"/docs/getting-started/quick-start-guide/run-data-warehouse-wizard","breadcrumb":"Getting Started › Quick Start Guide › Run Data Warehouse Wizard","description":"","searchText":"getting started quick start guide run data warehouse wizard after connectors and metadata are available in the repository, the next step is to generate a draft data warehouse model using the analyticscreator wizard. this is the central step where the system translates metadata into a structured warehouse design. the wizard analyzes imported metadata and automatically creates a full model including staging, historization, and transformation layers. this provides a working baseline that can be refined instead of built manually from scratch. purpose generate a complete draft data warehouse model based on imported metadata, including stg, core, and dm structures. design principle analyticscreator follows a generation-first approach: the full data warehouse model is generated automatically from metadata developers refine and adjust the generated model instead of building it manually the wizard uses structural metadata such as tables, keys, and relationships to infer joins, dimensions, and fact structures. inputs / outputs inputs imported metadata from connectors selected source tables modeling approach (e.g. data vault, dimensional, mixed) optional configuration (naming conventions, defaults) outputs generated data warehouse model including: stg layer (import structures) persistent staging and historization structures core layer (dimensions and facts) dm layer (analytical structures) predefined joins and relationships initial transformation logic internal mechanics 1. metadata analysis the wizard reads all metadata stored in the repository, including tables, columns, and relationships. based on this, it determines how objects are related. 2. model generation analyticscreator generates a complete data warehouse structure. this includes: import tables in the stg layer persistent staging structures with historization core transformations for dimensions and facts dm structures for analytical consumption 3. relationship inference joins between tables are derived automatically based on source relationships. these joins are used to construct fact and dimension transformations. 4. default logic generation the wizard can apply default behaviors such as: including directly and indirectly related tables in facts creating standard transformations generating calendar dimensions 5. visual model creation the result is a fully structured data warehouse diagram that shows all layers and dependencies. at this stage, the model is defined but not yet deployed. types / variants modeling approaches data vault model (hubs, links, satellites) dimensional model (facts and dimensions) mixed approach (data vault foundation with dimensional output) configuration options naming conventions (prefixes, suffixes) default transformations inclusion rules for related tables example a set of source tables is selected: customer orders orderlines products after running the wizard: stg tables are created for each source relationships are detected automatically a fact table is generated based on transaction data dimensions are generated for related entities the resulting model already contains joins, transformation paths, and structural dependencies. when to use / when not to use use when starting a new data warehouse model rapidly generating a baseline structure working with well-defined source metadata do not rely on defaults when business logic is complex or non-standard source relationships are incomplete or incorrect fact and dimension definitions require domain-specific adjustments performance & design considerations the wizard accelerates initial modeling but does not replace design decisions generated joins should be reviewed for correctness and performance fact table scope depends on inclusion settings (direct vs indirect relationships) design trade-off: full automation provides speed manual refinement ensures correctness and performance integration with other analyticscreator features repository: provides metadata input for the wizard transformations: generated and refined after wizard execution synchronization: converts generated model into sql objects deployment: packages generated artifacts common pitfalls assuming the generated model is production-ready without review over-including tables leading to overly complex fact structures ignoring incorrect or missing source relationships not validating generated joins key takeaway the wizard generates a complete data warehouse model from metadata, which is then refined and deployed rather than built manually."}
,{"id":385512401101,"name":"Create Connectors","type":"subsection","path":"/docs/getting-started/quick-start-guide/create-connectors","breadcrumb":"Getting Started › Quick Start Guide › Create Connectors","description":"","searchText":"getting started quick start guide create connectors after initializing the repository, the next step is to define connectors to source systems. connectors provide the technical and structural foundation for importing metadata and generating the data warehouse model. a connector defines how analyticscreator accesses a source system and how metadata (tables, columns, keys, relationships) is retrieved. this metadata is then stored in the repository and used by the data warehouse wizard to generate a draft model. purpose establish access to source systems and import structural metadata required for automated data warehouse generation. design principle analyticscreator separates metadata acquisition from data extraction. metadata (structure) is imported first and stored in the repository data extraction happens later during execution (via pipelines) this means a data warehouse model can be designed and generated without requiring an active connection to the source system at runtime. inputs / outputs inputs connector type (e.g. sql server, sap, metadata connector) connection configuration (server, database, authentication) selected schemas, tables, or metadata source outputs connector definition stored in repository imported metadata: tables and views columns and data types primary keys foreign keys or references (if available) internal mechanics 1. connector definition the connector stores the configuration required to access a source system. this includes connection details and selection of relevant schemas or objects. 2. metadata extraction analyticscreator reads structural metadata from the source system or from a metadata connector. this includes: table structures column definitions key definitions relationships between tables in some cases (e.g. sap or metadata connectors), metadata can be imported without direct access to the operational system. 3. repository persistence all imported metadata is stored in the repository. at this stage: no sql objects are generated no data is extracted no pipelines are executed the system builds a structural model that will later drive code generation. 4. relationship availability if source systems expose foreign keys or references, these are imported and can be reused during modeling. if not, relationships must be defined manually in later steps. types / variants connector types direct database connectors (e.g. sql server) erp connectors (e.g. sap metadata extraction) metadata connectors (predefined structures without live connection) import modes full metadata import selective table import manual definition (if metadata is incomplete) example a connector is created for a sql server database containing the following tables: customer orders orderlines the system imports: column definitions (e.g. customerid, orderid) primary keys foreign key relationships (e.g. orders → customer) these definitions are stored in the repository and become available for automated model generation in the next step. when to use / when not to use use when starting a new data warehouse model importing metadata from source systems preparing for automated model generation do not rely on connectors alone when source metadata is incomplete or inconsistent business relationships differ from technical relationships required structures are not exposed in the source system performance & design considerations connector scope directly affects model complexity importing unnecessary tables increases modeling overhead metadata quality determines quality of generated model design trade-off: broad import (high coverage, more noise) selective import (cleaner model, more manual work later) integration with other analyticscreator features repository: stores connector and metadata definitions wizard: uses imported metadata to generate draft model stg generation: based on imported source structures transformations: reuse source metadata and relationships common pitfalls importing entire source systems without filtering assuming source relationships are suitable for analytical models using technical keys as business keys without validation skipping metadata validation before running the wizard key takeaway connectors import and persist source metadata in the repository, forming the structural basis for automated data warehouse generation."}
,{"id":385512401133,"name":"Execute Workflows (Load Data)","type":"subsection","path":"/docs/getting-started/quick-start-guide/execute-workflows-load-data","breadcrumb":"Getting Started › Quick Start Guide › Execute Workflows (Load Data)","description":"","searchText":"getting started quick start guide execute workflows (load data) after deployment, the data warehouse structure, pipelines, and analytical models exist in the target environment, but no business data has been loaded yet. the next step is to execute the generated workflows. workflow execution runs the generated load processes in the correct order. this is the stage where source data is extracted, written to staging, historized where required, transformed into core structures, and exposed through data marts and analytical models. purpose execute the generated loading and processing workflows so that the deployed data warehouse is populated with data. design principle analyticscreator separates execution from generation. generation defines structure and logic execution runs the actual data movement and processing this separation makes it possible to validate and deploy a model before loading any business data. inputs / outputs inputs deployed database objects generated workflows or pipeline packages configured source connections and linked services execution parameters and scheduling context outputs loaded stg tables historized persistent staging tables processed core structures updated dm structures refreshed analytical model content internal mechanics 1. workflow start execution begins by starting the generated workflow package or pipeline. this acts as the orchestration entry point for the full load process. 2. source extraction data is read from the configured source systems and written into the stg layer. import mappings, filters, and variables defined in the model are applied during this step. 3. persistent staging and historization after import, the data is written into the persistent staging layer. if historization is enabled, valid-from and valid-to handling or other configured historization logic is executed here. 4. core processing generated transformations are processed in dependency order. facts, dimensions, and other core structures are built from the persisted source data. 5. dm and semantic model refresh after core processing, the dm layer and the generated semantic model can be refreshed so that reporting tools can consume the updated data. 6. dependency handling the execution order is controlled by the generated workflow logic. upstream objects are processed before downstream objects so that dependencies are resolved automatically. types / variants execution variants ssis-based execution azure data factory pipeline execution manual execution for testing scheduled execution in production loading patterns full load incremental load historized load example a deployed workflow package contains the following sequence: load source table into stg.customer_import apply historization into pst.customer_history refresh fact and dimension transformations refresh the semantic model used by power bi at the end of execution: source data is available in staging historical versions are stored where configured reporting tools can access current analytical data when to use / when not to use use when the deployment has completed successfully source connections are configured correctly you want to populate or refresh the data warehouse do not execute before validating linked services and source access reviewing load filters and parameters confirming that required objects have been deployed performance & design considerations execution time depends on data volume, transformation complexity, and load pattern persistent staging supports reprocessing without re-reading source systems incremental loading reduces runtime but requires correct filter logic historization increases write volume and storage requirements design trade-off: full reloads are simpler to validate incremental and historized loads scale better but require stricter design control integration with other analyticscreator features connectors: provide source access used during execution stg and historization: form the first processing layers workflows: define orchestration and dependency order deployment: provides the executable packages and pipelines semantic models: can be refreshed after successful load common pitfalls assuming deployment already loaded data running workflows without validating linked services using incorrect filter logic for incremental loads ignoring dependency order in manually triggered runs confusing source staging with final analytical output key takeaway workflow execution is the step where deployed structures are populated with data and processed into usable analytical output."}
,{"id":385512401114,"name":"Refine the Model","type":"subsection","path":"/docs/getting-started/quick-start-guide/refine-the-model","breadcrumb":"Getting Started › Quick Start Guide › Refine the Model","description":"","searchText":"getting started quick start guide refine the model after generating the draft model with the wizard, the next step is to refine and adjust the data warehouse structure. the generated model provides a complete baseline, but it must be validated and adapted to match business logic, data quality, and performance requirements. this step focuses on defining keys, adjusting transformations, handling historization, and ensuring that the generated joins and structures reflect the intended analytical model. purpose validate and adjust the generated data warehouse model to ensure correct business logic, data relationships, and performance behavior. design principle analyticscreator generates a structurally complete model, but correctness is achieved through refinement. automation provides the structure manual refinement ensures semantic accuracy developers work on metadata definitions, not directly on sql, and all changes are reflected in generated code during synchronization. inputs / outputs inputs generated draft model (stg, core, dm) source metadata and relationships business requirements and logic outputs refined transformations defined business keys and surrogate keys adjusted joins and relationships configured historization behavior internal mechanics 1. column selection and cleanup generated transformations often include all available columns. unnecessary attributes should be removed to reduce model complexity and improve performance. 2. business key definition business keys must be validated or defined explicitly. these keys determine: uniqueness of entities join conditions between tables basis for historization 3. surrogate key generation analyticscreator generates surrogate keys automatically. depending on the modeling approach: identity-based keys (e.g. integer) hash-based keys (for data vault or hybrid models) hash keys are typically generated in the staging layer as calculated and persisted columns. 4. relationship validation automatically generated joins should be reviewed. this includes: correct join paths cardinality assumptions inclusion of required tables 5. historization configuration historization is applied in persistent staging and core layers. typical behavior includes: valid-from and valid-to columns tracking changes over time the historization strategy should be verified for correctness and performance impact. 6. macro usage reusable sql logic is implemented using macros. for example: hash key generation standard transformations macros allow centralized control of repeated logic without modifying generated sql directly. 7. dimension and fact adjustments fact tables and dimensions generated by the wizard should be refined: remove unnecessary joins add required attributes ensure correct grain of fact tables 8. calendar and date handling date columns should typically be replaced by references to a calendar dimension. this is often done using predefined macros. types / variants key strategies business keys only surrogate keys (identity) hash-based keys historization strategies scd2 (valid-from / valid-to) snapshot-based access current-state only transformation styles fully generated adjusted via metadata extended with custom sql logic example a generated fact table includes all columns from multiple related tables. refinement steps: remove unnecessary attributes validate join between orders and customers define surrogate key for dimension tables replace date columns with calendar dimension references example adjustment: -- before refinement select * from stg_orders o join stg_customer c on o.customer_id = c.customer_id; -- after refinement (conceptual) select o.order_id, c.customer_key, o.order_date_key, o.amount from core_orders o join dim_customer c on o.customer_key = c.customer_key; when to use / when not to use use when after running the wizard validating generated model structures aligning model with business logic do not skip when working with complex source systems data quality issues exist performance requirements are strict performance & design considerations reducing column count improves performance incorrect joins can cause data duplication historization increases storage and processing cost hash keys improve scalability but add computation overhead design trade-off: automation speed vs model accuracy flexibility vs standardization integration with other analyticscreator features wizard: provides initial model macros: define reusable sql logic synchronization: generates sql from refined metadata deployment: uses finalized model for artifact creation common pitfalls leaving generated joins unvalidated using incorrect business keys overloading fact tables with unnecessary attributes ignoring historization impact on performance mixing business logic directly into sql instead of metadata key takeaway the generated model must be refined to ensure correct business logic, keys, and performance before sql generation and deployment."}
,{"id":383225948362,"name":"Understanding AnalyticsCreator","type":"section","path":"/docs/getting-started/understanding-analytics-creator","breadcrumb":"Getting Started › Understanding AnalyticsCreator","description":"","searchText":"getting started understanding analyticscreator analyticscreator is a metadata-driven design application for building and automating data warehouses and analytical models. instead of manually implementing etl and sql logic, developers define metadata such as sources, keys, relationships, transformations, and loading behavior. analyticscreator uses these definitions to generate database objects, pipelines, and semantic models. how analyticscreator works the workflow in analyticscreator starts with a repository, continues with source metadata import, and then uses a wizard to generate a draft data warehouse model. that model is refined, synchronized into sql objects, deployed to the target environment, and finally executed through generated workflows or pipelines. create a repository define or import connectors import source metadata run the data warehouse wizard refine the generated model synchronize the structure deploy artifacts execute workflows consume data through data marts and semantic models repository and metadata every analyticscreator project is based on a repository. the repository is a sql server database that stores the full metadata definition of the data warehouse. this includes connectors, source objects, transformations, keys, relationships, deployment settings, and other object definitions. the repository is the design-time control layer and the source for all generated artifacts. this means the target database is not modeled manually. instead, analyticscreator reads the repository metadata and generates the required sql structures from it. generated code can run independently after deployment because analyticscreator is used as a design-time application, not as a runtime dependency. connectors and metadata import analyticscreator connects to source systems such as sql server or sap and imports structural metadata including tables, columns, keys, and references. in some scenarios, metadata can also be imported through metadata connectors, which makes it possible to model a data warehouse without an active connection to the live source system during design. imported metadata is stored in the repository and later used by the wizard to generate the draft warehouse model. at this stage, no warehouse data has been loaded yet. only structure and metadata are being captured. the wizard the data warehouse wizard is the central acceleration mechanism in analyticscreator. it analyzes source metadata and generates a draft warehouse model automatically. depending on the selected approach, this can be a dimensional model, a data vault model, or a mixed approach. the wizard can create staging structures, historization layers, dimensions, facts, calendar dimensions, and default relationships based on detected metadata. the generated model is not the end result. it is the baseline that developers refine and validate. the main engineering work happens after generation, when keys, joins, historization behavior, measures, and transformations are adjusted to fit the intended warehouse design. warehouse layers analyticscreator supports a layered warehouse architecture from source to presentation. in a typical setup, this includes source objects, staging, persistent staging or historization, core transformations, data marts, and semantic or reporting layers. it can also generate analytical models for tools such as power bi. persistent staging a key architectural concept is the persistent staging layer. source data is first imported into staging structures and then stored persistently for further processing. this persistent layer is used for historization and for decoupling source extraction from downstream transformations. it allows data to be reprocessed without repeatedly reading the source system. in dimensional scenarios, historized tables typically include surrogate keys together with valid-from and valid-to columns. in data vault and hybrid scenarios, additional hash-based keys and references can be generated in the staging layer as persisted calculated columns and then reused in later layers. transformations transformations in analyticscreator are usually generated as sql views based on metadata definitions. these definitions specify source tables, joins, selected columns, macros, and transformation rules. in many cases, the default generated view logic is sufficient as a starting point, but it can be refined through metadata rather than by rewriting generated sql directly. analyticscreator also supports reusable macros for standard sql logic, such as date-to-calendar-key conversion or hash key generation. this allows repeated logic to be defined once and reused consistently across the model. synchronization, deployment, and execution these three steps are related but different and should not be confused. synchronization synchronization materializes the metadata model into sql objects in the target database. this creates the database structure defined in analyticscreator, such as tables, views, and procedures. it does not mean that business data has already been loaded. :contentreference[oaicite:13]{index=13} deployment deployment creates and distributes deployable artifacts for the selected target environment. these can include sql database packages, ssis packages, azure data factory pipelines, and semantic models. deployment prepares the environment but still does not imply that source data has already been processed. execution execution runs the generated workflows and pipelines. this is the step where source data is actually extracted, written to staging, historized where required, transformed into core structures, and exposed through data marts and semantic models. in azure scenarios, this may happen through azure data factory. in on-premise scenarios, this may happen through ssis. consumption after execution, the data warehouse can be consumed through data marts and semantic models. these structures are intended for reporting and analytics, while lower layers such as staging and historization should remain implementation layers rather than direct reporting interfaces. analyticscreator can generate tabular models and structures for tools such as power bi. design implications the repository is the source of truth metadata drives generation, not manual sql-first development the wizard creates a baseline, not a final production model persistent staging is part of the architecture, not just a temporary landing area synchronization, deployment, and execution are separate steps consumption should happen from data marts or semantic models, not from staging layers key takeaway analyticscreator works by storing warehouse definitions as metadata, generating sql and orchestration artifacts from that metadata, and then deploying and executing those artifacts in the target environment."}
,{"id":383225948358,"name":"Installation","type":"section","path":"/docs/getting-started/installation","breadcrumb":"Getting Started › Installation","description":"","searchText":"getting started installation installing analyticscreator: 32-bit and 64-bit versions this guide offers step-by-step instructions for installing either the 32-bit or 64-bit version of analyticscreator, depending on your system requirements. ⓘ note: to ensure optimal performance, verify that your system meets the following prerequisites before installation."}
,{"id":383225948359,"name":"System Requirements","type":"section","path":"/docs/getting-started/system-requirements","breadcrumb":"Getting Started › System Requirements","description":"","searchText":"getting started system requirements to ensure optimal performance, verify that the following requirements are met: ⓘ note: if you already have sql server installed and accessible, you can proceed directly to the launching analyticscreator section. networking: communication over port 443 is where analytics communicates to the analyticscreator server. operating system: windows 10 or later. analyticscreator is compatible with windows operating systems starting from version 10. ⓘ warning: port 443 is the standard https port for secured transactions. it is used for data transfers and ensures that data exchanged between a web browser and websites remains encrypted and protected from unauthorized access. microsoft sql server: sql server on azure virtual machines azure sql managed instances"}
,{"id":383225948360,"name":"Download and Installation","type":"section","path":"/docs/getting-started/download-and-installation","breadcrumb":"Getting Started › Download and Installation","description":"","searchText":"getting started download and installation access the download page navigate to the analyticscreator download page download the installer locate and download the installation file. verify sql server connectivity before proceeding with the installation, confirm that you can connect to your sql server instance. connecting to sql server: to ensure successful connectivity: use sql server management studio (ssms), a tool for managing and configuring sql server. if ssms is not installed on your system, download it from the official microsoft site: download sql server management studio (ssms) install the software once connectivity is confirmed, follow the instructions below to complete the installation."}
,{"id":383225948361,"name":"Configuring AnalyticsCreator","type":"section","path":"/docs/getting-started/configuring-analyticscreator","breadcrumb":"Getting Started › Configuring AnalyticsCreator","description":"","searchText":"getting started configuring analyticscreator this guide will walk you through configuring analyticscreator with your system. provide the login and password that you received by e-mail from analyticscreator minimum requirements configuration settings the configuration of analyticscreator is very simple. the only mandatory configuration is the sql server settings. sql server settings use localdb to store repository: enables you to store the analyticscreator project (metadata only) on your localdb. sql server to store repository: enter the ip address or the name of your microsoft sql server. security integrated: authentication is based on the current windows user. standard: requires a username and password. azure ad: uses azure ad (now microsoft entra) for microsoft sql server authentication. trust server certificate: accepts the server's certificate as trusted. sql user: the sql server username. sql password: the corresponding password. optional requirements paths unc path to store backup: a network path to store project backups. local sql server path to store backup: a local folder to store your project backups. local sql server path to store database: a local folder to store your sql server database backups. repository database template: the alias format for your repositories. default: repo_{reponame}. dwh database template: the alias format for your dwh templates. default: dwh_{reponame}. proxy settings proxy address: the ip address or hostname of your proxy server. proxy port: the port number used by the proxy. proxy user: the username for proxy authentication. proxy password: the password for the proxy user. now you're ready to create your new data warehouse with analyticscreator."}
,
{"id":383461199042,"name":"User Guide","type":"category","path":"/docs/user-guide","breadcrumb":"User Guide","description":"","searchText":"user guide you can launch analyticscreator in two ways: from the desktop icon after installation or streaming setup, a desktop shortcut is created. double-click the icon to start analyticscreator. from the installer window open the downloaded analyticscreator installer. instead of selecting install, click launch (labeled as number one in the image below). a window will appear showing the available analyticscreator servers, which deliver the latest version to your system. this process launches analyticscreator without performing a full installation, assuming all necessary prerequisites are already in place."}
,{"id":383225948364,"name":" Desktop Interface","type":"section","path":"/docs/user-guide/desktop-interface","breadcrumb":"User Guide › Desktop Interface","description":"","searchText":"user guide desktop interface with analyticscreator desktop users can: data warehouse creation automatically generate and structure your data warehouse, including fact tables and dimensions. connectors add connections to various data sources and import metadata seamlessly. layer management define and manage layers such as staging, persisted staging, core, and datamart layers. package generation generate integration packages for ssis (sql server integration services) and adf (azure data factory). indexes and partitions automatically configure indexes and partitions for optimized performance. roles and security manage roles and permissions to ensure secure access to your data. galaxies and hierarchies organize data across galaxies and define hierarchies for better data representation. customizations configure parameters, macros, scripts, and object-specific scripts for tailored solutions. filters and predefined transformations apply advanced filters and transformations for data preparation and enrichment. snapshots and versioning create snapshots to track and manage changes in your data warehouse. deployments deploy your projects with flexible configurations, supporting on-premises and cloud solutions. groups and models organize objects into groups and manage models for streamlined workflows. data historization automate the process of creating historical data models for auditing and analysis."}
,{"id":383225948365,"name":"Working with AnalyticsCreator","type":"section","path":"/docs/user-guide/working-with-analyticscreator","breadcrumb":"User Guide › Working with AnalyticsCreator","description":"","searchText":"user guide working with analyticscreator understanding the fundamental operations in analyticscreator desktop is essential for efficiently managing your data warehouse repository and ensuring accuracy in your projects. below are key basic operations you can perform within the interface: edit mode and saving - data warehouse editor single object editing: in the data warehouse repository, you can edit one object at a time. this ensures precision and reduces the risk of unintended changes across multiple objects. how to edit: double-click on any field within an object to enter edit mode. the selected field becomes editable, allowing you to make modifications. save prompt: if any changes are made, a prompt will appear, reminding you to save your modifications before exiting the edit mode. this safeguard prevents accidental loss of changes. unsaved changes: while edits are immediately reflected in the repository interface, they are not permanently saved until explicitly confirmed by clicking the save button. accessing views in data warehouse explorer layer-specific views: each layer in the data warehouse contains views generated by analyticscreator. these views provide insights into the underlying data structure and transformations applied at that layer. how to access: navigate to the data warehouse explorer and click on the view tab for the desired layer. this displays the layer's contents, including tables, fields, and transformations. adding and deleting objects adding new objects: navigate to the appropriate section (e.g., tables, layers, or connectors) in the navigation tree. right-click and select add [object type] to create a new object. provide the necessary details, such as name, description, and configuration parameters. save the object. deleting objects: select the object in the navigation tree and right-click to choose delete. confirm the deletion when prompted. â ď¸ note: deleting an object may affect dependent objects or configurations. filtering and searching in data warehouse explorer filtering: use filters to narrow down displayed objects by criteria such as name, type, or creation date. searching: enter keywords or phrases in the search bar to quickly locate objects. benefits: these features enhance repository navigation and efficiency when working with large datasets. object dependencies and relationships dependency view: for any selected object, view its dependencies and relationships with other objects by accessing the dependencies tab. impact analysis: analyze how changes to one object might affect other parts of the data warehouse. managing scripts predefined scripts: add scripts for common operations like data transformations or custom sql queries. edit and run: double-click a script in the navigation tree to modify it. use run script to execute and view results. validating and testing changes validation tools: use built-in tools to check for errors or inconsistencies in your repository. evaluate changes: use the evaluate button before saving or deploying to test functionality and ensure correctness. locking and unlocking objects locking: prevent simultaneous edits by locking objects, useful in team environments. unlocking: release locks once edits are complete to allow further modifications by others. exporting and importing data export: export objects, scripts, or configurations for backup or sharing. use the export option in the toolbar or navigation tree. import: import previously exported files to replicate configurations or restore backups. use the import option and follow the prompts to load the data."}
,{"id":391011561704,"name":"Historization with AnalyticsCreator","type":"subsection","path":"/docs/user-guide/working-with-analyticscreator/historization-with-analyticscreator","breadcrumb":"User Guide › Working with AnalyticsCreator › Historization with AnalyticsCreator","description":"","searchText":"user guide working with analyticscreator historization with analyticscreator historization in analyticscreator is applied after source import and before downstream analytical modeling. source data is first loaded into staging, then written into a persistent staging or historization layer, and only then used in core and datamart transformations. historization in analyticscreator table historization stores changing records with validity periods and surrogate keys. this page focuses on that pattern. column historization individual columns can use full history, equal-only behavior, or no change tracking. transformation historization downstream transformations can consume historized data as current-state, snapshot-based, or full historical output. join historization historized joins can apply different validity rules when combining time-dependent structures. purpose explain how analyticscreator stores and processes changing data over time so that previous states remain available for analysis and downstream processing. design principle analyticscreator treats historization as a warehouse-layer concern, not a reporting-layer concern. source data is imported first historization is applied in persistent staging downstream transformations consume historized data this design separates source extraction from change tracking and allows historical states to be reused across multiple downstream transformations. inputs / outputs inputs imported source table or source query in staging key definition used to identify records across loads column-level historization settings missing-source behavior optional filters and variables outputs historized table in persistent staging valid-from column valid-to column generated surrogate key generated historization stored procedure optional snapshot-aware downstream transformations internal mechanics 1. import first, historize second analyticscreator first imports source data into a staging table. historization is executed after the import step, not during initial extraction. 2. historized table structure a historized table typically contains: business key or source key tracked attributes valid-from field valid-to field surrogate key field this is the standard scd type 2 structure used to preserve previous states of a record. 3. column-level historization behavior historization is configurable per column. analyticscreator supports different behaviors per attribute: full history – changes create new historical versions equal only / scd1-style – current value is updated without creating a history row none – the column is ignored for change tracking this allows mixed historization strategies within the same object. 4. missing-source behavior analyticscreator allows explicit handling of records that disappear from the source: close the current record by setting the end of validity leave the current record open optionally insert an empty record to avoid timeline gaps this is important when rows can temporarily disappear and reappear later. 5. generated historization procedure historization logic is generated as a stored procedure. the procedure is specific to the object configuration and can be reviewed or extended if required. 6. downstream consumption downstream transformations can consume historized data in different ways: actual only – only the currently valid row is used snapshot – rows are selected based on a snapshot date between valid-from and valid-to full historical – all historical states remain available types / variants column-level change tracking full history equal only none missing-source behavior close validity keep open add empty record consumption behavior current-state only snapshot-based full historical access example assume a staging table contains customer data: stg_customer ( customer_id, name, city ) a historized table generated from it may look like this: pst_customer_history ( sats_id bigint, customer_id int, name nvarchar(100), city nvarchar(100), date_from datetime, date_to datetime ) a representative scd type 2 pattern is: -- close current row when tracked attributes changed update tgt set date_to = @load_ts from pst_customer_history tgt join stg_customer src on tgt.customer_id = src.customer_id and tgt.date_to is null where isnull(tgt.name, '') <> isnull(src.name, '') or isnull(tgt.city, '') <> isnull(src.city, ''); -- insert new current row insert into pst_customer_history ( customer_id, name, city, date_from, date_to ) select src.customer_id, src.name, src.city, @load_ts, null from stg_customer src left join pst_customer_history tgt on tgt.customer_id = src.customer_id and tgt.date_to is null where tgt.customer_id is null or isnull(tgt.name, '') <> isnull(src.name, '') or isnull(tgt.city, '') <> isnull(src.city, ''); this pattern shows the core behavior: current rows are closed when tracked attributes change, and a new current row is inserted. when to use / when not to use use when attribute changes must remain traceable over time source systems overwrite current values point-in-time analysis is required previous business states must remain queryable do not use when only the latest state matters the source already provides reliable historized data and duplicate historization is unnecessary storage growth from history rows is not acceptable performance & design considerations historization increases write volume and storage usage over-tracking noisy columns creates unnecessary row churn wrong missing-source settings can produce incorrect history timelines snapshot-based downstream joins are more expensive than current-state joins design trade-off: full history gives maximum traceability selective tracking improves storage and runtime efficiency integration with other analyticscreator features import packages and pipelines provide the staging input for historization transformation historization types define how historized rows are consumed downstream macros can support key generation in hybrid and data vault scenarios persisting can materialize downstream historized views for performance datamarts and semantic models can consume current-state or snapshot-based outputs common pitfalls tracking all columns as scd type 2 even when some should be scd1 or ignored not defining missing-source behavior using current-state-only logic when point-in-time analysis is required overusing snapshot logic in scenarios where current-state output is sufficient changing generated sql directly instead of fixing metadata configuration metadata representation historization metadata in analyticscreator typically includes: source object reference key definition per-column historization mode missing-source behavior optional filters and variables downstream transformation historization mode these settings are stored in the repository and used to generate historization logic and dependent transformations. deployment behavior build reads metadata from the repository generates historized tables generates historization procedures builds downstream transformations deploy deploys historized table structures deploys generated procedures deploys orchestration assets refresh / execute imports source data into staging executes historization logic refreshes downstream core and datamart structures key design principle what is generated? historized tables, surrogate keys, validity columns, and historization procedures when is it executed? after source import and before downstream transformation processing where is it stored? in the persistent staging or historization layer how does it scale? through selective column tracking, explicit missing-source handling, filtered loads, and downstream consumption control key takeaway analyticscreator implements scd type 2 historization as a configurable warehouse-layer service that preserves previous states through validity windows, surrogate keys, and generated historization procedures."}
,{"id":383225948366,"name":"Advanced Features","type":"section","path":"/docs/user-guide/advanced-features","breadcrumb":"User Guide › Advanced Features","description":"","searchText":"user guide advanced features analyticscreator provides a rich set of advanced features to help you configure, customize, and optimize your data warehouse projects. these features extend the toolâs capabilities beyond standard operations, enabling more precise control and flexibility. scripts scripts in analyticscreator allow for detailed customization at various stages of data warehouse creation and deployment. they enhance workflow flexibility and enable advanced repository configurations. types of scripts object-specific scripts define custom behavior for individual objects, such as tables or transformations, to meet specific requirements. pre-creation scripts execute tasks prior to creating database objects. example: define sql functions to be used in transformations. pre-deployment scripts configure processes that run before deploying the project. example: validate dependencies or prepare the target environment. post-deployment scripts handle actions executed after deployment is complete. example: perform cleanup tasks or execute stored procedures. pre-workflow scripts manage operations that occur before initiating an etl workflow. example: configure variables or initialize staging environments. repository extension scripts extend repository functionality with user-defined logic. example: add custom behaviors to redefine repository objects. historization the historization features in analyticscreator enable robust tracking and analysis of historical data changes, supporting advanced time-based reporting and auditing. key components slowly changing dimensions (scd) automate the management of changes in dimension data. supports various scd types including: type 1 (overwrite) type 2 (versioning) others as needed time dimensions create and manage temporal structures to facilitate time-based analysis. example: build fiscal calendars or weekly rollups for time-series analytics. snapshots capture and preserve specific states of the data warehouse. use cases include audit trails, historical reporting, and rollback points. parameters and macros these tools provide centralized control and reusable logic to optimize workflows and streamline repetitive tasks. parameters dynamic management: centralize variable definitions for consistent use across scripts, transformations, and workflows. reusable configurations: update values in one place to apply changes globally. use cases: set default values for connection strings, table prefixes, or date ranges. macros reusable logic: create parameterized scripts for tasks repeated across projects or workflows. streamlined processes: use macros to enforce consistent logic in transformations and calculations. example: define a macro to calculate age from a birthdate and reuse it across transformations. summary analyticscreatorâs advanced features offer deep customization options that allow you to: control object-level behavior through scripting track and manage historical data effectively streamline project-wide settings with parameters reuse logic with powerful macros these capabilities enable you to build scalable, maintainable, and highly flexible data warehouse solutions."}
,{"id":383225948367,"name":"Wizards","type":"section","path":"/docs/user-guide/wizards","breadcrumb":"User Guide › Wizards","description":"","searchText":"user guide wizards the wizards in analyticscreator provide a guided and efficient way to perform various tasks related to building and managing a data warehouse. below is an overview of the eight available wizards and their core functions. dwh wizard the dwh wizard is designed to quickly create a semi-ready data warehouse. it is especially useful when the data source contains defined table relationships or manually maintained references. supports multiple architectures: classic (kimball), data vault 1.0 & 2.0, or mixed. automatically creates imports, dimensions, facts, hubs, satellites, and links. customizable field naming, calendar dimensions, and sap deltaq integration. source wizard the source wizard adds new data sources to the repository. supports source types: table or query. retrieves table relationships and sap-specific metadata. allows query testing and schema/table filtering. import wizard the import wizard defines and manages the import of external data into the warehouse. configures source, target schema, table name, and ssis package. allows additional attributes and parameters. historization wizard the historization wizard manages how tables or transformations are historized. supports scd types: 0, 1, and 2. configures empty record behavior and vault id usage. supports ssis-based or stored procedure historization. transformation wizard the transformation wizard creates and manages data transformations. supports regular, manual, script, and external transformation types. handles both historicized and non-historicized data. configures joins, fields, persistence, and metadata settings. calendar transformation wizard the calendar transformation wizard creates calendar transformations used in reporting and time-based models. configures schema, name, start/end dates, and date-to-id macros. assigns transformations to specific data mart stars. time transformation wizard the time transformation wizard creates time dimensions to support time-based analytics. configures schema, name, time period, and time-to-id macros. assigns transformations to specific data mart stars. snapshot transformation wizard the snapshot transformation wizard creates snapshot dimensions for snapshot-based analysis. allows creation of one snapshot dimension per data warehouse. configures schema, name, and data mart star assignment. by using these eight wizards, analyticscreator simplifies complex tasks, ensures consistency, and accelerates the creation and management of enterprise data warehouse solutions."}
,{"id":384157771973,"name":"DWH Wizard ","type":"subsection","path":"/docs/user-guide/wizards/dwh-wizard-function","breadcrumb":"User Guide › Wizards › DWH Wizard ","description":"","searchText":"user guide wizards dwh wizard the dwh wizard allows for the rapid creation of a semi-ready data warehouse. it is especially effective when the data source includes predefined table references or manually maintained source references. prerequisites at least one source connector must be defined before using the dwh wizard. note: the dwh wizard support flat files using duckdb , in that case you should select the option \"use metadata of existing sources\" or use the source wizard instead. to launch the dwh wizard, click the “dwh wizard” button in the toolbar. instead, the user can use the connector context menu: using the dwh wizard select the connector, optionally enter the schema or table filter, and click \"apply\". then, the source tables will be displayed. optionally, select the \"existing sources\" radio button to work with already defined sources instead of querying the external system (ideal for meta connectors). if a table already exists, the \"exist\" checkbox will be selected. to add or remove tables: select them and click the ▶ button to add. select from below and click the ◀ button to remove. dwh wizard architecture options the wizard can generate the dwh using: classic or mixed architecture: supports imports, historization, dimensions, and facts. data vault architecture: supports hubs, satellites, links, dimensions, and facts with automatic classification when “auto” is selected. define name templates for dwh objects: set additional parameters: dwh wizard properties field name appearance: leave unchanged, or convert to upper/lowercase. retrieve relations: enable automatic relation detection from source metadata. create calendar dimension: auto-create calendar dimension and define date range. include tables in facts: include related tables in facts (n:1, indirect, etc.). use calendar in facts: include date-to-calendar references in fact transformations. sap deltaq transfer mode: choose between idoc or trfs. sap deltaq automatic synchronization: enable automatic deltaq sync. sap description language: select sap object description language. datavault2: do not create hubs: optionally suppress hub creation in dv2. historizing type: choose ssis package or stored procedure for historization. use friendly names in transformations as column names: use display names from sap/meta/manual connectors. default transformations: select default predefined transformations for dimensions. stars: assign generated dimensions and facts to data mart stars."}
,{"id":384138863824,"name":"Snapshot transformation wizard","type":"subsection","path":"/docs/user-guide/wizards/snapshot-transformation-wizard","breadcrumb":"User Guide › Wizards › Snapshot transformation wizard","description":"","searchText":"user guide wizards snapshot transformation wizard to create a snapshot transformation, select \"add → snapshot dimension\" from the diagram context menu. this will open the snapshot transformation wizard. ⚠️ note: only one snapshot dimension can exist in the data warehouse. as shown in the image below: parameters schema the schema in which the snapshot transformation resides. name the name assigned to the snapshot transformation. stars the data mart stars where this snapshot transformation will be included."}
,{"id":384159908072,"name":"Import wizard","type":"subsection","path":"/docs/user-guide/wizards/import-wizard","breadcrumb":"User Guide › Wizards › Import wizard","description":"","searchText":"user guide wizards import wizard to start the import wizard, use the source context menu: import status indicators sources marked with a \"!\" icon indicate that they have not yet been imported. attempting to launch the import wizard on a source that has already been imported will result in an error. typical import wizard window there is a typical import wizard window, as shown in the image below: options: source: the source that should be imported. target schema: the schema of the import table. target name: the name of the import table. package: the name of the ssis package where the import will be done. you can select an existing import package or add a new package name. click finish to proceed. the import definition window will open, allowing the configuration of additional import attributes and parameters, as shown in the image below: post-import actions refer to the \"import package\" description for more details. after creating a new import, refresh the diagram to reflect the changes, as shown in the image below:"}
,{"id":384140346566,"name":"Source Wizard","type":"subsection","path":"/docs/user-guide/wizards/source-wizard","breadcrumb":"User Guide › Wizards › Source Wizard","description":"","searchText":"user guide wizards source wizard the source wizard is used to add new data sources to the repository. to launch the source wizard, right-click on the \"sources\" branch of a connector in the context menu and select \"add source.\" source wizard functionality the appearance and functionality of the source wizard will vary depending on the selected source type (table or query): table: when selecting table as the data source, the wizard provides options to configure and view available tables. configuring a table data source when selecting \"table\" as the data source in the source wizard, click the \"apply\" button to display the list of available source tables. optionally, you can enter a schema or table filter to refine the results. configuration options: retrieve relations: enables the retrieval of relationships for the selected source table, if available. sap description language: specifies the language for object descriptions when working with sap sources. sap deltaq attributes: for sap deltaq sources, additional deltaq-specific attributes must be defined. configuring a query as a data source when selecting \"query\" as the data source in the source wizard, follow these steps: define schema and name: specify the schema and name of the source for the repository. enter the query: provide the query in the query language supported by the data source. test the query: click the “test query” button to verify its validity and ensure it retrieves the expected results. complete the configuration: click the “finish” button to add the new source to the repository. the source definition window will open, allowing further modifications if needed."}
,{"id":384159908073,"name":"Time transformation wizard","type":"subsection","path":"/docs/user-guide/wizards/time-transformation-wizard","breadcrumb":"User Guide › Wizards › Time transformation wizard","description":"","searchText":"user guide wizards time transformation wizard to create a time transformation, select \"add → time dimension\" from the diagram context menu. as shown in the image below: the time transformation wizard will then open, allowing you to configure a new time transformation: parameters schema the schema in which the time transformation resides. name the name assigned to the time transformation. period (minutes) the interval (in minutes) used to generate time dimension records. time-to-id function the macro function that converts a datetime value into the key value for the time dimension. use case: convert datetime fields in fact transformations into time dimension members. stars the data mart stars where the time transformation will be included."}
,{"id":384136118500,"name":"Historization wizard","type":"subsection","path":"/docs/user-guide/wizards/historization-wizard","breadcrumb":"User Guide › Wizards › Historization wizard","description":"","searchText":"user guide wizards historization wizard the historization wizard is used to historicize a table or transformation. to start the historization wizard, use the object context menu: \"add\" → \"historization\" in the diagram, as shown in the image below: alternatively, the object context menu in the navigation tree can be used, as shown in the image below: parameters there is a typical historization wizard window, as shown in the image below: source table: the table that should be historicized. target schema: the schema of the historicized table. target name: the name of the historicized table. package: the name of the ssis package where the historization will be done. you can select an existing historization package or add a new package name. historizing type: you can select between ssis package and stored procedure. scd type: the user can select between different historization types: scd 0, scd 1, and scd 2. empty record behavior: defines what should happen in case of a missing source record. use vault id as pk: if you are using datavault or mixed architecture, the user can use hashkeys instead of business keys to perform historization. after clicking \"finish\", the historization will be generated, and the diagram will be updated automatically. then, the user can select the generated historization package and optionally change some package properties (see \"historizing package\")."}
,{"id":384157771974,"name":"Persisting wizard","type":"subsection","path":"/docs/user-guide/wizards/persisting-wizard","breadcrumb":"User Guide › Wizards › Persisting wizard","description":"","searchText":"user guide wizards persisting wizard the content of any regular or manual transformation can be stored in a table, typically to improve access speed for complex transformations. persisting the transformation is managed through an ssis package. to persist a transformation, the user should select \"add → persisting\" from the object context menu in the diagram. as shown in the image below: persisting wizard options as shown in the image below: transformation: the name of the transformation to persist. persist table: the name of the table where the transformation will be persisted. this table will be created in the same schema as the transformation. persist package: the name of the ssis package that manages the persistence process."}
,{"id":384138863823,"name":"Transformation wizard","type":"subsection","path":"/docs/user-guide/wizards/transformation-wizard","breadcrumb":"User Guide › Wizards › Transformation wizard","description":"","searchText":"user guide wizards transformation wizard the transformation wizard is used to create a new transformation. to start it, use the object context menu and select: \"add → transformation\" in the diagram. typical transformation wizard window supported transformation types regular transformations: described in tabular form, results in a generated view. manual transformations: hand-created views defined manually by the user. script transformations: based on sql scripts, often calling stored procedures. external transformations: created outside analyticscreator as ssis packages. main page parameters type: transformation type: dimension: fullhist, creates unknown member, joinhisttype: actual fact: snapshot, no unknown member, joinhisttype: historical_to other: fullhist, no unknown member, joinhisttype: historical_to manual, external, script: as named schema: schema name name: transformation name historizing type: fullhist snapshothist snapshot actualonly none main table: only for regular transformations create unknown member: adds surrogate id = 0 (for dimensions) persist transformation: save view to a table persist table: name of persist table persist package: ssis package name result table: for external/script types ssis package: for external/script types table selection page allows selection of additional tables. tables must be directly or indirectly related to the main table. parameters table joinhisttype none actual historical_from historical_to full join options: all n:1 direct related all direct related all n:1 related all related use hash keys if available parameter page configure additional parameters (for regular transformations only). fields: none all key fields all fields field names (if duplicated): field[n] table_field field name appearance: no changes upper case lower case key fields null to zero: replaces null with 0 use friendly names as column names stars page stars: data mart stars for the transformation default transformations: no defaults (facts) all defaults (dimensions) selected defaults dependent tables: manage dependent tables script page used for script transformations. enter the sql logic that defines the transformation. insert into imp.lastpayment(businessentityid, ratechangedate, rate) select ph.businessentityid, ph.ratechangedate, ph.rate from ( select businessentityid, max(ratechangedate) lastratechangedate from [imp].[employeepayhistory] group by businessentityid ) t inner join [imp].[employeepayhistory] ph on ph.businessentityid = t.businessentityid and ph.ratechangedate = t.lastratechangedate"}
,{"id":384140346567,"name":"Calendar transformation wizard","type":"subsection","path":"/docs/user-guide/wizards/calendar-transformation-wizard","breadcrumb":"User Guide › Wizards › Calendar transformation wizard","description":"","searchText":"user guide wizards calendar transformation wizard to create a calendar transformation, select \"add → calendar dimension\" from the diagram context menu. as shown in the image below: the calendar transformation wizard will open. typically, only one calendar transformation is required in the data warehouse. as shown in the image below: parameters schema: the schema of the calendar transformation. name: the name of the calendar transformation. date from: the start date for the calendar. date to: the end date for the calendar. date-to-id function: the macro name that transforms a datetime value into the key value for the calendar dimension. this macro is typically used in fact transformations to map datetime fields to calendar dimension members. stars: the data mart stars where the calendar transformation will be included."}
,
{"id":383461199043,"name":"Reference","type":"category","path":"/docs/reference","breadcrumb":"Reference","description":"","searchText":"reference this section provides structured technical reference documentation for analyticscreator. it is intended for users who need detailed information about the user interface, entity types, entities, and configuration parameters. use this section when you already know which part of the application you want to understand and need a precise description of available objects, categories, and options. reference sections user interface reference information for the analyticscreator user interface and its structural elements. navigation and ui components windows, dialogs, and views interaction patterns open user interface entity types reference for the structural categories used in analyticscreator, such as connectors, sources, tables, transformations, packages, scripts, and schemas. connector and source categories table and transformation types schema, package, and script types open entity types entities reference for the concrete entities used in analyticscreator and their roles in modeling, generation, and execution. modeling objects execution-related entities generated object definitions open entities parameters reference for configuration parameters and settings that control generation, execution, historization, and other system behavior. object-specific parameters execution and generation settings configuration options open parameters how to use this section the reference section is organized by topic area rather than by workflow. use user interface when you need help locating or understanding specific interface elements use entity types when you need to understand the available structural categories in analyticscreator use entities when you need reference information about concrete objects used in the model use parameters when you need detailed information about settings and configurable behavior when to use reference instead of other sections use getting started for onboarding and step-by-step implementation flow use tutorials for guided example walkthroughs use reference for precise technical definitions and detailed lookup documentation key takeaway the reference section provides structured technical lookup documentation for analyticscreator user interface elements, entity categories, concrete entities, and configuration parameters."}
,{"id":383461259458,"name":"User Interface","type":"section","path":"/docs/reference/user-interface","breadcrumb":"Reference › User Interface","description":"","searchText":"reference user interface the analyticscreator user interface is designed to support structured, metadata-driven development of data products. it provides a clear separation between modeling, configuration, and generation activities, enabling users to navigate complex data solutions efficiently. the interface is organized into multiple functional areas that work together: navigation & repository structure provides access to repositories, object groups, and individual objects. it reflects the logical organization of the data solution and supports collaboration across teams. design & modeling area the central workspace where users define sources, transformations, and data products. this includes visual representations of data flows and dependencies, supporting transparency and impact analysis. properties & configuration panels context-sensitive panels that allow detailed configuration of selected objects, including technical settings, mappings, and behavior definitions. toolbar offers quick access to key actions such as synchronization, validation, and deployment, enabling an efficient workflow from design to delivery. lineage & dependency visualization displays relationships between objects and data flows. users can explore upstream and downstream dependencies to understand the impact of changes. the interface follows a metadata-driven approach: users define logic and structure once, and analyticscreator generates the corresponding technical artifacts. this ensures consistency, traceability, and efficient lifecycle management across environments."}
,{"id":383509396676,"name":"Toolbar","type":"subsection","path":"/docs/reference/user-interface/toolbar","breadcrumb":"Reference › User Interface › Toolbar","description":"","searchText":"reference user interface toolbar the toolbar gives users direct access to the main functional areas of analyticscreator and serves as the primary entry point for day-to-day work across the platform. its sections follow the typical implementation flow, from repository and source management through warehouse design, data product preparation, process generation, deployment, configuration, and support. available topics file covers core workspace actions such as opening, saving, and managing repositories and project files. sources explains how to configure source systems, maintain connections, and import or refresh source metadata. dwh describes the toolbar area used to design warehouse structures, transformations, and historization logic. data mart shows the commands used to build analytics-ready data products and business-facing reporting models. etl summarizes the toolbar functions related to generating and managing data movement and transformation workflows. deployment documents the options for packaging, generating, and deploying analyticscreator artifacts to target environments. options covers application and repository settings that control environment behavior and authoring preferences. help points users to documentation, guidance, and support-oriented resources available from the toolbar. how to use this section start with file and sources when setting up or opening a repository and connecting source systems. use dwh and data mart when defining warehouse logic and shaping analytical output models. move to etl and deployment when you need to generate, run, or release implementation artifacts. use options for configuration changes and help when you need documentation or support guidance. key takeaway the toolbar section organizes analyticscreator commands by workflow stage, making it easier to move from repository setup and source ingestion to modeling, process generation, deployment, and support."}
,{"id":379959516358,"name":"File","type":"topic","path":"/docs/reference/user-interface/toolbar/file","breadcrumb":"Reference › User Interface › Toolbar › File","description":"","searchText":"reference user interface toolbar file the file menu contains commands for creating, connecting, and maintaining repositories in analyticscreator. from here, you can start new projects, connect to existing repositories, synchronize metadata, and back up or restore configurations. it's the primary place to manage the setup and ongoing maintenance of your warehouse models. [link:380044750015|dwh wizard] rapidly creates a semi-ready warehouse, ideal when sources include predefined or curated table references. [link:384157770997|sync dwh] synchronizes the warehouse with metadata and source changes to keep structures current. [link:373340595406|new] creates a new repository configuration for metadata and model definitions. [link:373340595407|connect] connects to an existing repository database to reuse or update metadata. [link:373340595408|backup & restore — load from file] imports repository data or metadata from a local file. [link:373340595408| backup & restore — save to file] saves the current repository or project metadata to a portable file. [link:373340595408|backup & restore — load from cloud] restores repository data directly from cloud storage. [link:373340595408|backup & restore — save to cloud] backs up the repository or metadata to connected cloud storage. find on diagram highlights specific tables, columns, or objects within the modeling diagram."}
,{"id":380042415310,"name":"Sources","type":"topic","path":"/docs/reference/user-interface/toolbar/sources","breadcrumb":"Reference › User Interface › Toolbar › Sources","description":"","searchText":"reference user interface toolbar sources overview the sources ribbon tab groups connector, source, and source-reference commands. function the tab opens source-related lists and the new-connector import flows from the main ribbon. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source defines the sources ribbon tab and the commands shown under it. how to access navigation tree not direct. use the main ribbon. toolbar sources diagram not direct. use the main ribbon. visual element mainwindow ribbon -> sources screen overview the sources ribbon tab shows the following source-defined button labels and groups. id property description 1 home visible label, button, tab, or grid header defined in the source-backed xaml. 2 connectors visible field label or grid column header defined in the source-backed xaml. 3 sources visible field label or grid column header defined in the source-backed xaml. 4 references visible field label or grid column header defined in the source-backed xaml. 5 add creates a new item or starts the add flow defined in the screen. 6 import from file visible label, button, tab, or grid header defined in the source-backed xaml. 7 import from cloud visible label, button, tab, or grid header defined in the source-backed xaml. 8 list visible label, button, tab, or grid header defined in the source-backed xaml. 9 new connector visible field label or grid column header defined in the source-backed xaml. related topics help options"}
,{"id":380044750015,"name":"DWH","type":"topic","path":"/docs/reference/user-interface/toolbar/dwh","breadcrumb":"Reference › User Interface › Toolbar › DWH","description":"","searchText":"reference user interface toolbar dwh overview the dwh ribbon tab groups list-entry commands for warehouse layers, schemas, tables, indexes, references, macros, predefined transformations, and snapshots. function the tab opens the warehouse list and maintenance pages from the main ribbon. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source defines the dwh ribbon tab and the commands shown under it. how to access navigation tree not direct. use the main ribbon. toolbar dwh diagram not direct. use the main ribbon. visual element mainwindow ribbon -> dwh screen overview the dwh ribbon tab shows the following source-defined button labels and groups. id property description 1 home visible label, button, tab, or grid header defined in the source-backed xaml. 2 layers visible label, button, tab, or grid header defined in the source-backed xaml. 3 schemas visible field label or grid column header defined in the source-backed xaml. 4 tables tab header defined in the source-backed xaml. 5 indexes visible label, button, tab, or grid header defined in the source-backed xaml. 6 references visible field label or grid column header defined in the source-backed xaml. 7 macros visible label, button, tab, or grid header defined in the source-backed xaml. 8 predefined trans. visible label, button, tab, or grid header defined in the source-backed xaml. 9 snapshots visible field label or grid column header defined in the source-backed xaml. 10 list visible label, button, tab, or grid header defined in the source-backed xaml. related topics data mart deployment etl help"}
,{"id":380044818681,"name":"Data mart","type":"topic","path":"/docs/reference/user-interface/toolbar/data-mart","breadcrumb":"Reference › User Interface › Toolbar › Data mart","description":"","searchText":"reference user interface toolbar data mart overview the data mart ribbon tab groups commands for galaxies, stars, hierarchies, roles, partitions, and models in the main analyticscreator window. function the tab exposes list-entry commands for data mart objects directly from the main ribbon. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source defines the data mart ribbon tab and the commands shown under it. how to access navigation tree not direct. use the main ribbon. toolbar data mart diagram not direct. use the main ribbon. visual element mainwindow ribbon -> data mart screen overview the data mart ribbon tab shows the following source-defined button labels and groups. id property description 1 home visible label, button, tab, or grid header defined in the source-backed xaml. 2 galaxies visible label, button, tab, or grid header defined in the source-backed xaml. 3 stars visible label, button, tab, or grid header defined in the source-backed xaml. 4 hierarchies visible label, button, tab, or grid header defined in the source-backed xaml. 5 roles visible field label or grid column header defined in the source-backed xaml. 6 partitions visible field label or grid column header defined in the source-backed xaml. 7 models visible field label or grid column header defined in the source-backed xaml. 8 list visible label, button, tab, or grid header defined in the source-backed xaml. related topics deployment dwh"}
,{"id":380044750017,"name":"ETL","type":"topic","path":"/docs/reference/user-interface/toolbar/etl","breadcrumb":"Reference › User Interface › Toolbar › ETL","description":"","searchText":"reference user interface toolbar etl overview the etl ribbon tab groups list-entry and creation commands for packages, scripts, imports, historizations, and transformations. function the tab opens etl lists and also starts the main transformation-related wizards. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source defines the etl ribbon tab and the commands shown under it. how to access navigation tree not direct. use the main ribbon. toolbar etl diagram not direct. use the main ribbon. visual element mainwindow ribbon -> etl screen overview the etl ribbon tab shows the following source-defined button labels and groups. id property description 1 home visible label, button, tab, or grid header defined in the source-backed xaml. 2 packages visible field label or grid column header defined in the source-backed xaml. 3 scripts visible label, button, tab, or grid header defined in the source-backed xaml. 4 imports visible label, button, tab, or grid header defined in the source-backed xaml. 5 historiza- tions visible label, button, tab, or grid header defined in the source-backed xaml. 6 transfor- mations visible label, button, tab, or grid header defined in the source-backed xaml. 7 new trans- formation visible label, button, tab, or grid header defined in the source-backed xaml. 8 calendar dimension visible label, button, tab, or grid header defined in the source-backed xaml. 9 time dimension visible label, button, tab, or grid header defined in the source-backed xaml. 10 snapshot dimension visible field label or grid column header defined in the source-backed xaml. 11 list visible label, button, tab, or grid header defined in the source-backed xaml. 12 new creates a new item or starts the add flow defined in the screen. related topics deployment dwh help options"}
,{"id":380044819646,"name":"Deployment","type":"topic","path":"/docs/reference/user-interface/toolbar/deployment","breadcrumb":"Reference › User Interface › Toolbar › Deployment","description":"","searchText":"reference user interface toolbar deployment overview the deployment ribbon tab contains the deployment-package entry point in the main analyticscreator window. function the tab provides the ribbon command that opens the deployment package page. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source defines the deployment ribbon tab and the commands shown under it. how to access navigation tree not direct. use the main ribbon. toolbar deployment diagram not direct. use the main ribbon. visual element mainwindow ribbon -> deployment screen overview the deployment ribbon tab shows the following source-defined button labels and groups. id property description 1 home visible label, button, tab, or grid header defined in the source-backed xaml. 2 deployment package visible field label or grid column header defined in the source-backed xaml. related topics data mart dwh etl"}
,{"id":380044819647,"name":"Options","type":"topic","path":"/docs/reference/user-interface/toolbar/options","breadcrumb":"Reference › User Interface › Toolbar › Options","description":"","searchText":"reference user interface toolbar options overview the options ribbon tab groups user-management and application-settings commands. function the tab opens user groups, dwh settings, interface settings, parameters, and encrypted strings. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source defines the options ribbon tab and the commands shown under it. how to access navigation tree not direct. use the main ribbon. toolbar options diagram not direct. use the main ribbon. visual element mainwindow ribbon -> options screen overview the options ribbon tab shows the following source-defined button labels and groups. id property description 1 home visible label, button, tab, or grid header defined in the source-backed xaml. 2 user groups group-related control or command defined in the source-backed ui. 3 dwh settngs visible label, button, tab, or grid header defined in the source-backed xaml. 4 interface visible label, button, tab, or grid header defined in the source-backed xaml. 5 parameter visible label, button, tab, or grid header defined in the source-backed xaml. 6 encrypted strings visible label, button, tab, or grid header defined in the source-backed xaml. related topics etl help sources"}
,{"id":380044750021,"name":"Help","type":"topic","path":"/docs/reference/user-interface/toolbar/help","breadcrumb":"Reference › User Interface › Toolbar › Help","description":"","searchText":"reference user interface toolbar help overview the help ribbon tab groups export, internet, and product-information commands. function the tab opens help resources such as eula, about, community links, and export helpers. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source defines the help ribbon tab and the commands shown under it. how to access navigation tree not direct. use the main ribbon. toolbar help diagram not direct. use the main ribbon. visual element mainwindow ribbon -> help screen overview the help ribbon tab shows the following source-defined button labels and groups. id property description 1 home visible label, button, tab, or grid header defined in the source-backed xaml. 2 export to visio visible label, button, tab, or grid header defined in the source-backed xaml. 3 export in word visible label, button, tab, or grid header defined in the source-backed xaml. 4 wikipedia visible label, button, tab, or grid header defined in the source-backed xaml. 5 videos visible label, button, tab, or grid header defined in the source-backed xaml. 6 community visible label, button, tab, or grid header defined in the source-backed xaml. 7 version history visible label, button, tab, or grid header defined in the source-backed xaml. 8 eula visible label, button, tab, or grid header defined in the source-backed xaml. 9 about visible label, button, tab, or grid header defined in the source-backed xaml. 10 export visible label, button, tab, or grid header defined in the source-backed xaml. 11 internet visible label, button, tab, or grid header defined in the source-backed xaml. related topics dwh etl options sources"}
,{"id":383509396677,"name":"Navigation tree","type":"subsection","path":"/docs/reference/user-interface/navigation-tree","breadcrumb":"Reference › User Interface › Navigation tree","description":"","searchText":"reference user interface navigation tree the navigation tree provides the primary structural view of an analyticscreator repository and helps users browse objects by area, layer, and responsibility. it is the fastest way to move across repository components, inspect relationships, and open the exact object or configuration area needed during design, maintenance, and troubleshooting. available topics connectors explains how connector objects appear in the tree and how they organize source-system access points. layers describes how repository layers structure objects and separate modeling responsibilities across the solution. packages shows how package objects are grouped in the tree for orchestration, movement, and process control. indexes covers where index definitions appear and how they are organized within the repository hierarchy. roles documents the tree placement of role-related objects used for access and semantic model control. galaxies explains how galaxy structures are represented and accessed from the navigation tree. hierarchies shows how hierarchy objects are grouped in the tree for analytical model navigation. partitions describes where partition definitions live in the tree and how they support model organization. parameters explains how technical and functional parameters are exposed for repository configuration and reuse. macros documents the navigation-tree location of reusable macros and shared logic components. object scripts covers how object-level scripts are organized for targeted execution and automation tasks. filters shows how filter definitions appear in the tree and support selective modeling behavior. predefined transformations explains where predefined transformation templates are stored and accessed from the tree. snapshots describes the tree location of snapshot-related objects used for point-in-time handling. deployments documents how deployment objects are grouped for release preparation and execution. groups shows how group structures help organize large repositories and related object collections. models explains where model objects appear in the tree and how they anchor business-facing structures. transformations describes how transformation logic is surfaced in the tree for editing, tracing, and maintenance. how to use this section use the tree to move quickly between repository object families instead of searching manually across dialogs and designers. start with structural areas such as layers, parameters, and groups when orienting yourself inside a project. use object-specific branches such as connectors, packages, deployments, and transformations when working on a focused implementation task. use the tree as the operational backbone of the repository, then open individual topics here to understand the behavior of each object area in detail. key takeaway the navigation tree organizes analyticscreator repository objects into a clear operational hierarchy, making it the central navigation surface for browsing, opening, and managing solution components."}
,{"id":380121766108,"name":"Connectors","type":"topic","path":"/docs/reference/user-interface/navigation-tree/connectors","breadcrumb":"Reference › User Interface › Navigation tree › Connectors","description":"","searchText":"reference user interface navigation tree connectors overview the connectors menu in analyticscreator defines metadata for establishing a connection to a source system. each connector includes a name, a source type, and a connection string. these connections are used in etl packages to access external data sources during data warehouse generation. function connectors allow analyticscreator to integrate with relational databases and other supported systems. the connection string is stored in the project metadata and referenced during package execution. each connector is project-specific and can be reused across multiple packages or layers. access connectors are managed under the sources section in the analyticscreator user interface. all defined connectors are listed in a searchable grid, and new entries can be created or deleted from this screen. selecting new opens a connector definition form with metadata fields and a connection string editor. how to access navigation tree connectors → connector → edit connector; connectors → add connector toolbar sources → add diagram not applicable visual element {searchconnectors} → connector → double-click screen overview the first image below shows the main connectors interface. the second shows the editor that appears when a new connector is created. list connectors id property description 1 connectorname logical name identifying the connector within the project 2 connectortype type of source system (e.g., mssql, oracle, etc.) 3 connectionstring ole db or equivalent connection string used to connect to the source system new connector dialog id property description 1 connectorname logical name identifying the connector within the project. 2 connectortype type of source system, for example mssql, oracle, or another supported connector type. 3 azure source type type of azure source, for example azure sql, azure postgres, or another supported azure source type. 4 connectionstring ole db or equivalent connection string used to connect to the source system. 5 cfg.ssis controls whether the connection string should not be stored in cfg.ssis_configurations. related topics sources connector types refresh source metadata create source"}
,{"id":380121766109,"name":"Layers","type":"topic","path":"/docs/reference/user-interface/navigation-tree/layers","breadcrumb":"Reference › User Interface › Navigation tree › Layers","description":"","searchText":"reference user interface navigation tree layers overview the layers feature in analyticscreator defines the logical and sequential structure in which metadata objects are grouped and generated. each object in a project is assigned to a layer, which determines its build order and visibility during solution generation. function layers represent vertical slices in a project's architecture, such as source, staging, persisted staging, transformation, data warehouse - core, or datamart. one layer can have one or more schemas associated with it. they are used to control: object assignment and isolation layers define where objects belong and keep architectural responsibilities clearly separated. deployment sequencing layers control the order in which structures are generated and deployed across environments. selective generation specific parts of the solution can be included or excluded based on layer configuration. dependency resolution layer order influences build-time logic and helps resolve dependencies between generated objects. layer configuration impacts how analyticscreator generates the sql database schema, azure data factory pipelines, and semantic models. access layers are accessible from the dwh section. a dedicated layers panel displays all defined layers, their order, and their assignment status. how to access navigation tree layers → layer → edit layer toolbar dwh → layers diagram not applicable visual element not applicable screen overview the image below shows the list layers interface with columns labeled for easy identification. id property description 1 name name of the layer used to identify it within the project structure. 2 seqnr defines the sequence number of the layer and controls its display order in the lineage. 3 description optional field used to provide a more detailed description of the layer. behavior execution order layers are executed in the defined top-down order. generation scope disabling a layer excludes its objects from generation. object assignment each object must belong to one and only one layer. build influence layers influence sql build context and pipeline generation. usage context layers are typically aligned with logical data architecture phases. common usage includes separating ingestion, transformation, modeling, and reporting responsibilities. notes layer configurations are stored within the project metadata. changes to layer order or status require regeneration of the solution. layer visibility and behavior apply across all deployment targets. related topics [link:#|schema] [link:#|table] [link:#|transformation] [link:#|predefined transformations]"}
,{"id":380121766110,"name":"Packages","type":"topic","path":"/docs/reference/user-interface/navigation-tree/packages","breadcrumb":"Reference › User Interface › Navigation tree › Packages","description":"","searchText":"reference user interface navigation tree packages overview packages is a feature in the navigation tree that provides access to package-related areas. it serves as the parent entry for multiple package categories and helps organize package-related functionality in one place. function the packages feature is used to open and access the package-related areas available in analyticscreator. it acts as a structural entry in the navigation tree and groups the available package categories under one feature. access the packages feature is available in the navigation tree of the main analyticscreator user interface. how to access navigation tree navigation tree → packages toolbar dwh -> packages diagram not applicable. visual element not confirmed. screen overview id property description 1 package name displays the unique name of the package 2 package type shows the type of the package (e.g., imp, hist, pers) 3 manually created indicates if the package was created manually 4 externally launched indicates if the package is triggered externally 5 description shows notes or comments about the package 6 delete deletes the selected package 7 new opens the editor to define a new package related topics connectors deployments filters galaxies"}
,{"id":380121766111,"name":"Indexes","type":"topic","path":"/docs/reference/user-interface/navigation-tree/indexes","breadcrumb":"Reference › User Interface › Navigation tree › Indexes","description":"","searchText":"reference user interface navigation tree indexes overview indexes is a feature in the analyticscreator navigation tree. it is used to group and expose index-related content in a consistent location within the user interface. function from a reference-guide perspective, this feature should be understood as a user-interface entry that helps the user locate and open index-related objects or related maintenance areas. access the indexes feature is used to navigate to index-related content. it serves as a structural access point in the navigation tree rather than as a standalone processing object. how to access navigation tree navigation tree → indexes toolbar data mart → indexes diagram not applicable. visual element not confirmed. screen overview id property description 1 schema schema that contains the indexed table. 2 table table where the index is defined. 3 index index name displayed in the list. 4 clustered indicates whether the listed index is clustered. 5 unique indicates whether the listed index enforces unique values. 6 primary key indicates whether the listed index is the primary key. related topics connectors deployments filters galaxies"}
,{"id":380121767100,"name":"Roles","type":"topic","path":"/docs/reference/user-interface/navigation-tree/roles","breadcrumb":"Reference › User Interface › Navigation tree › Roles","description":"","searchText":"reference user interface navigation tree roles overview in analyticscreator, a role is a security object that defines which users have which access rights and which data restrictions apply. function it is used to assign users to a role and to control behavior such as rights and filters, including cube-related settings like tabular cube, multidimensional cube, and dax filter. access roles are maintained with general properties, user assignments, cube-specific settings, and filter settings. how to access navigation tree roles → role → edit role; roles → add role toolbar data mart -> roles diagram not applicable visual element not confirmed screen overview id property description 1 search criteria input box used to filter the roles list. 2 search runs the search for the entered criteria. 3 delete deletes the selected role. 4 duplicate creates a copy of the selected role. 5 new opens the editor to define a new role. related topics groups filters user groups olap roles"}
,{"id":380121783543,"name":"Galaxies","type":"topic","path":"/docs/reference/user-interface/navigation-tree/galaxies","breadcrumb":"Reference › User Interface › Navigation tree › Galaxies","description":"","searchText":"reference user interface navigation tree galaxies overview in analyticscreator, a galaxy is a logical container for related star schemas. it is used to group stars into a shared business context, which helps organize larger analytical solutions and manage related data mart structures more clear. function each galaxy acts as a container for related stars. access galaxies are used to organize larger analytical solutions by grouping related stars into a shared business context. how to access navigation tree galaxies → galaxy → right-click → edit toolbar data mart → galaxies diagram not applicable. visual element not confirmed. screen overview id property description 1 name the display name of the galaxy 2 galaxy galaxy group to which the star schema belongs 3 schema database schema in which the galaxy resides 4 order in diagram defines the position of the galaxy in the diagram for layout purposes 5 description optional text describing the galaxy's business context or contents related topics connectors deployments filters groups"}
,{"id":380121783544,"name":"Hierarchies","type":"topic","path":"/docs/reference/user-interface/navigation-tree/hierarchies","breadcrumb":"Reference › User Interface › Navigation tree › Hierarchies","description":"","searchText":"reference user interface navigation tree hierarchies overview in analyticscreator, hierarchies define semantic drill-down paths within dimension tables, such as year -> quarter -> month -> day. they are used for semantic model generation and cube design. function a hierarchy groups multiple columns of a dimension table in a defined sequence for user-friendly navigation and drill-downs in reports. access hierarchies are managed from the data mart hierarchy tools. each hierarchy is tied to a table and contains one or more ordered levels. how to access navigation tree hierarchies → hierarchy → right-click → edit toolbar data mart → hierarchies diagram diagram → hierarchies → right-click → edit visual element not confirmed. screen overview id property description 1 schema database schema for the table that owns the hierarchy. 2 table table where the hierarchy is defined. 3 hierarchy hierarchy name displayed in the list. 4 clustered indicates whether the listed hierarchy is marked as clustered. 5 delete removes the selected hierarchy from the list. 6 new creates a new hierarchy entry. related topics connectors deployments filters galaxies"}
,{"id":380121784533,"name":"Partitions","type":"topic","path":"/docs/reference/user-interface/navigation-tree/partitions","breadcrumb":"Reference › User Interface › Navigation tree › Partitions","description":"","searchText":"reference user interface navigation tree partitions overview in analyticscreator, a partition is used to divide large fact or dimension tables into logical slices for improved performance, faster refresh operations, and better manageability. function the partitions feature is used to define and maintain table partitions. access partitions are configured by partition key, strategy, and slice definition. they can be used to partition large tables by keys such as date or region. how to access navigation tree partitions → partition → right-click → edit toolbar dwh -> partitions diagram not applicable. visual element not confirmed. screen overview id property description 1 fact table fact table associated with the partition. 2 name partition name shown in the list. 3 delete removes the selected partition from metadata. 4 duplicate creates a copy of an existing partition definition. 5 new opens the editor to define a new partition. related topics connectors deployments filters galaxies"}
,{"id":380121767101,"name":"Parameters","type":"topic","path":"/docs/reference/user-interface/navigation-tree/parameters","breadcrumb":"Reference › User Interface › Navigation tree › Parameters","description":"","searchText":"reference user interface navigation tree parameters overview parameters are configuration settings that control technical behavior, naming rules, deployment options, and other system or project-specific functions across the application. each parameter provides a technical or project-related setting that influences areas such as logging, naming conventions, deployment behavior, storage settings, and provider configuration. function the parameters feature is used to review default parameter values and define custom values for the current project. changes made in this area affect how analyticscreator behaves during modeling, generation, deployment, and related technical processing. access parameters are available in the main analyticscreator user interface. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview the parameters screen contains a parameter list with default values and optional custom values. this page covers the following parameters: ac_log: controls the logging level of deployment and processing. value range: 0 = no log, 1 = basic log. table_compression_type: defines the default table compression type. documented values: 1 = none, 2 = page, 3 = raw. pers_default_partswitch: parameter name confirmed in the current public parameter reference, but the detailed description was not exposed in the fetched snippet. diagram_name_pattern: defines the object name shown in diagrams. supported placeholders include {name}, {friendly name}, {fullfriendlyname}, {id}, and {cr}. the documented default is {fullfriendlyname}. oledbprovider_sqlserver: defines the oledb provider for sql server. hist_proc_use_hash_join: parameter name confirmed in the current public parameter reference, but the detailed description was not exposed in the fetched snippet. deployment_create_subdirectory: creates a subdirectory for every generated deployment package. value range: 0 = no, 1 = yes. dwh_metadata_in_extended_properties: parameter name confirmed in the current public parameter reference, but the detailed description was not exposed in the fetched snippet. project_restrict_filepath_length: parameter name confirmed in the current public parameter reference, but the detailed description was not exposed in the fetched snippet. related topics options dwh settings encrypted strings"}
,{"id":380121767102,"name":"Macros","type":"topic","path":"/docs/reference/user-interface/navigation-tree/macros","breadcrumb":"Reference › User Interface › Navigation tree › Macros","description":"","searchText":"reference user interface navigation tree macros overview a macro is a reusable action object used in transformations to standardize repeated logic and reduce duplication in the data warehouse model. function the macros feature is used to create and maintain reusable macro actions. access macros help standardize repeated logic in transformations and other workflow scenarios. they can be used to centralize reusable sql or ssis-based logic and support parameterized patterns through placeholders. how to access navigation tree macros → macro → right-click → edit toolbar dwh -> macros diagram not applicable. visual element not confirmed. screen overview id property description 1 name unique identifier for the macro used in referencing expressions 2 language specifies the sql dialect or scripting language used (e.g., t-sql) related topics connectors deployments filters galaxies"}
,{"id":380121784534,"name":"Object scripts","type":"topic","path":"/docs/reference/user-interface/navigation-tree/object-scripts","breadcrumb":"Reference › User Interface › Navigation tree › Object scripts","description":"","searchText":"reference user interface navigation tree object scripts overview object scripts is a navigation-tree entry in the main analyticscreator window. function the tree node is created in mainwindow.xaml.cs and uses the mnuobjectscripts context menu defined in mainwindow.xaml. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source shows the tree entry, its context-menu commands, and the supporting main-window controls. how to access navigation tree main window tree -> object scripts toolbar not direct. use the navigation tree object scripts node. diagram not direct. use the navigation tree. visual element mainwindow -> object scripts tree node screen overview the object scripts navigation entry exposes the following tree labels and commands in the source-backed ui. id property description 1 refresh visible label, button, tab, or grid header defined in the source-backed xaml. 2 list object scripts visible label, button, tab, or grid header defined in the source-backed xaml. 3 add object script visible label, button, tab, or grid header defined in the source-backed xaml. related topics filters groups"}
,{"id":380121784535,"name":"Filters","type":"topic","path":"/docs/reference/user-interface/navigation-tree/filters","breadcrumb":"Reference › User Interface › Navigation tree › Filters","description":"","searchText":"reference user interface navigation tree filters overview filters is a navigation-tree entry in the main analyticscreator window. function the tree node is created in mainwindow.xaml.cs and uses the mnufilters context menu defined in mainwindow.xaml. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source shows the tree entry, its context-menu commands, and the supporting main-window controls. how to access navigation tree main window tree -> filters toolbar file -> find on diagram and the diagram filter controls in the main window. diagram not direct. use the navigation tree. visual element mainwindow -> filters tree node screen overview the filters navigation entry exposes the following tree labels and commands in the source-backed ui. id property description 1 filters filter-related control or command defined in the source-backed ui. 2 store current filter filter-related control or command defined in the source-backed ui. 3 apply filter filter-related control or command defined in the source-backed ui. 4 group group-related control or command defined in the source-backed ui. 5 diagram filter filter-related control or command defined in the source-backed ui. 6 actual filter filter-related control or command defined in the source-backed ui. related topics deployments groups object scripts"}
,{"id":380121767103,"name":"Predefined transformations","type":"topic","path":"/docs/reference/user-interface/navigation-tree/predefined-transformations","breadcrumb":"Reference › User Interface › Navigation tree › Predefined transformations","description":"","searchText":"reference user interface navigation tree predefined transformations overview a predefined transformation is a reusable transformation template for common patterns. it helps standardize field-level transformation logic and reduce repetitive manual configuration in the data warehouse model. function the predefined transformations feature is used to provide access to reusable transformation templates. access these predefined transformations represent ready-to-use logic for recurring conversion, cleanup, formatting, and standardization tasks. how to access navigation tree navigation tree → predefined transformations toolbar etl -> predefined transformations diagram not applicable. visual element not confirmed. screen overview id property description 1 name predefined transformation name shown in the list. 2 description text describing the predefined transformation. 3 delete deletes the selected predefined transformation. 4 new opens the editor to define a new predefined transformation. related topics transformations macros object scripts filters"}
,{"id":380121767104,"name":"Snapshots","type":"topic","path":"/docs/reference/user-interface/navigation-tree/snapshots","breadcrumb":"Reference › User Interface › Navigation tree › Snapshots","description":"","searchText":"reference user interface navigation tree snapshots overview a snapshot is a metadata object used to capture point-in-time states. it helps preserve historical values for time-based analysis and historization scenarios in the data warehouse model. function the snapshots feature is used to define and maintain snapshot structures. access snapshots are used for point-in-time tracking and historization scenarios, including scd-related time tracking. how to access navigation tree snapshots → snapshot → right-click → edit toolbar etl -> snapshots diagram not applicable. visual element not confirmed. screen overview id property description 1 name unique identifier used to reference the snapshot in expressions 2 update sql the sql expression that returns a single scalar value (e.g., current date or timestamp) 3 description optional explanation of what the snapshot represents 4 delete removes the selected snapshot definition 5 new creates a new snapshot entry in the list related topics historization snapshot groups dimensions transformations"}
,{"id":380121767105,"name":"Deployments","type":"topic","path":"/docs/reference/user-interface/navigation-tree/deployments","breadcrumb":"Reference › User Interface › Navigation tree › Deployments","description":"","searchText":"reference user interface navigation tree deployments overview deployments is a navigation-tree entry in the main analyticscreator window. function the tree node is created in mainwindow.xaml.cs and uses the mnudeployments context menu defined in mainwindow.xaml. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source shows the tree entry, its context-menu commands, and the supporting main-window controls. how to access navigation tree main window tree -> deployments toolbar not direct. use the navigation tree deployments node. diagram not direct. use the navigation tree. visual element mainwindow -> deployments tree node screen overview the deployments navigation entry exposes the following tree labels and commands in the source-backed ui. id property description 1 refresh visible label, button, tab, or grid header defined in the source-backed xaml. 2 list deployments visible label, button, tab, or grid header defined in the source-backed xaml. 3 add deployment visible label, button, tab, or grid header defined in the source-backed xaml. related topics filters groups"}
,{"id":380121767106,"name":"Groups","type":"topic","path":"/docs/reference/user-interface/navigation-tree/groups","breadcrumb":"Reference › User Interface › Navigation tree › Groups","description":"","searchText":"reference user interface navigation tree groups overview groups is a navigation-tree entry in the main analyticscreator window. function the tree node is created in mainwindow.xaml.cs and uses the mnugroups context menu defined in mainwindow.xaml. access this topic was rebuilt from mainwindow.xaml and mainwindow.xaml.cs. the source shows the tree entry, its context-menu commands, and the supporting main-window controls. how to access navigation tree main window tree -> groups toolbar not direct. use the navigation tree groups node or the diagram group selector. diagram not direct. use the navigation tree. visual element mainwindow -> groups tree node screen overview the groups navigation entry exposes the following tree labels and commands in the source-backed ui. id property description 1 refresh visible label, button, tab, or grid header defined in the source-backed xaml. 2 list groups group-related control or command defined in the source-backed ui. 3 add group group-related control or command defined in the source-backed ui. related topics deployments filters object scripts"}
,{"id":380121784536,"name":"Models","type":"topic","path":"/docs/reference/user-interface/navigation-tree/models","breadcrumb":"Reference › User Interface › Navigation tree › Models","description":"","searchText":"reference user interface navigation tree models overview a model is a semantic model definition used to organize data mart objects for analytical or reporting purposes. function the models feature is used to define and maintain model metadata. access each model represents a logical grouping of tables and serves as a high-level container for a business-specific semantic definition. how to access navigation tree models → model → right-click → edit toolbar dwh -> models diagram not applicable. visual element not confirmed. screen overview id property description 1 name model name shown in the list. 2 description text describing the model. related topics connectors deployments filters galaxies"}
,{"id":381152140476,"name":"Transformations","type":"topic","path":"/docs/reference/user-interface/navigation-tree/transformations","breadcrumb":"Reference › User Interface › Navigation tree › Transformations","description":"","searchText":"reference user interface navigation tree transformations overview the transformations freature is used to define and manage data transformation objects such as dimensions and fact tables. each transformation describes how data is processed, historized, and loaded into the data warehouse or star schema. function transformations define how analyticscreator processes, combines, and prepares data between sources and target structures. they store the transformation logic in project metadata and can be reused within the data flow and deployment process. access transformations can be accessed via dwh > transformations in the main navigation panel. all defined transformations are listed in a searchable grid, and new entries can be created using the transformation wizard. selecting new opens the wizard, which guides the user through defining a transformation step-by-step. how to access navigation tree dwh > transformations > transformation > edit transformation; dwh > add transformation toolbar etl > new transformation diagram right-click context menu > add > transformation visual element {searchtransformations} > add -> transformation > double-click screen overview the first image below shows the main transformations list interface. the following images show each screen of the transformation wizard (screens a, b, and c). list transformations id property description 1 schema the target schema for the transformation (e.g., dwh, star). 2 name the name of the transformation table being defined. 3 type indicates the transformation type (manual, regular, datamart). 4 hist type specifies the historization type applied (none, snapshot, fullhist). 5 createdummyentry defines whether to include a dummy or unknown member record. 6 delete removes a selected transformation. 7 duplicate creates a copy of an existing transformation. 8 new opens the transformation wizard to create a new transformation. related topics [link:#|transformation wizard] [link:#|calendar transformation wizard] [link:#|time transformation wizard] [link:#|snapshot transformation wizard] [link:#|predefined transformations] [link:#|new transformation]"}
,{"id":383509174508,"name":"Dataflow diagram","type":"subsection","path":"/docs/reference/user-interface/dataflow-diagram","breadcrumb":"Reference › User Interface › Dataflow diagram","description":"","searchText":"reference user interface dataflow diagram the dataflow diagram section explains the object types that appear in analyticscreator's visual dataflow and how they represent movement, transformation, and delivery across the solution. use these topics to understand how operational objects relate to one another in the diagram and how to read the pipeline from filtering and grouping through storage, historization, and export. available topics search search is a dataflow diagram feature used to quickly locate objects by entering keywords or phrases in the search bar. filters a filter is a reusable view definition used in the dataflow diagram to limit the visible objects based on selected criteria such as object types, layers, schemas, or groups. object groups object groups are used to organize objects such as sources, tables, and transformations into reusable groups. layers a layer is a logical architectural slice used to group metadata objects and define their build order and visibility in the model. source in analyticscreator, a source is a metadata object that describes external data. table a table is a metadata object that represents a database table or view within the data warehouse. transformation a transformation is a metadata object used to define how data is processed in the staging and warehouse layers. fact in analyticscreator, a fact is a metadata object used to model quantitative business data for analytical processing in the data warehouse and data mart. dimension a dimension is a metadata object used in the data warehouse model to organize descriptive business data and support analysis of facts through shared business context. import shows how import objects appear in the dataflow diagram and how they bring source data into the warehouse pipeline. historization a historization is a metadata object used to track changes of a table or transformation over time in the data warehouse model. persisting a persisting object is a metadata object used to store the content of a regular or manual transformation in a table to improve access speed for complex transformations. export shows how export objects appear in the dataflow diagram and how they deliver modeled data to downstream targets. how to use this section start with search, filters, and object groups when you need to orient yourself inside a large visual model. use layers, source, table, and transformation to follow the structural path of data through the warehouse. use fact, dimension, import, historization, and persisting to understand the implementation role of each diagram element. use export when the flow continues beyond internal warehouse processing into downstream delivery scenarios. key takeaway the dataflow diagram section helps readers interpret analyticscreator diagrams as end-to-end operational models, connecting each object type to its role in the data pipeline."}
,{"id":386694025440,"name":"Search","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-search","breadcrumb":"Reference › User Interface › Dataflow diagram › Search","description":"","searchText":"reference user interface dataflow diagram search overview search is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support search. how to access navigation tree not direct. use the architecture diagram view. toolbar file -> find on diagram diagram architecture -> search node or related context-menu command visual element architecture -> search screen overview the search diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 find on diagram visible label, button, tab, or grid header defined in the source-backed xaml. 2 group group-related control or command defined in the source-backed ui. 3 diagram filter filter-related control or command defined in the source-backed ui. 4 selected object visible label, button, tab, or grid header defined in the source-backed xaml. 5 actual filter filter-related control or command defined in the source-backed ui. related topics object groups persisting source table"}
,{"id":386694025434,"name":"Filters","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-filters","breadcrumb":"Reference › User Interface › Dataflow diagram › Filters","description":"","searchText":"reference user interface dataflow diagram filters overview filters is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support filters. how to access navigation tree not direct. use the architecture diagram view. toolbar file -> find on diagram and the main-window filter controls. diagram architecture -> filters node or related context-menu command visual element architecture -> filters screen overview the filters diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 set filter filter-related control or command defined in the source-backed ui. 2 add to filter filter-related control or command defined in the source-backed ui. 3 store filter filter-related control or command defined in the source-backed ui. 4 remove filter filter-related control or command defined in the source-backed ui. 5 apply filter filter-related control or command defined in the source-backed ui. related topics export fact historization import"}
,{"id":386694025438,"name":"Object groups","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-object-groups","breadcrumb":"Reference › User Interface › Dataflow diagram › Object groups","description":"","searchText":"reference user interface dataflow diagram object groups overview object groups is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support object groups. how to access navigation tree not direct. use the architecture diagram view. toolbar not direct. use the object or package context menu. diagram architecture -> object groups node or related context-menu command visual element architecture -> object groups screen overview the object groups diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 object groups group-related control or command defined in the source-backed ui. 2 group group-related control or command defined in the source-backed ui. 3 diagram filter filter-related control or command defined in the source-backed ui. 4 selected object visible label, button, tab, or grid header defined in the source-backed xaml. 5 actual filter filter-related control or command defined in the source-backed ui. related topics import layers persisting search"}
,{"id":386694025437,"name":"Layers","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-layers","breadcrumb":"Reference › User Interface › Dataflow diagram › Layers","description":"","searchText":"reference user interface dataflow diagram layers overview layers is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support layers. how to access navigation tree not direct. use the architecture diagram view. toolbar dwh -> layers diagram architecture -> layers node or related context-menu command visual element architecture -> layers screen overview the layers diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 group group-related control or command defined in the source-backed ui. 2 diagram filter filter-related control or command defined in the source-backed ui. 3 selected object visible label, button, tab, or grid header defined in the source-backed xaml. 4 actual filter filter-related control or command defined in the source-backed ui. 5 store filter filter-related control or command defined in the source-backed ui. related topics historization import object groups persisting"}
,{"id":386694025441,"name":"Source","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-source","breadcrumb":"Reference › User Interface › Dataflow diagram › Source","description":"","searchText":"reference user interface dataflow diagram source overview source is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support source. how to access navigation tree not direct. use the architecture diagram view. toolbar sources -> sources diagram architecture -> source node or related context-menu command visual element architecture -> source screen overview the source diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 data source visible field label or grid column header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 refresh source visible field label or grid column header defined in the source-backed xaml. 4 preview data visible label, button, tab, or grid header defined in the source-backed xaml. 5 object groups group-related control or command defined in the source-backed ui. related topics persisting search table transformation"}
,{"id":386694025442,"name":"Table","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-table","breadcrumb":"Reference › User Interface › Dataflow diagram › Table","description":"","searchText":"reference user interface dataflow diagram table overview table is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support table. how to access navigation tree not direct. use the architecture diagram view. toolbar dwh -> tables diagram architecture -> table node or related context-menu command visual element architecture -> table screen overview the table diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 externally filled table visible field label or grid column header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 preview data visible label, button, tab, or grid header defined in the source-backed xaml. 5 object groups group-related control or command defined in the source-backed ui. related topics search source transformation"}
,{"id":386694025443,"name":"Transformation","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-transformation","breadcrumb":"Reference › User Interface › Dataflow diagram › Transformation","description":"","searchText":"reference user interface dataflow diagram transformation overview transformation is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support transformation. how to access navigation tree not direct. use the architecture diagram view. toolbar etl -> new transformation diagram architecture -> transformation node or related context-menu command visual element architecture -> transformation screen overview the transformation diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 transformation visible label, button, tab, or grid header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 object groups group-related control or command defined in the source-backed ui. 5 preview data visible label, button, tab, or grid header defined in the source-backed xaml. related topics source table"}
,{"id":386694025433,"name":"Fact","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-fact","breadcrumb":"Reference › User Interface › Dataflow diagram › Fact","description":"","searchText":"reference user interface dataflow diagram fact overview fact is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support fact. how to access navigation tree not direct. use the architecture diagram view. toolbar not direct. use the architecture diagram or the related detail page. diagram architecture -> fact node or related context-menu command visual element architecture -> fact screen overview the fact diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 fact visible label, button, tab, or grid header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 preview data visible label, button, tab, or grid header defined in the source-backed xaml. 5 object groups group-related control or command defined in the source-backed ui. related topics dimension export filters historization"}
,{"id":386694025431,"name":"Dimension","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-dimension","breadcrumb":"Reference › User Interface › Dataflow diagram › Dimension","description":"","searchText":"reference user interface dataflow diagram dimension overview dimension is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support dimension. how to access navigation tree not direct. use the architecture diagram view. toolbar not direct. use the architecture diagram or the related detail page. diagram architecture -> dimension node or related context-menu command visual element architecture -> dimension screen overview the dimension diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 dimension visible label, button, tab, or grid header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 preview data visible label, button, tab, or grid header defined in the source-backed xaml. 5 object groups group-related control or command defined in the source-backed ui. related topics export fact"}
,{"id":386694025436,"name":"Import","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-import","breadcrumb":"Reference › User Interface › Dataflow diagram › Import","description":"","searchText":"reference user interface dataflow diagram import overview import is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support import. how to access navigation tree not direct. use the architecture diagram view. toolbar etl -> imports diagram architecture -> import node or related context-menu command visual element architecture -> import screen overview the import diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 import visible label, button, tab, or grid header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 refresh source visible field label or grid column header defined in the source-backed xaml. 5 preview data visible label, button, tab, or grid header defined in the source-backed xaml. related topics filters historization layers object groups"}
,{"id":386694025435,"name":"Historization","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-historization","breadcrumb":"Reference › User Interface › Dataflow diagram › Historization","description":"","searchText":"reference user interface dataflow diagram historization overview historization is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support historization. how to access navigation tree not direct. use the architecture diagram view. toolbar etl -> historizations diagram architecture -> historization node or related context-menu command visual element architecture -> historization screen overview the historization diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 historization visible label, button, tab, or grid header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 object groups group-related control or command defined in the source-backed ui. 5 preview data visible label, button, tab, or grid header defined in the source-backed xaml. related topics fact filters import layers"}
,{"id":386694025439,"name":"Persisting","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-persisting","breadcrumb":"Reference › User Interface › Dataflow diagram › Persisting","description":"","searchText":"reference user interface dataflow diagram persisting overview persisting is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support persisting. how to access navigation tree not direct. use the architecture diagram view. toolbar not direct in the ribbon. use the diagram add menu or related flow. diagram architecture -> persisting node or related context-menu command visual element architecture -> persisting screen overview the persisting diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 persisting visible label, button, tab, or grid header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 object groups group-related control or command defined in the source-backed ui. 5 preview data visible label, button, tab, or grid header defined in the source-backed xaml. related topics layers object groups search source"}
,{"id":386694025432,"name":"Export","type":"topic","path":"/docs/reference/user-interface/dataflow-diagram/dataflow-diagram-export","breadcrumb":"Reference › User Interface › Dataflow diagram › Export","description":"","searchText":"reference user interface dataflow diagram export overview export is represented in the analyticscreator architecture canvas and the related diagram commands defined in architecture.xaml. function the architecture page and its context menus drive diagram interactions such as locating objects, filtering the diagram, previewing data, refreshing sources, and opening related maintenance flows. access this topic was rebuilt from architecture.xaml, architecture.xaml.cs, mainwindow.xaml, and mainwindow.xaml.cs. the source shows the diagram commands and the main-window filter controls that support export. how to access navigation tree not direct. use the architecture diagram view. toolbar not direct. use the related workflow or diagram object menu. diagram architecture -> export node or related context-menu command visual element architecture -> export screen overview the export diagram behavior is represented by the architecture canvas, the diagram context menus, and the filter controls in the main window. id property description 1 export visible label, button, tab, or grid header defined in the source-backed xaml. 2 locate in tree visible label, button, tab, or grid header defined in the source-backed xaml. 3 set filter filter-related control or command defined in the source-backed ui. 4 object groups group-related control or command defined in the source-backed ui. 5 preview data visible label, button, tab, or grid header defined in the source-backed xaml. related topics dimension fact filters"}
,{"id":383509174509,"name":"Pages","type":"subsection","path":"/docs/reference/user-interface/pages","breadcrumb":"Reference › User Interface › Pages","description":"","searchText":"reference user interface pages the pages section documents the page-level object views that users open to configure analyticscreator components in detail. use these topics to understand what each page is responsible for, which object family it manages, and how page-based editing supports modeling, deployment, semantic design, and operational maintenance. available topics connector the connector page is used to add and edit source connectors. export the export page is used to add and edit data exports. olap hierarchy the olap hierarchy page is used to add and edit olap hierarchies. historization the historization page is used to add and edit historizations. import the import page is used to add and edit data imports from a source. index the index page is used to add and edit table indexes. macro the macro page is used to add and edit macros. model dimension the model dimension page is used to add and edit model dimensions. model fact the model fact page is used to add and edit model facts. table the table page is used to add and edit tables. object script the object script page is used to add and edit object scripts. package the package page is used to add and edit packages. olap partition the olap partition page is used to add and edit olap partitions. persisting the persisting page is used to add and edit transformation persistings. predefined transformation the predefined transformation page is used to add and edit predefined transformations. table reference the table reference page is used to add and edit table references. olap role the olap role page is used to add and edit olap roles. sql script the sql script page is used to add and edit sql scripts. snapshot group the snapshot group page is used to add and edit snapshot groups. snapshot the snapshot page is used to add and edit snapshots. source the source page is used to add and edit sources in a connector. star the star page is used to add and edit data mart stars. deployment the deployment page is used to add, edit, and run deployments. source refererence the source reference page is used to add and edit source references. transformation the transformation page is used to add and edit transformations. users in user group the users in user group page is used to add and edit users in a user group. how to use this section start with core implementation pages such as connector, source, table, transformation, and package when you need to configure the main warehouse objects. use model dimension, model fact, olap hierarchy, olap partition, and olap role for analytical and semantic model structures. use persisting, predefined transformation, sql script, snapshot, and snapshot group for implementation behavior and reusable runtime structures. use deployment, table reference, source refererence, and users in user group when the task involves release management, object relationships, or access organization. key takeaway the pages section maps analyticscreator's object-specific editing pages to the responsibilities they control, helping users choose the right page for the task at hand."}
,{"id":386694025444,"name":"Connector","type":"topic","path":"/docs/reference/user-interface/pages/pages-connector","breadcrumb":"Reference › User Interface › Pages › Connector","description":"","searchText":"reference user interface pages connector overview connector is implemented as a detail page in detailconnectors.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for connector. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailconnectors.xaml and detailconnectors.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree connectors -> open a connector toolbar sources -> connectors diagram not direct. open the related detail page. visual element detailconnectors screen overview the connector page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 connector visible field label or grid column header defined in the source-backed xaml. 2 add encrypted string visible label, button, tab, or grid header defined in the source-backed xaml. 3 connector name visible field label or grid column header defined in the source-backed xaml. 4 connector type visible field label or grid column header defined in the source-backed xaml. 5 azure source type visible field label or grid column header defined in the source-backed xaml. 6 do not store connection string in cfg.ssis configurations visible label, button, tab, or grid header defined in the source-backed xaml. 7 connection string visible label, button, tab, or grid header defined in the source-backed xaml. 8 url visible label, button, tab, or grid header defined in the source-backed xaml. 9 authentication visible label, button, tab, or grid header defined in the source-backed xaml. 10 login visible field label or grid column header defined in the source-backed xaml. 11 password visible field label or grid column header defined in the source-backed xaml. 12 template visible label, button, tab, or grid header defined in the source-backed xaml. related topics deployment export"}
,{"id":386694025446,"name":"Export","type":"topic","path":"/docs/reference/user-interface/pages/pages-export","breadcrumb":"Reference › User Interface › Pages › Export","description":"","searchText":"reference user interface pages export overview export is implemented as a detail page in detailexport.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for export. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailexport.xaml and detailexport.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree export -> open an export toolbar not confirmed in the ribbon. use the related export flow. diagram not direct. open the related detail page. visual element detailexport screen overview the export page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 main tab header defined in the source-backed xaml. 2 source name visible field label or grid column header defined in the source-backed xaml. 3 target name visible field label or grid column header defined in the source-backed xaml. 4 description visible field label or grid column header defined in the source-backed xaml. 5 ssis statement visible label, button, tab, or grid header defined in the source-backed xaml. 6 variable visible label, button, tab, or grid header defined in the source-backed xaml. 7 type visible field label or grid column header defined in the source-backed xaml. 8 expression visible label, button, tab, or grid header defined in the source-backed xaml. 9 initial value visible label, button, tab, or grid header defined in the source-backed xaml. 10 scripts visible label, button, tab, or grid header defined in the source-backed xaml. 11 options tab header defined in the source-backed xaml. 12 export visible label, button, tab, or grid header defined in the source-backed xaml. related topics connector deployment historization import"}
,{"id":386694025454,"name":"OLAP Hierarchy","type":"topic","path":"/docs/reference/user-interface/pages/pages-olap-hierarchy","breadcrumb":"Reference › User Interface › Pages › OLAP Hierarchy","description":"","searchText":"reference user interface pages olap hierarchy overview olap hierarchy is implemented as a detail page in detailhierarchies.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for olap hierarchy. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailhierarchies.xaml and detailhierarchies.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree hierarchies -> open a hierarchy toolbar data mart -> hierarchies diagram not direct. open the related detail page. visual element detailhierarchies screen overview the olap hierarchy page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 column visible label, button, tab, or grid header defined in the source-backed xaml. 2 seqnr visible label, button, tab, or grid header defined in the source-backed xaml. 3 name visible field label or grid column header defined in the source-backed xaml. 4 description visible field label or grid column header defined in the source-backed xaml. 5 hierarchy details visible field label or grid column header defined in the source-backed xaml. 6 schema visible field label or grid column header defined in the source-backed xaml. 7 table visible field label or grid column header defined in the source-backed xaml. 8 hierarchy name visible field label or grid column header defined in the source-backed xaml. 9 cancel closes the screen without saving changes. 10 save saves the current record. related topics model fact object script olap partition olap role"}
,{"id":386694025447,"name":"Historization","type":"topic","path":"/docs/reference/user-interface/pages/pages-historization","breadcrumb":"Reference › User Interface › Pages › Historization","description":"","searchText":"reference user interface pages historization overview historization is implemented as a detail page in detailhist.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for historization. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailhist.xaml and detailhist.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree historization -> open a historization toolbar etl -> historizations diagram not direct. open the related detail page. visual element detailhist screen overview the historization page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 definition visible label, button, tab, or grid header defined in the source-backed xaml. 2 column name visible field label or grid column header defined in the source-backed xaml. 3 scd type visible field label or grid column header defined in the source-backed xaml. 4 empty value visible label, button, tab, or grid header defined in the source-backed xaml. 5 last value as empty value visible label, button, tab, or grid header defined in the source-backed xaml. 6 statement visible label, button, tab, or grid header defined in the source-backed xaml. 7 data type visible field label or grid column header defined in the source-backed xaml. 8 maxlength visible label, button, tab, or grid header defined in the source-backed xaml. 9 numscale visible label, button, tab, or grid header defined in the source-backed xaml. 10 numprec visible label, button, tab, or grid header defined in the source-backed xaml. 11 variable visible label, button, tab, or grid header defined in the source-backed xaml. 12 type visible field label or grid column header defined in the source-backed xaml. related topics deployment export import index"}
,{"id":386694025448,"name":"Import","type":"topic","path":"/docs/reference/user-interface/pages/pages-import","breadcrumb":"Reference › User Interface › Pages › Import","description":"","searchText":"reference user interface pages import overview import is implemented as a detail page in detailimp.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for import. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailimp.xaml and detailimp.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree import -> open an import toolbar etl -> imports diagram not direct. open the related detail page. visual element detailimp screen overview the import page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 main tab header defined in the source-backed xaml. 2 source name visible field label or grid column header defined in the source-backed xaml. 3 target name visible field label or grid column header defined in the source-backed xaml. 4 description visible field label or grid column header defined in the source-backed xaml. 5 ssis statement visible label, button, tab, or grid header defined in the source-backed xaml. 6 variable visible label, button, tab, or grid header defined in the source-backed xaml. 7 type visible field label or grid column header defined in the source-backed xaml. 8 expression visible label, button, tab, or grid header defined in the source-backed xaml. 9 initial value visible label, button, tab, or grid header defined in the source-backed xaml. 10 scripts visible label, button, tab, or grid header defined in the source-backed xaml. 11 options tab header defined in the source-backed xaml. 12 import visible label, button, tab, or grid header defined in the source-backed xaml. related topics export historization index macro"}
,{"id":386694025449,"name":"Index","type":"topic","path":"/docs/reference/user-interface/pages/pages-index","breadcrumb":"Reference › User Interface › Pages › Index","description":"","searchText":"reference user interface pages index overview index is implemented as a detail page in detailindexes.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for index. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailindexes.xaml and detailindexes.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree indexes -> open an index toolbar dwh -> indexes diagram not direct. open the related detail page. visual element detailindexes screen overview the index page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 column visible label, button, tab, or grid header defined in the source-backed xaml. 2 position visible label, button, tab, or grid header defined in the source-backed xaml. 3 is descending visible label, button, tab, or grid header defined in the source-backed xaml. 4 include only visible label, button, tab, or grid header defined in the source-backed xaml. 5 index details visible label, button, tab, or grid header defined in the source-backed xaml. 6 schema visible field label or grid column header defined in the source-backed xaml. 7 table visible field label or grid column header defined in the source-backed xaml. 8 index name visible field label or grid column header defined in the source-backed xaml. 9 description visible field label or grid column header defined in the source-backed xaml. 10 compression type visible field label or grid column header defined in the source-backed xaml. 11 is unique visible label, button, tab, or grid header defined in the source-backed xaml. 12 is clustered visible label, button, tab, or grid header defined in the source-backed xaml. related topics historization import macro model dimension"}
,{"id":386694025450,"name":"Macro","type":"topic","path":"/docs/reference/user-interface/pages/pages-macro","breadcrumb":"Reference › User Interface › Pages › Macro","description":"","searchText":"reference user interface pages macro overview macro is implemented as a detail page in detailmacros.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for macro. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailmacros.xaml and detailmacros.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree macros -> open a macro toolbar dwh -> macros diagram not direct. open the related detail page. visual element detailmacros screen overview the macro page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 macro visible label, button, tab, or grid header defined in the source-backed xaml. 2 macro name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 language visible label, button, tab, or grid header defined in the source-backed xaml. 5 referenced table visible field label or grid column header defined in the source-backed xaml. 6 statement visible label, button, tab, or grid header defined in the source-backed xaml. 7 cancel closes the screen without saving changes. 8 save saves the current record. related topics import index model dimension model fact"}
,{"id":386694025451,"name":"Model Dimension","type":"topic","path":"/docs/reference/user-interface/pages/pages-model-dimension","breadcrumb":"Reference › User Interface › Pages › Model Dimension","description":"","searchText":"reference user interface pages model dimension overview model dimension is implemented as a detail page in detailmoddimensions.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for model dimension. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailmoddimensions.xaml and detailmoddimensions.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree models -> open a model dimension toolbar data mart -> models diagram not direct. open the related detail page. visual element detailmoddimensions screen overview the model dimension page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 name visible field label or grid column header defined in the source-backed xaml. 2 friendly name visible field label or grid column header defined in the source-backed xaml. 3 descrption visible label, button, tab, or grid header defined in the source-backed xaml. 4 iskey visible label, button, tab, or grid header defined in the source-backed xaml. 5 model visible field label or grid column header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 historicized visible label, button, tab, or grid header defined in the source-backed xaml. 8 attributes visible label, button, tab, or grid header defined in the source-backed xaml. 9 cancel closes the screen without saving changes. 10 save saves the current record. related topics index macro model fact object script"}
,{"id":386694025452,"name":"Model Fact","type":"topic","path":"/docs/reference/user-interface/pages/pages-model-fact","breadcrumb":"Reference › User Interface › Pages › Model Fact","description":"","searchText":"reference user interface pages model fact overview model fact is implemented as a detail page in detailmodfacts.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for model fact. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailmodfacts.xaml and detailmodfacts.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree models -> open a model fact toolbar data mart -> models diagram not direct. open the related detail page. visual element detailmodfacts screen overview the model fact page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 name visible field label or grid column header defined in the source-backed xaml. 2 friendly name visible field label or grid column header defined in the source-backed xaml. 3 descrption visible label, button, tab, or grid header defined in the source-backed xaml. 4 dimension visible label, button, tab, or grid header defined in the source-backed xaml. 5 model visible field label or grid column header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 cancel closes the screen without saving changes. 8 save saves the current record. related topics macro model dimension object script olap hierarchy"}
,{"id":386694026426,"name":"Table","type":"topic","path":"/docs/reference/user-interface/pages/pages-table","breadcrumb":"Reference › User Interface › Pages › Table","description":"","searchText":"reference user interface pages table overview table is implemented as a detail page in detailobjects.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for table. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailobjects.xaml and detailobjects.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree tables -> open a table toolbar dwh -> tables diagram not direct. open the related detail page. visual element detailobjects screen overview the table page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 columns visible label, button, tab, or grid header defined in the source-backed xaml. 2 add.col visible label, button, tab, or grid header defined in the source-backed xaml. 3 column name visible field label or grid column header defined in the source-backed xaml. 4 data type visible field label or grid column header defined in the source-backed xaml. 5 maxlength visible label, button, tab, or grid header defined in the source-backed xaml. 6 numprec visible label, button, tab, or grid header defined in the source-backed xaml. 7 numscale visible label, button, tab, or grid header defined in the source-backed xaml. 8 nullable visible label, button, tab, or grid header defined in the source-backed xaml. 9 pkordinalpos visible label, button, tab, or grid header defined in the source-backed xaml. 10 default visible label, button, tab, or grid header defined in the source-backed xaml. 11 friendlyname visible field label or grid column header defined in the source-backed xaml. 12 olap reference visible field label or grid column header defined in the source-backed xaml. related topics sql script star table reference transformation"}
,{"id":386694025453,"name":"Object script","type":"topic","path":"/docs/reference/user-interface/pages/pages-object-script","breadcrumb":"Reference › User Interface › Pages › Object script","description":"","searchText":"reference user interface pages object script overview object script is implemented as a detail page in detailobjectscripts.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for object script. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailobjectscripts.xaml and detailobjectscripts.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree object scripts -> open an object script toolbar not direct. use the object scripts tree node or list. diagram not direct. open the related detail page. visual element detailobjectscripts screen overview the object script page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 object script visible label, button, tab, or grid header defined in the source-backed xaml. 2 paramnr visible label, button, tab, or grid header defined in the source-backed xaml. 3 parameter visible label, button, tab, or grid header defined in the source-backed xaml. 4 default value visible label, button, tab, or grid header defined in the source-backed xaml. 5 script name visible field label or grid column header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 object visible label, button, tab, or grid header defined in the source-backed xaml. 8 parameters visible label, button, tab, or grid header defined in the source-backed xaml. 9 statement visible label, button, tab, or grid header defined in the source-backed xaml. 10 first parameter of the object-related scripts is always the object id visible label, button, tab, or grid header defined in the source-backed xaml. 11 check visible label, button, tab, or grid header defined in the source-backed xaml. 12 cancel closes the screen without saving changes. related topics model dimension model fact olap hierarchy olap partition"}
,{"id":386694025457,"name":"Package","type":"topic","path":"/docs/reference/user-interface/pages/pages-package","breadcrumb":"Reference › User Interface › Pages › Package","description":"","searchText":"reference user interface pages package overview package is implemented as a detail page in detailpackages.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for package. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailpackages.xaml and detailpackages.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree packages -> open a package toolbar etl -> packages diagram not direct. open the related detail page. visual element detailpackages screen overview the package page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 package visible field label or grid column header defined in the source-backed xaml. 2 content visible label, button, tab, or grid header defined in the source-backed xaml. 3 include visible label, button, tab, or grid header defined in the source-backed xaml. 4 interrupt on error visible label, button, tab, or grid header defined in the source-backed xaml. 5 retry attempts visible label, button, tab, or grid header defined in the source-backed xaml. 6 retry interval (min) visible label, button, tab, or grid header defined in the source-backed xaml. 7 depends on visible label, button, tab, or grid header defined in the source-backed xaml. 8 add creates a new item or starts the add flow defined in the screen. 9 remove visible label, button, tab, or grid header defined in the source-backed xaml. 10 package name visible field label or grid column header defined in the source-backed xaml. 11 package type visible field label or grid column header defined in the source-backed xaml. 12 manually created visible label, button, tab, or grid header defined in the source-backed xaml. related topics olap partition olap role persisting predefined transformation"}
,{"id":386694025455,"name":"OLAP Partition","type":"topic","path":"/docs/reference/user-interface/pages/pages-olap-partition","breadcrumb":"Reference › User Interface › Pages › OLAP Partition","description":"","searchText":"reference user interface pages olap partition overview olap partition is implemented as a detail page in detailpartitions.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for olap partition. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailpartitions.xaml and detailpartitions.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree partitions -> open a partition toolbar data mart -> partitions diagram not direct. open the related detail page. visual element detailpartitions screen overview the olap partition page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 partition visible field label or grid column header defined in the source-backed xaml. 2 partition name visible field label or grid column header defined in the source-backed xaml. 3 table visible field label or grid column header defined in the source-backed xaml. 4 slice visible label, button, tab, or grid header defined in the source-backed xaml. 5 sql visible label, button, tab, or grid header defined in the source-backed xaml. 6 cancel closes the screen without saving changes. 7 save saves the current record. related topics object script olap hierarchy olap role package"}
,{"id":386694025458,"name":"Persisting","type":"topic","path":"/docs/reference/user-interface/pages/pages-persisting","breadcrumb":"Reference › User Interface › Pages › Persisting","description":"","searchText":"reference user interface pages persisting overview persisting is implemented as a detail page in detailpers.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for persisting. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailpers.xaml and detailpers.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree persisting -> open a persisting object toolbar not confirmed in the ribbon. open from the related persisting flow. diagram not direct. open the related detail page. visual element detailpers screen overview the persisting page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 procedure visible label, button, tab, or grid header defined in the source-backed xaml. 2 scripts visible label, button, tab, or grid header defined in the source-backed xaml. 3 persisting visible label, button, tab, or grid header defined in the source-backed xaml. 4 package visible field label or grid column header defined in the source-backed xaml. 5 type visible field label or grid column header defined in the source-backed xaml. 6 incremental column visible label, button, tab, or grid header defined in the source-backed xaml. 7 update statistics visible label, button, tab, or grid header defined in the source-backed xaml. 8 partition switching visible field label or grid column header defined in the source-backed xaml. 9 renaming visible label, button, tab, or grid header defined in the source-backed xaml. 10 use transaction visible label, button, tab, or grid header defined in the source-backed xaml. 11 logging visible label, button, tab, or grid header defined in the source-backed xaml. 12 remove duplicates visible label, button, tab, or grid header defined in the source-backed xaml. related topics olap role package predefined transformation snapshot"}
,{"id":386694025459,"name":"Predefined transformation","type":"topic","path":"/docs/reference/user-interface/pages/pages-predefined-transformation","breadcrumb":"Reference › User Interface › Pages › Predefined transformation","description":"","searchText":"reference user interface pages predefined transformation overview predefined transformation is implemented as a detail page in detailpredefinedtransformations.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for predefined transformation. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailpredefinedtransformations.xaml and detailpredefinedtransformations.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree predefined transformations -> open an item toolbar dwh -> predefined trans. diagram not direct. open the related detail page. visual element detailpredefinedtransformations screen overview the predefined transformation page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 predefined transformations visible label, button, tab, or grid header defined in the source-backed xaml. 2 name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 check statement visible label, button, tab, or grid header defined in the source-backed xaml. 5 transformation statement visible label, button, tab, or grid header defined in the source-backed xaml. 6 evaluated statement visible label, button, tab, or grid header defined in the source-backed xaml. 7 allowed keywords visible label, button, tab, or grid header defined in the source-backed xaml. 8 evaluate visible label, button, tab, or grid header defined in the source-backed xaml. 9 cancel closes the screen without saving changes. 10 save saves the current record. related topics package persisting snapshot snapshot group"}
,{"id":386694026427,"name":"Table reference","type":"topic","path":"/docs/reference/user-interface/pages/pages-table-reference","breadcrumb":"Reference › User Interface › Pages › Table reference","description":"","searchText":"reference user interface pages table reference overview table reference is implemented as a detail page in detailreferences.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for table reference. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailreferences.xaml and detailreferences.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree table references -> open a reference toolbar dwh -> references diagram not direct. open the related detail page. visual element detailreferences screen overview the table reference page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 column1 visible label, button, tab, or grid header defined in the source-backed xaml. 2 statement1 visible label, button, tab, or grid header defined in the source-backed xaml. 3 column2 visible label, button, tab, or grid header defined in the source-backed xaml. 4 statement2 visible label, button, tab, or grid header defined in the source-backed xaml. 5 schema visible field label or grid column header defined in the source-backed xaml. 6 transformation visible label, button, tab, or grid header defined in the source-backed xaml. 7 cardinality visible label, button, tab, or grid header defined in the source-backed xaml. 8 join visible label, button, tab, or grid header defined in the source-backed xaml. 9 table 1 visible field label or grid column header defined in the source-backed xaml. 10 table 2 visible field label or grid column header defined in the source-backed xaml. 11 description visible field label or grid column header defined in the source-backed xaml. 12 parentdescription visible field label or grid column header defined in the source-backed xaml. related topics star table transformation users in user group"}
,{"id":386694025456,"name":"OLAP role","type":"topic","path":"/docs/reference/user-interface/pages/pages-olap-role","breadcrumb":"Reference › User Interface › Pages › OLAP role","description":"","searchText":"reference user interface pages olap role overview olap role is implemented as a detail page in detailroles.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for olap role. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailroles.xaml and detailroles.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree roles -> open a role toolbar data mart -> roles diagram not direct. open the related detail page. visual element detailroles screen overview the olap role page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 login visible field label or grid column header defined in the source-backed xaml. 2 tabular cube visible label, button, tab, or grid header defined in the source-backed xaml. 3 table visible field label or grid column header defined in the source-backed xaml. 4 disable visible label, button, tab, or grid header defined in the source-backed xaml. 5 dax filter filter-related control or command defined in the source-backed ui. 6 multidimensional cube visible label, button, tab, or grid header defined in the source-backed xaml. 7 star visible label, button, tab, or grid header defined in the source-backed xaml. 8 allowread visible label, button, tab, or grid header defined in the source-backed xaml. 9 allowwrite visible label, button, tab, or grid header defined in the source-backed xaml. 10 allowdrillthrough visible label, button, tab, or grid header defined in the source-backed xaml. 11 allowprocess visible label, button, tab, or grid header defined in the source-backed xaml. 12 allow reading of cube content visible label, button, tab, or grid header defined in the source-backed xaml. related topics olap hierarchy olap partition package persisting"}
,{"id":386694025464,"name":"SQL Script","type":"topic","path":"/docs/reference/user-interface/pages/pages-sql-script","breadcrumb":"Reference › User Interface › Pages › SQL Script","description":"","searchText":"reference user interface pages sql script overview sql script is implemented as a detail page in detailscript.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for sql script. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailscript.xaml and detailscript.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree sql scripts -> open a script toolbar etl -> scripts diagram not direct. open the related detail page. visual element detailscript screen overview the sql script page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 package visible field label or grid column header defined in the source-backed xaml. 2 run visible label, button, tab, or grid header defined in the source-backed xaml. 3 script type visible field label or grid column header defined in the source-backed xaml. 4 name visible field label or grid column header defined in the source-backed xaml. 5 description visible field label or grid column header defined in the source-backed xaml. 6 sequence number visible label, button, tab, or grid header defined in the source-backed xaml. 7 inactive visible label, button, tab, or grid header defined in the source-backed xaml. 8 original visible label, button, tab, or grid header defined in the source-backed xaml. 9 parsed visible label, button, tab, or grid header defined in the source-backed xaml. 10 cancel closes the screen without saving changes. 11 save saves the current record. related topics source source refererence star table"}
,{"id":386694025461,"name":"Snapshot group","type":"topic","path":"/docs/reference/user-interface/pages/pages-snapshot-group","breadcrumb":"Reference › User Interface › Pages › Snapshot group","description":"","searchText":"reference user interface pages snapshot group overview snapshot group is implemented as a detail page in detailsnapshotgroup.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for snapshot group. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailsnapshotgroup.xaml and detailsnapshotgroup.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree snapshot groups -> open a snapshot group toolbar not direct. use the snapshot groups tree node. diagram not direct. open the related detail page. visual element detailsnapshotgroup screen overview the snapshot group page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 snapshot visible field label or grid column header defined in the source-backed xaml. 2 group name group-related control or command defined in the source-backed ui. 3 description visible field label or grid column header defined in the source-backed xaml. 4 cancel closes the screen without saving changes. 5 save saves the current record. related topics predefined transformation snapshot source source refererence"}
,{"id":386694025460,"name":"Snapshot","type":"topic","path":"/docs/reference/user-interface/pages/pages-snapshot","breadcrumb":"Reference › User Interface › Pages › Snapshot","description":"","searchText":"reference user interface pages snapshot overview snapshot is implemented as a detail page in detailsnapshots.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for snapshot. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailsnapshots.xaml and detailsnapshots.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree snapshots -> open a snapshot toolbar dwh -> snapshots diagram not direct. open the related detail page. visual element detailsnapshots screen overview the snapshot page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 snapshot visible field label or grid column header defined in the source-backed xaml. 2 snapshot name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 sql visible label, button, tab, or grid header defined in the source-backed xaml. 5 cancel closes the screen without saving changes. 6 save saves the current record. related topics persisting predefined transformation snapshot group source"}
,{"id":386694025462,"name":"Source","type":"topic","path":"/docs/reference/user-interface/pages/pages-source","breadcrumb":"Reference › User Interface › Pages › Source","description":"","searchText":"reference user interface pages source overview source is implemented as a detail page in detailsource.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for source. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailsource.xaml and detailsource.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree sources -> open a source toolbar sources -> sources diagram not direct. open the related detail page. visual element detailsource screen overview the source page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 definition visible label, button, tab, or grid header defined in the source-backed xaml. 2 column name visible field label or grid column header defined in the source-backed xaml. 3 ordernr visible label, button, tab, or grid header defined in the source-backed xaml. 4 data type visible field label or grid column header defined in the source-backed xaml. 5 maxlength visible label, button, tab, or grid header defined in the source-backed xaml. 6 numprec visible label, button, tab, or grid header defined in the source-backed xaml. 7 numscale visible label, button, tab, or grid header defined in the source-backed xaml. 8 nullable visible label, button, tab, or grid header defined in the source-backed xaml. 9 pk ordinal position visible label, button, tab, or grid header defined in the source-backed xaml. 10 anonymize visible label, button, tab, or grid header defined in the source-backed xaml. 11 friendly name visible field label or grid column header defined in the source-backed xaml. 12 display folder visible label, button, tab, or grid header defined in the source-backed xaml. related topics snapshot snapshot group source refererence sql script"}
,{"id":386694025465,"name":"Star","type":"topic","path":"/docs/reference/user-interface/pages/pages-star","breadcrumb":"Reference › User Interface › Pages › Star","description":"","searchText":"reference user interface pages star overview star is implemented as a detail page in detailstars.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for star. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailstars.xaml and detailstars.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree stars -> open a star toolbar data mart -> stars diagram not direct. open the related detail page. visual element detailstars screen overview the star page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 star visible label, button, tab, or grid header defined in the source-backed xaml. 2 multidimensional visible label, button, tab, or grid header defined in the source-backed xaml. 3 tabular visible label, button, tab, or grid header defined in the source-backed xaml. 4 star name visible field label or grid column header defined in the source-backed xaml. 5 galaxy visible label, button, tab, or grid header defined in the source-backed xaml. 6 schema visible field label or grid column header defined in the source-backed xaml. 7 order in diagram visible label, button, tab, or grid header defined in the source-backed xaml. 8 description visible field label or grid column header defined in the source-backed xaml. 9 mdx visible label, button, tab, or grid header defined in the source-backed xaml. 10 cancel closes the screen without saving changes. 11 save saves the current record. related topics source refererence sql script table table reference"}
,{"id":386694025445,"name":"Deployment","type":"topic","path":"/docs/reference/user-interface/pages/pages-deployment","breadcrumb":"Reference › User Interface › Pages › Deployment","description":"","searchText":"reference user interface pages deployment overview deployment is implemented as a detail page in newssis.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for deployment. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from newssis.xaml and newssis.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree deployments -> edit/run deployment toolbar deployment -> deployment package diagram not direct. open the related detail page. visual element newssis screen overview the deployment page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 options tab header defined in the source-backed xaml. 2 data warehouse visible label, button, tab, or grid header defined in the source-backed xaml. 3 ssis settings visible label, button, tab, or grid header defined in the source-backed xaml. 4 other files visible label, button, tab, or grid header defined in the source-backed xaml. 5 tabular olap deployment visible label, button, tab, or grid header defined in the source-backed xaml. 6 multidimensional olap deployment visible label, button, tab, or grid header defined in the source-backed xaml. 7 ssis visible label, button, tab, or grid header defined in the source-backed xaml. 8 adf2 visible label, button, tab, or grid header defined in the source-backed xaml. 9 packagename visible field label or grid column header defined in the source-backed xaml. 10 packagetype visible field label or grid column header defined in the source-backed xaml. 11 description visible field label or grid column header defined in the source-backed xaml. 12 variable visible label, button, tab, or grid header defined in the source-backed xaml. related topics connector export historization"}
,{"id":386694025463,"name":"Source refererence","type":"topic","path":"/docs/reference/user-interface/pages/pages-source-reference","breadcrumb":"Reference › User Interface › Pages › Source refererence","description":"","searchText":"reference user interface pages source refererence overview source refererence is implemented as a detail page in detailsrcreferences.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for source refererence. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailsrcreferences.xaml and detailsrcreferences.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree source references -> open a source reference toolbar sources -> references diagram not direct. open the related detail page. visual element detailsrcreferences screen overview the source refererence page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 column1 visible label, button, tab, or grid header defined in the source-backed xaml. 2 statement1 visible label, button, tab, or grid header defined in the source-backed xaml. 3 column2 visible label, button, tab, or grid header defined in the source-backed xaml. 4 statement2 visible label, button, tab, or grid header defined in the source-backed xaml. 5 source reference details visible field label or grid column header defined in the source-backed xaml. 6 cardinality visible label, button, tab, or grid header defined in the source-backed xaml. 7 join visible label, button, tab, or grid header defined in the source-backed xaml. 8 source 1 visible field label or grid column header defined in the source-backed xaml. 9 source 2 visible field label or grid column header defined in the source-backed xaml. 10 description visible field label or grid column header defined in the source-backed xaml. 11 reference statement visible field label or grid column header defined in the source-backed xaml. 12 alias visible label, button, tab, or grid header defined in the source-backed xaml. related topics snapshot group source sql script star"}
,{"id":386694026428,"name":"Transformation","type":"topic","path":"/docs/reference/user-interface/pages/pages-transformation","breadcrumb":"Reference › User Interface › Pages › Transformation","description":"","searchText":"reference user interface pages transformation overview transformation is implemented as a detail page in detailtransformations.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for transformation. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailtransformations.xaml and detailtransformations.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree transformations -> open a transformation toolbar etl -> transformations diagram not direct. open the related detail page. visual element detailtransformations screen overview the transformation page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 snapshot group group-related control or command defined in the source-backed ui. 2 snapshot visible field label or grid column header defined in the source-backed xaml. 3 definition visible label, button, tab, or grid header defined in the source-backed xaml. 4 star visible label, button, tab, or grid header defined in the source-backed xaml. 5 view name visible field label or grid column header defined in the source-backed xaml. 6 isfact visible label, button, tab, or grid header defined in the source-backed xaml. 7 filter filter-related control or command defined in the source-backed ui. 8 predifined transformation visible label, button, tab, or grid header defined in the source-backed xaml. 9 useonvault visible label, button, tab, or grid header defined in the source-backed xaml. 10 check and update columns visible label, button, tab, or grid header defined in the source-backed xaml. 11 add all columns to transformation visible label, button, tab, or grid header defined in the source-backed xaml. 12 remove all columns from transformation visible label, button, tab, or grid header defined in the source-backed xaml. related topics table table reference users in user group"}
,{"id":386694026429,"name":"Users in user group","type":"topic","path":"/docs/reference/user-interface/pages/pages-users-in-user-group","breadcrumb":"Reference › User Interface › Pages › Users in user group","description":"","searchText":"reference user interface pages users in user group overview users in user group is implemented as a detail page in detailuserroles.xaml. function the page exposes the editor fields, tabs, grids, and action buttons for users in user group. its companion code-behind applies page-specific behavior such as selection changes, save/cancel actions, and dynamic control visibility. access this topic was rebuilt from detailuserroles.xaml and detailuserroles.xaml.cs. the source defines the visible page structure and its editor actions. how to access navigation tree user groups -> open a user group toolbar options -> user groups diagram not direct. open the related detail page. visual element detailuserroles screen overview the users in user group page exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 user visible label, button, tab, or grid header defined in the source-backed xaml. 2 rights visible label, button, tab, or grid header defined in the source-backed xaml. 3 group name group-related control or command defined in the source-backed ui. 4 group members group-related control or command defined in the source-backed ui. 5 cancel closes the screen without saving changes. 6 save saves the current record. related topics table reference transformation"}
,{"id":383509396683,"name":"Lists","type":"subsection","path":"/docs/reference/user-interface/lists","breadcrumb":"Reference › User Interface › Lists","description":"","searchText":"reference user interface lists the lists section groups the list views and registry-style pages used to browse, compare, and manage collections of analyticscreator objects. use these topics when you need a whole-of-category view, want to navigate quickly to a specific definition, or need to review many related objects from one place. available topics connectors the connectors page is used to list connectors. datamart stars the datamart stars page is used to list datamart stars. deploymens the deploymens page is used to list deployments. encrypted strings the encrypted strings page is used to list and edit encrypted strings. exports the exports page is used to list data exports. galaxies the galaxies page is used to list and edit galaxies. hierarchies the hierarchies page is used to list hierarchies. historizations the historizations page is used to list historizations. imports the imports page is used to list data imports. indexes the indexes page is used to list table indexes. layers the layers page is used to list and edit layers. macros the macros page is used to list macros. models the models page is used to list and edit models. object group content the object group content page is used to list and edit obects in object groups. object scripts the object scripts page is used to list object scripts. olap roles the olap roles page is used to list olap roles. packages the packages page is used to list packages. parameters the parameters page is used to list and edit analyticscreator parameters. partitions the partitions page is used to list partitions. predefined transformations the predefined transformations page is used to list predefined transformations. schemas the schemas page is used to list and edit schemas. snapshot groups the snapshot groups page is used to list snapshot groups. snapshots the snapshots page is used to list snapshots. source references the source references page is used to list source references. sources the sources page is used to list sources. sql script the sql script page is used to list sql script. table references the table references page is used to list table references. tables the tables page is used to list tables. transformations the transformations page is used to list transformations. user groups the user groups page is used to list user groups. how to use this section start with structural lists such as connectors, layers, sources, tables, and transformations when you need a repository-wide overview. use governance and metadata lists such as parameters, indexes, schemas, source references, and table references when validating relationships or implementation rules. use analytical lists such as datamart stars, galaxies, hierarchies, models, olap roles, and partitions when working on semantic structures. use operational lists such as deploymens, packages, snapshots, snapshot groups, and user groups when managing runtime and organizational objects in bulk. key takeaway the lists section shows where analyticscreator exposes grouped object inventories for bulk browsing, comparison, and fast navigation across large repositories."}
,{"id":386688842958,"name":"Connectors","type":"topic","path":"/docs/reference/user-interface/lists/lists-connectors","breadcrumb":"Reference › User Interface › Lists › Connectors","description":"","searchText":"reference user interface lists connectors overview connectors is implemented as a searchable list page in searchconnectors.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchconnectors.xaml and searchconnectors.xaml.cs. the source defines the filter controls, grid headers, and list actions for connectors. how to access navigation tree connectors -> list connectors toolbar sources -> connectors diagram not direct. use the list page. visual element searchconnectors screen overview the connectors list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 connectorname visible field label or grid column header defined in the source-backed xaml. 3 connectortype visible field label or grid column header defined in the source-backed xaml. 4 connectionstring visible label, button, tab, or grid header defined in the source-backed xaml. 5 search runs the filter action defined for this screen. 6 delete deletes the selected item. 7 new creates a new item or starts the add flow defined in the screen. related topics datamart stars deploymens"}
,{"id":386688842959,"name":"Datamart stars","type":"topic","path":"/docs/reference/user-interface/lists/lists-datamart-stars","breadcrumb":"Reference › User Interface › Lists › Datamart stars","description":"","searchText":"reference user interface lists datamart stars overview datamart stars is implemented as a searchable list page in searchstars.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchstars.xaml and searchstars.xaml.cs. the source defines the filter controls, grid headers, and list actions for datamart stars. how to access navigation tree stars -> list stars toolbar data mart -> stars diagram not direct. use the list page. visual element searchstars screen overview the datamart stars list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 galaxy visible label, button, tab, or grid header defined in the source-backed xaml. 4 schema visible field label or grid column header defined in the source-backed xaml. 5 order in diagram visible label, button, tab, or grid header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 search runs the filter action defined for this screen. 8 delete deletes the selected item. 9 new creates a new item or starts the add flow defined in the screen. related topics connectors deploymens exports"}
,{"id":386688842960,"name":"Deploymens","type":"topic","path":"/docs/reference/user-interface/lists/lists-deploymens","breadcrumb":"Reference › User Interface › Lists › Deploymens","description":"","searchText":"reference user interface lists deploymens overview deploymens is implemented as a searchable list page in searchdeployments.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchdeployments.xaml and searchdeployments.xaml.cs. the source defines the filter controls, grid headers, and list actions for deploymens. how to access navigation tree deployments -> list deployments toolbar not direct. use the navigation tree deployments node. diagram not direct. use the list page. visual element searchdeployments screen overview the deploymens list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 new creates a new item or starts the add flow defined in the screen. 6 delete deletes the selected item. related topics connectors datamart stars exports galaxies"}
,{"id":386688842961,"name":"Encrypted strings","type":"topic","path":"/docs/reference/user-interface/lists/lists-encrypted-strings","breadcrumb":"Reference › User Interface › Lists › Encrypted strings","description":"","searchText":"reference user interface lists encrypted strings overview the encrypted strings page is used to list and edit encrypted strings. function this page is used to list and maintain encrypted strings. access the page can be opened from the toolbar. how to access navigation tree not confirmed. toolbar options->encrypted strings diagram not confirmed. visual element not confirmed. screen overview candidate screen coverage to be validated during the approval step. encrypted strings legacy screenshot 1 id property description 1 focus area encrypted strings legacy screenshot 1 2 source legacy backup candidate pending validation 3 next action confirm the screenshot matches the current ui before implementation. related topics connectors datamart stars deploymens exports"}
,{"id":386688842962,"name":"Exports","type":"topic","path":"/docs/reference/user-interface/lists/lists-exports","breadcrumb":"Reference › User Interface › Lists › Exports","description":"","searchText":"reference user interface lists exports overview exports is implemented as a searchable list page in searchexports.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchexports.xaml and searchexports.xaml.cs. the source defines the filter controls, grid headers, and list actions for exports. how to access navigation tree not confirmed. toolbar not confirmed in the ribbon. use the related workflow or existing tree entry. diagram not direct. use the list page. visual element searchexports screen overview the exports list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 table visible field label or grid column header defined in the source-backed xaml. 3 source visible field label or grid column header defined in the source-backed xaml. 4 package visible field label or grid column header defined in the source-backed xaml. 5 description visible field label or grid column header defined in the source-backed xaml. 6 filter filter-related control or command defined in the source-backed ui. 7 impsql visible label, button, tab, or grid header defined in the source-backed xaml. 8 updatestatistics visible label, button, tab, or grid header defined in the source-backed xaml. 9 uselogging visible label, button, tab, or grid header defined in the source-backed xaml. 10 search runs the filter action defined for this screen. related topics datamart stars deploymens galaxies hierarchies"}
,{"id":386688842963,"name":"Galaxies","type":"topic","path":"/docs/reference/user-interface/lists/lists-galaxies","breadcrumb":"Reference › User Interface › Lists › Galaxies","description":"","searchText":"reference user interface lists galaxies overview galaxies is implemented as a searchable list page in configgalaxies.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. access this topic was rebuilt from configgalaxies.xaml and configgalaxies.xaml.cs. the source defines the filter controls, grid headers, and list actions for galaxies. how to access navigation tree galaxies -> list galaxies toolbar data mart -> galaxies diagram not direct. use the list page. visual element configgalaxies screen overview the galaxies list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 save saves the current record. 6 cancel closes the screen without saving changes. related topics deploymens exports hierarchies indexes"}
,{"id":386688842964,"name":"Hierarchies","type":"topic","path":"/docs/reference/user-interface/lists/lists-hierarchies","breadcrumb":"Reference › User Interface › Lists › Hierarchies","description":"","searchText":"reference user interface lists hierarchies overview hierarchies is implemented as a searchable list page in searchhierarchies.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchhierarchies.xaml and searchhierarchies.xaml.cs. the source defines the filter controls, grid headers, and list actions for hierarchies. how to access navigation tree hierarchies -> list hierarchies toolbar data mart -> hierarchies diagram not direct. use the list page. visual element searchhierarchies screen overview the hierarchies list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 schema visible field label or grid column header defined in the source-backed xaml. 3 table visible field label or grid column header defined in the source-backed xaml. 4 hierarchy visible field label or grid column header defined in the source-backed xaml. 5 clustered visible label, button, tab, or grid header defined in the source-backed xaml. 6 search runs the filter action defined for this screen. 7 new creates a new item or starts the add flow defined in the screen. 8 delete deletes the selected item. related topics exports galaxies indexes layers"}
,{"id":386688842965,"name":"Historizations","type":"topic","path":"/docs/reference/user-interface/lists/lists-historizations","breadcrumb":"Reference › User Interface › Lists › Historizations","description":"","searchText":"reference user interface lists historizations overview the historizations page is used to list historizations. function this page is used to list historizations. access the page can be opened from the toolbar. how to access navigation tree not confirmed. toolbar etl->historizations diagram not confirmed. visual element not confirmed. screen overview candidate screen coverage to be validated during the approval step. historizations legacy screenshot 1 id property description 1 hist table name of the source table configured for historization 2 package etl package assigned to manage historization for this table 3 hist type type of historization applied (e.g., scd type, custom tracking) 4 do not close if checked, the previous record is not closed even when changes occur 5 inssql insert sql is generated for historized records 6 delsql delete sql logic is executed for historized records 7 updatestatistics enables sql server to update statistics after historization 8 uselogging logs each historization step for auditing or troubleshooting 9 delete removes historization configuration from the selected table 10 new opens a new historization entry form for manual creation related topics connectors datamart stars deploymens encrypted strings"}
,{"id":386688842966,"name":"Imports","type":"topic","path":"/docs/reference/user-interface/lists/lists-imports","breadcrumb":"Reference › User Interface › Lists › Imports","description":"","searchText":"reference user interface lists imports overview the imports page is used to list data imports. function this page is used to list data imports. access the page can be opened from the toolbar. how to access navigation tree not confirmed. toolbar etl->imports diagram not confirmed. visual element not confirmed. screen overview id property description 1 table the name of the source table to be imported 2 source the actual source name from the system 3 package associated import package the table belongs to 4 description optional notes about the table's purpose or contents 5 updatestatistics specifies if sql server statistics should be updated after import 6 uselogging enables logging for the import process of this table 7 delete removes the selected import entry 8 new creates a new import table configuration related topics connectors datamart stars deploymens encrypted strings"}
,{"id":386688842967,"name":"Indexes","type":"topic","path":"/docs/reference/user-interface/lists/lists-indexes","breadcrumb":"Reference › User Interface › Lists › Indexes","description":"","searchText":"reference user interface lists indexes overview indexes is implemented as a searchable list page in searchindexes.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchindexes.xaml and searchindexes.xaml.cs. the source defines the filter controls, grid headers, and list actions for indexes. how to access navigation tree indexes -> list indexes toolbar dwh -> indexes diagram not direct. use the list page. visual element searchindexes screen overview the indexes list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 schema visible field label or grid column header defined in the source-backed xaml. 3 table visible field label or grid column header defined in the source-backed xaml. 4 index visible label, button, tab, or grid header defined in the source-backed xaml. 5 clustered visible label, button, tab, or grid header defined in the source-backed xaml. 6 unique visible label, button, tab, or grid header defined in the source-backed xaml. 7 primary key visible label, button, tab, or grid header defined in the source-backed xaml. 8 search runs the filter action defined for this screen. 9 new creates a new item or starts the add flow defined in the screen. 10 delete deletes the selected item. related topics galaxies hierarchies layers macros"}
,{"id":386688842968,"name":"Layers","type":"topic","path":"/docs/reference/user-interface/lists/lists-layers","breadcrumb":"Reference › User Interface › Lists › Layers","description":"","searchText":"reference user interface lists layers overview layers is implemented as a searchable list page in configlayers.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. access this topic was rebuilt from configlayers.xaml and configlayers.xaml.cs. the source defines the filter controls, grid headers, and list actions for layers. how to access navigation tree layers -> list layers toolbar dwh -> layers diagram not direct. use the list page. visual element configlayers screen overview the layers list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 seqnr visible label, button, tab, or grid header defined in the source-backed xaml. 4 description visible field label or grid column header defined in the source-backed xaml. 5 search runs the filter action defined for this screen. 6 save saves the current record. 7 cancel closes the screen without saving changes. related topics hierarchies indexes macros models"}
,{"id":386688842969,"name":"Macros","type":"topic","path":"/docs/reference/user-interface/lists/lists-macros","breadcrumb":"Reference › User Interface › Lists › Macros","description":"","searchText":"reference user interface lists macros overview macros is implemented as a searchable list page in searchmacros.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchmacros.xaml and searchmacros.xaml.cs. the source defines the filter controls, grid headers, and list actions for macros. how to access navigation tree macros -> list macros toolbar dwh -> macros diagram not direct. use the list page. visual element searchmacros screen overview the macros list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 language visible label, button, tab, or grid header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 delete deletes the selected item. 6 new creates a new item or starts the add flow defined in the screen. related topics indexes layers models object group content"}
,{"id":386688842970,"name":"Models","type":"topic","path":"/docs/reference/user-interface/lists/lists-models","breadcrumb":"Reference › User Interface › Lists › Models","description":"","searchText":"reference user interface lists models overview models is implemented as a searchable list page in configmodels.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. access this topic was rebuilt from configmodels.xaml and configmodels.xaml.cs. the source defines the filter controls, grid headers, and list actions for models. how to access navigation tree models -> list models toolbar data mart -> models diagram not direct. use the list page. visual element configmodels screen overview the models list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 save saves the current record. 6 cancel closes the screen without saving changes. related topics layers macros object group content object scripts"}
,{"id":386688842971,"name":"Object group content","type":"topic","path":"/docs/reference/user-interface/lists/lists-object-group-content","breadcrumb":"Reference › User Interface › Lists › Object group content","description":"","searchText":"reference user interface lists object group content overview object group content is implemented as a searchable list page in searchgroupobjects.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. access this topic was rebuilt from searchgroupobjects.xaml and searchgroupobjects.xaml.cs. the source defines the filter controls, grid headers, and list actions for object group content. how to access navigation tree groups -> list groups toolbar not direct. open the groups dialog and inspect one group. diagram not direct. use the list page. visual element searchgroupobjects screen overview the object group content list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 group group-related control or command defined in the source-backed ui. 3 object visible label, button, tab, or grid header defined in the source-backed xaml. 4 inherit predecessors visible label, button, tab, or grid header defined in the source-backed xaml. 5 inherit successors visible label, button, tab, or grid header defined in the source-backed xaml. 6 inherited visible label, button, tab, or grid header defined in the source-backed xaml. 7 exclude visible label, button, tab, or grid header defined in the source-backed xaml. 8 inherited from objects visible label, button, tab, or grid header defined in the source-backed xaml. 9 search runs the filter action defined for this screen. 10 save saves the current record. related topics macros models object scripts olap roles"}
,{"id":386688842972,"name":"Object Scripts","type":"topic","path":"/docs/reference/user-interface/lists/lists-object-scripts","breadcrumb":"Reference › User Interface › Lists › Object Scripts","description":"","searchText":"reference user interface lists object scripts overview object scripts is implemented as a searchable list page in searchobjectscript.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchobjectscript.xaml and searchobjectscript.xaml.cs. the source defines the filter controls, grid headers, and list actions for object scripts. how to access navigation tree object scripts -> list object scripts toolbar not direct. use the navigation tree object scripts node. diagram not direct. use the list page. visual element searchobjectscript screen overview the object scripts list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 object visible label, button, tab, or grid header defined in the source-backed xaml. 3 name visible field label or grid column header defined in the source-backed xaml. 4 description visible field label or grid column header defined in the source-backed xaml. 5 search runs the filter action defined for this screen. 6 delete deletes the selected item. 7 new creates a new item or starts the add flow defined in the screen. related topics models object group content olap roles packages"}
,{"id":386688842973,"name":"OLAP roles","type":"topic","path":"/docs/reference/user-interface/lists/lists-olap-roles","breadcrumb":"Reference › User Interface › Lists › OLAP roles","description":"","searchText":"reference user interface lists olap roles overview olap roles is implemented as a searchable list page in searchroles.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchroles.xaml and searchroles.xaml.cs. the source defines the filter controls, grid headers, and list actions for olap roles. how to access navigation tree roles -> list roles toolbar data mart -> roles diagram not direct. use the list page. visual element searchroles screen overview the olap roles list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 delete deletes the selected item. 6 duplicate visible label, button, tab, or grid header defined in the source-backed xaml. 7 new creates a new item or starts the add flow defined in the screen. related topics object group content object scripts packages partitions"}
,{"id":386688842974,"name":"Packages","type":"topic","path":"/docs/reference/user-interface/lists/lists-packages","breadcrumb":"Reference › User Interface › Lists › Packages","description":"","searchText":"reference user interface lists packages overview packages is implemented as a searchable list page in searchpackages.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchpackages.xaml and searchpackages.xaml.cs. the source defines the filter controls, grid headers, and list actions for packages. how to access navigation tree packages -> list packages toolbar etl -> packages diagram not direct. use the list page. visual element searchpackages screen overview the packages list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 package name visible field label or grid column header defined in the source-backed xaml. 3 package type visible field label or grid column header defined in the source-backed xaml. 4 manually created visible label, button, tab, or grid header defined in the source-backed xaml. 5 externally launched visible label, button, tab, or grid header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 search runs the filter action defined for this screen. 8 delete deletes the selected item. 9 new creates a new item or starts the add flow defined in the screen. related topics object scripts olap roles partitions predefined transformations"}
,{"id":386688842975,"name":"Parameters","type":"topic","path":"/docs/reference/user-interface/lists/lists-parameters","breadcrumb":"Reference › User Interface › Lists › Parameters","description":"","searchText":"reference user interface lists parameters overview the parameters page is used to list and edit analyticscreator parameters. function this page is used to list and maintain analyticscreator parameters. access the page can be opened from the navigation tree. how to access navigation tree parameters->list parameters toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchparameter this page is used to list/edit analyticscreator parameters. related topics none confirmed."}
,{"id":386688842976,"name":"Partitions","type":"topic","path":"/docs/reference/user-interface/lists/lists-partitions","breadcrumb":"Reference › User Interface › Lists › Partitions","description":"","searchText":"reference user interface lists partitions overview partitions is implemented as a searchable list page in searchpartitions.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchpartitions.xaml and searchpartitions.xaml.cs. the source defines the filter controls, grid headers, and list actions for partitions. how to access navigation tree partitions -> list partitions toolbar data mart -> partitions diagram not direct. use the list page. visual element searchpartitions screen overview the partitions list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 fact table visible field label or grid column header defined in the source-backed xaml. 3 name visible field label or grid column header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 delete deletes the selected item. 6 duplicate visible label, button, tab, or grid header defined in the source-backed xaml. 7 new creates a new item or starts the add flow defined in the screen. related topics olap roles packages predefined transformations snapshot groups"}
,{"id":386688842977,"name":"Predefined transformations","type":"topic","path":"/docs/reference/user-interface/lists/lists-predefined-transformations","breadcrumb":"Reference › User Interface › Lists › Predefined transformations","description":"","searchText":"reference user interface lists predefined transformations overview predefined transformations is implemented as a searchable list page in searchpredifinedtransformations.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchpredifinedtransformations.xaml and searchpredifinedtransformations.xaml.cs. the source defines the filter controls, grid headers, and list actions for predefined transformations. how to access navigation tree predefined transformations -> list predefined transformations toolbar dwh -> predefined trans. diagram not direct. use the list page. visual element searchpredifinedtransformations screen overview the predefined transformations list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 delete deletes the selected item. 6 new creates a new item or starts the add flow defined in the screen. related topics packages partitions snapshot groups snapshots"}
,{"id":386688842978,"name":"Schemas","type":"topic","path":"/docs/reference/user-interface/lists/lists-schemas","breadcrumb":"Reference › User Interface › Lists › Schemas","description":"","searchText":"reference user interface lists schemas overview the schemas page is used to list and edit schemas. function this page is used to list and maintain schemas. access the page can be opened from the navigation tree and toolbar. how to access navigation tree layers->layer->schema->edit schema toolbar dwh->schemas diagram not confirmed. visual element not confirmed. screen overview id property description 1 name sql schema name used during deployment (e.g., stg , dwh ) 2 schema type logical role of the schema in the data pipeline (e.g., staging, core, datamart) 3 layer associated layer that controls the build sequence for the schema's objects 4 description optional field for describing the schema's purpose or contents related topics connectors datamart stars deploymens encrypted strings"}
,{"id":386688842979,"name":"Snapshot groups","type":"topic","path":"/docs/reference/user-interface/lists/lists-snapshot-groups","breadcrumb":"Reference › User Interface › Lists › Snapshot groups","description":"","searchText":"reference user interface lists snapshot groups overview snapshot groups is implemented as a searchable list page in searchsnapshotgroups.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchsnapshotgroups.xaml and searchsnapshotgroups.xaml.cs. the source defines the filter controls, grid headers, and list actions for snapshot groups. how to access navigation tree snapshot groups -> list snapshot groups toolbar not direct. use the navigation tree snapshot groups node. diagram not direct. use the list page. visual element searchsnapshotgroups screen overview the snapshot groups list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 description visible field label or grid column header defined in the source-backed xaml. 4 search runs the filter action defined for this screen. 5 delete deletes the selected item. 6 new creates a new item or starts the add flow defined in the screen. related topics partitions predefined transformations snapshots source references"}
,{"id":386688842980,"name":"Snapshots","type":"topic","path":"/docs/reference/user-interface/lists/lists-snapshots","breadcrumb":"Reference › User Interface › Lists › Snapshots","description":"","searchText":"reference user interface lists snapshots overview snapshots is implemented as a searchable list page in searchsnapshots.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchsnapshots.xaml and searchsnapshots.xaml.cs. the source defines the filter controls, grid headers, and list actions for snapshots. how to access navigation tree snapshots -> list snapshots toolbar dwh -> snapshots diagram not direct. use the list page. visual element searchsnapshots screen overview the snapshots list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 update sql visible label, button, tab, or grid header defined in the source-backed xaml. 4 description visible field label or grid column header defined in the source-backed xaml. 5 search runs the filter action defined for this screen. 6 delete deletes the selected item. 7 new creates a new item or starts the add flow defined in the screen. related topics predefined transformations snapshot groups source references sources"}
,{"id":386688842981,"name":"Source references","type":"topic","path":"/docs/reference/user-interface/lists/lists-source-references","breadcrumb":"Reference › User Interface › Lists › Source references","description":"","searchText":"reference user interface lists source references overview source references is implemented as a searchable list page in searchsrcreferences.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchsrcreferences.xaml and searchsrcreferences.xaml.cs. the source defines the filter controls, grid headers, and list actions for source references. how to access navigation tree source references -> list references toolbar sources -> references diagram not direct. use the list page. visual element searchsrcreferences screen overview the source references list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 connector1 visible field label or grid column header defined in the source-backed xaml. 3 schema1 visible field label or grid column header defined in the source-backed xaml. 4 source1 visible field label or grid column header defined in the source-backed xaml. 5 cardinality visible label, button, tab, or grid header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 references visible field label or grid column header defined in the source-backed xaml. 8 search runs the filter action defined for this screen. 9 new creates a new item or starts the add flow defined in the screen. 10 delete deletes the selected item. related topics snapshot groups snapshots sources sql script"}
,{"id":386688842982,"name":"Sources","type":"topic","path":"/docs/reference/user-interface/lists/lists-sources","breadcrumb":"Reference › User Interface › Lists › Sources","description":"","searchText":"reference user interface lists sources overview sources is implemented as a searchable list page in searchsources.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchsources.xaml and searchsources.xaml.cs. the source defines the filter controls, grid headers, and list actions for sources. how to access navigation tree sources -> list sources toolbar sources -> sources diagram not direct. use the list page. visual element searchsources screen overview the sources list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 source schema visible field label or grid column header defined in the source-backed xaml. 3 source name visible field label or grid column header defined in the source-backed xaml. 4 connector visible field label or grid column header defined in the source-backed xaml. 5 type visible field label or grid column header defined in the source-backed xaml. 6 path visible label, button, tab, or grid header defined in the source-backed xaml. 7 friendly name visible field label or grid column header defined in the source-backed xaml. 8 description visible field label or grid column header defined in the source-backed xaml. 9 search runs the filter action defined for this screen. 10 delete deletes the selected item. related topics snapshots source references sql script table references"}
,{"id":386688842983,"name":"SQL Script","type":"topic","path":"/docs/reference/user-interface/lists/lists-sql-script","breadcrumb":"Reference › User Interface › Lists › SQL Script","description":"","searchText":"reference user interface lists sql script overview sql script is implemented as a searchable list page in searchscripts.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchscripts.xaml and searchscripts.xaml.cs. the source defines the filter controls, grid headers, and list actions for sql script. how to access navigation tree sql scripts -> list scripts toolbar etl -> scripts diagram not direct. use the list page. visual element searchscripts screen overview the sql script list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 name visible field label or grid column header defined in the source-backed xaml. 3 type visible field label or grid column header defined in the source-backed xaml. 4 seqnr visible label, button, tab, or grid header defined in the source-backed xaml. 5 description visible field label or grid column header defined in the source-backed xaml. 6 search runs the filter action defined for this screen. 7 delete deletes the selected item. 8 new creates a new item or starts the add flow defined in the screen. related topics source references sources table references transformations"}
,{"id":386688842984,"name":"Table references","type":"topic","path":"/docs/reference/user-interface/lists/lists-table-references","breadcrumb":"Reference › User Interface › Lists › Table references","description":"","searchText":"reference user interface lists table references overview table references is implemented as a searchable list page in searchreferences.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchreferences.xaml and searchreferences.xaml.cs. the source defines the filter controls, grid headers, and list actions for table references. how to access navigation tree table references -> list references toolbar dwh -> references diagram not direct. use the list page. visual element searchreferences screen overview the table references list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 autcreated visible label, button, tab, or grid header defined in the source-backed xaml. 3 used visible label, button, tab, or grid header defined in the source-backed xaml. 4 schema1 visible field label or grid column header defined in the source-backed xaml. 5 table1 visible field label or grid column header defined in the source-backed xaml. 6 schema2 visible field label or grid column header defined in the source-backed xaml. 7 table2 visible field label or grid column header defined in the source-backed xaml. 8 doublesided visible label, button, tab, or grid header defined in the source-backed xaml. 9 inactive visible label, button, tab, or grid header defined in the source-backed xaml. 10 force inheritance visible label, button, tab, or grid header defined in the source-backed xaml. related topics sources sql script transformations"}
,{"id":386688842985,"name":"Tables","type":"topic","path":"/docs/reference/user-interface/lists/lists-tables","breadcrumb":"Reference › User Interface › Lists › Tables","description":"","searchText":"reference user interface lists tables overview the tables page is used to list tables. function this page is used to list tables. access the page can be opened from the navigation tree and toolbar. how to access navigation tree model->layers->layer->schema->tables->list tables toolbar dwh->tables diagram not confirmed. visual element not confirmed. screen overview id property description 1 table schema the database schema (e.g., dwh, imp) where the table resides 2 table name the name of the table used in the sql database and pipelines 3 historization of table indicates if historization (type 2 scd logic) is applied to the table 4 persistance of table if enabled, stores the table as a persisted table (not a view) 5 table type defines the type of object (e.g., import table, view with history, view without history, persisted table with history) 6 friendly name optional user-defined label for easier identification of the table 7 description free-text field used for documenting the purpose or contents of the table related topics connectors datamart stars deploymens encrypted strings"}
,{"id":386688842986,"name":"Transformations","type":"topic","path":"/docs/reference/user-interface/lists/lists-transformations","breadcrumb":"Reference › User Interface › Lists › Transformations","description":"","searchText":"reference user interface lists transformations overview transformations is implemented as a searchable list page in searchtransformations.xaml. function the page uses the standard search-page pattern: a filter group at the top, a read-only result grid in the center, and footer actions such as new and delete. the xaml also binds a double-click handler so the selected row can open the related detail page. access this topic was rebuilt from searchtransformations.xaml and searchtransformations.xaml.cs. the source defines the filter controls, grid headers, and list actions for transformations. how to access navigation tree transformations -> list transformations toolbar etl -> transformations diagram not direct. use the list page. visual element searchtransformations screen overview the transformations list follows the search-page layout defined in source, with these visible controls and columns. id property description 1 search criteria group box that contains the filter controls for this screen. 2 schema visible field label or grid column header defined in the source-backed xaml. 3 name visible field label or grid column header defined in the source-backed xaml. 4 type visible field label or grid column header defined in the source-backed xaml. 5 hist type visible field label or grid column header defined in the source-backed xaml. 6 createdummyentry visible label, button, tab, or grid header defined in the source-backed xaml. 7 search runs the filter action defined for this screen. 8 new creates a new item or starts the add flow defined in the screen. 9 duplicate visible label, button, tab, or grid header defined in the source-backed xaml. 10 delete deletes the selected item. related topics sql script table references"}
,{"id":386688842987,"name":"User groups","type":"topic","path":"/docs/reference/user-interface/lists/lists-user-groups","breadcrumb":"Reference › User Interface › Lists › User groups","description":"","searchText":"reference user interface lists user groups overview the user groups page is used to list user groups. function this page is used to list user groups. access the page can be opened from the toolbar. how to access navigation tree not confirmed. toolbar options->user groups diagram not confirmed. visual element not confirmed. screen overview id property description 1 search criteria filter existing user groups by name or partial keyword. 2 rights displays access rights for the user in each group (e.g., read write , read only , group owner ). 3 delete removes the selected group permanently (requires group owner rights). 4 leave allows the logged user to exit a group without deleting it. 5 new creates a new user group for collaboration. related topics connectors datamart stars deploymens encrypted strings"}
,{"id":383509396684,"name":"Dialogs","type":"subsection","path":"/docs/reference/user-interface/dialogs","breadcrumb":"Reference › User Interface › Dialogs","description":"","searchText":"reference user interface dialogs the dialogs section covers the focused pop-up workflows that support configuration, validation, search, preview, synchronization, and repository maintenance in analyticscreator. use these topics to understand when a dialog appears, which decision it supports, and how it fits into broader activities such as metadata refresh, cloud operations, upgrades, and day-to-day authoring. available topics about the about dialog is used for about analyticscreator (version). dwh settings the dwh settings dialog is used for common dwh settings. error description the error description dialog is used for common dialog containing errors/warnings/meessages. eula the eula dialog is used for dialog contatinig end user licence agreement. input dialog the input dialog dialog is used for common input dialog. input dialog with dropbox the input dialog with dropbox dialog is used for common input dialog with dropbox. open/save in cloud the open/save in cloud dialog is used for dialog to load/store data in cloud. preview source data the preview source data dialog is used for dialog to preview source data. upgrade repository the upgrade repository dialog is used for repository upgrade progress dialog. refresh source metadata the refresh source metadata dialog is used for dialog to update source metadata. search the search dialog is used for common search dialog. tumbnail diagram the tumbnail diagram dialog is used in the analyticscreator user interface. source constraints the source constraints dialog is used for information about source constraints. synchronize dwh the synchronize dwh dialog is used for dialog to synchronize dwh. interface settings the interface settings dialog is used for analyticscreator interface settings. login the login dialog is used for login dialog on start of analyticscreator. object groups the object groups dialog is used for information about the groups of specific object. how to use this section start with about, eula, login, and interface settings for environment, access, and application-level context. use input dialog and input dialog with dropbox when a workflow depends on guided data entry or assisted selection. use preview source data, refresh source metadata, search, and source constraints when inspecting or troubleshooting source-side behavior. use synchronize dwh, upgrade repository, and open/save in cloud when the task affects repository lifecycle, synchronization, or environment operations. key takeaway the dialogs section explains the short, decision-oriented interaction surfaces that support guided work across the analyticscreator interface."}
,{"id":386707108084,"name":"About","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-about","breadcrumb":"Reference › User Interface › Dialogs › About","description":"","searchText":"reference user interface dialogs about overview the about dialog is used for about analyticscreator (version). function this dialog supports about analyticscreator (version). access the about dialog can be opened from the toolbar. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview candidate screen coverage to be validated during the approval step. about legacy screenshot 1 id property description 1 focus area about legacy screenshot 1 2 source legacy backup candidate pending validation 3 next action confirm the screenshot matches the current ui before implementation. related topics dwh settings error description eula input dialog"}
,{"id":386707108085,"name":"DWH settings","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-dwh-settings","breadcrumb":"Reference › User Interface › Dialogs › DWH settings","description":"","searchText":"reference user interface dialogs dwh settings overview the dwh settings dialog is used for common dwh settings. function this dialog supports common dwh settings. access the dwh settings dialog can be opened from the toolbar. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview candidate screen coverage to be validated during the approval step. dwh settings legacy screenshot 1 id property description 1 focus area dwh settings legacy screenshot 1 2 source legacy backup candidate pending validation 3 next action confirm the screenshot matches the current ui before implementation. related topics about error description eula input dialog"}
,{"id":386707108086,"name":"Error description","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-error-description","breadcrumb":"Reference › User Interface › Dialogs › Error description","description":"","searchText":"reference user interface dialogs error description overview error description is implemented by the error dialog/window in analyticscreator. function the dialog is defined in errorwindow.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from errorwindow.xaml and errorwindow.xaml.cs. the source defines the visible controls and the action buttons for the error description dialog. how to access navigation tree opened from the related workflow. toolbar opened by error handling in the current workflow. diagram not direct. visual element errorwindow screen overview the error description dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 error message visible label, button, tab, or grid header defined in the source-backed xaml. 2 stack trace visible label, button, tab, or grid header defined in the source-backed xaml. 3 ok visible label, button, tab, or grid header defined in the source-backed xaml. related topics eula input dialog"}
,{"id":386707108087,"name":"EULA","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-eula","breadcrumb":"Reference › User Interface › Dialogs › EULA","description":"","searchText":"reference user interface dialogs eula overview eula is implemented by the end-user license agreement dialog/window in analyticscreator. function the dialog is defined in eulawindow.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from eulawindow.xaml and eulawindow.xaml.cs. the source defines the visible controls and the action buttons for the eula dialog. how to access navigation tree opened from the related workflow. toolbar help -> eula diagram not direct. visual element eulawindow screen overview the eula dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 decline visible label, button, tab, or grid header defined in the source-backed xaml. 2 accept visible label, button, tab, or grid header defined in the source-backed xaml. 3 close visible label, button, tab, or grid header defined in the source-backed xaml. related topics error description input dialog input dialog with dropbox"}
,{"id":386707108088,"name":"Input dialog","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-input-dialog","breadcrumb":"Reference › User Interface › Dialogs › Input dialog","description":"","searchText":"reference user interface dialogs input dialog overview input dialog is implemented by the inputdialog dialog/window in analyticscreator. function the dialog is defined in inputdialog.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from inputdialog.xaml and inputdialog.xaml.cs. the source defines the visible controls and the action buttons for the input dialog dialog. how to access navigation tree opened from the related workflow. toolbar opened by commands that request typed input. diagram not direct. visual element inputdialog screen overview the input dialog dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 cancel closes the screen without saving changes. 2 ok visible label, button, tab, or grid header defined in the source-backed xaml. related topics error description eula input dialog with dropbox interface settings"}
,{"id":386707108089,"name":"Input dialog with dropbox","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-input-dialog-with-dropbox","breadcrumb":"Reference › User Interface › Dialogs › Input dialog with dropbox","description":"","searchText":"reference user interface dialogs input dialog with dropbox overview input dialog with dropbox is implemented by the inputdialogcombo dialog/window in analyticscreator. function the dialog is defined in inputdialogcombo.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from inputdialogcombo.xaml and inputdialogcombo.xaml.cs. the source defines the visible controls and the action buttons for the input dialog with dropbox dialog. how to access navigation tree opened from the related workflow. toolbar opened by commands that request typed input and a predefined choice. diagram not direct. visual element inputdialogcombo screen overview the input dialog with dropbox dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 cancel closes the screen without saving changes. 2 ok visible label, button, tab, or grid header defined in the source-backed xaml. related topics eula input dialog interface settings login"}
,{"id":386707109053,"name":"Open/save in cloud","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-open-save-in-cloud","breadcrumb":"Reference › User Interface › Dialogs › Open/save in cloud","description":"","searchText":"reference user interface dialogs open/save in cloud overview open/save in cloud is implemented by the list repositories dialog/window in analyticscreator. function the dialog is defined in listfileswindow.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from listfileswindow.xaml and listfileswindow.xaml.cs. the source defines the visible controls and the action buttons for the open/save in cloud dialog. how to access navigation tree opened from the related workflow. toolbar file -> load from cloud or save to cloud diagram not direct. visual element listfileswindow screen overview the open/save in cloud dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 rename visible field label or grid column header defined in the source-backed xaml. 2 change description visible field label or grid column header defined in the source-backed xaml. 3 delete deletes the selected item. 4 delete all visible label, button, tab, or grid header defined in the source-backed xaml. 5 name visible field label or grid column header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 ok visible label, button, tab, or grid header defined in the source-backed xaml. 8 cancel closes the screen without saving changes. related topics login object groups preview source data refresh source metadata"}
,{"id":386707109054,"name":"Preview source data","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-preview-source-data","breadcrumb":"Reference › User Interface › Dialogs › Preview source data","description":"","searchText":"reference user interface dialogs preview source data overview preview source data is implemented by the preview dialog/window in analyticscreator. function the dialog is defined in preview.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from preview.xaml and preview.xaml.cs. the source defines the visible controls and the action buttons for the preview source data dialog. how to access navigation tree opened from the related workflow. toolbar opened from preview actions on sources and source-related objects. diagram architecture -> preview data visual element preview screen overview the preview source data dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 filter filter-related control or command defined in the source-backed ui. 2 num of rows visible label, button, tab, or grid header defined in the source-backed xaml. 3 timeout (sec) visible label, button, tab, or grid header defined in the source-backed xaml. 4 apply visible label, button, tab, or grid header defined in the source-backed xaml. 5 ok visible label, button, tab, or grid header defined in the source-backed xaml. related topics object groups open/save in cloud refresh source metadata search"}
,{"id":386707109060,"name":"Upgrade repository","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-upgrade-repository","breadcrumb":"Reference › User Interface › Dialogs › Upgrade repository","description":"","searchText":"reference user interface dialogs upgrade repository overview upgrade repository is implemented by the creating repository dialog/window in analyticscreator. function the dialog is defined in publishdatabase.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from publishdatabase.xaml and publishdatabase.xaml.cs. the source defines the visible controls and the action buttons for the upgrade repository dialog. how to access navigation tree opened from the related workflow. toolbar opened during repository creation or upgrade. diagram not direct. visual element publishdatabase screen overview the upgrade repository dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 ok visible label, button, tab, or grid header defined in the source-backed xaml. related topics synchronize dwh tumbnail diagram"}
,{"id":386707109055,"name":"Refresh source metadata","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-refresh-source-metadata","breadcrumb":"Reference › User Interface › Dialogs › Refresh source metadata","description":"","searchText":"reference user interface dialogs refresh source metadata overview refresh source metadata is implemented by the refresh sources dialog/window in analyticscreator. function the dialog is defined in refreshsources.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from refreshsources.xaml and refreshsources.xaml.cs. the source defines the visible controls and the action buttons for the refresh source metadata dialog. how to access navigation tree opened from the related workflow. toolbar opened from source refresh actions. diagram architecture -> refresh source visual element refreshsources screen overview the refresh source metadata dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 detect differences without to change repository visible label, button, tab, or grid header defined in the source-backed xaml. 2 delete missing sources visible field label or grid column header defined in the source-backed xaml. 3 refresh source descriptions visible field label or grid column header defined in the source-backed xaml. 4 refresh existing source columns visible field label or grid column header defined in the source-backed xaml. 5 refresh columns in imported tables visible field label or grid column header defined in the source-backed xaml. 6 delete missing columns in imported tables visible field label or grid column header defined in the source-backed xaml. 7 refresh primary keys in imported tables visible field label or grid column header defined in the source-backed xaml. 8 refresh descriptions in imported tables visible field label or grid column header defined in the source-backed xaml. 9 refresh source references visible field label or grid column header defined in the source-backed xaml. 10 cancel closes the screen without saving changes. related topics open/save in cloud preview source data search source constraints"}
,{"id":386707109056,"name":"Search","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-search","breadcrumb":"Reference › User Interface › Dialogs › Search","description":"","searchText":"reference user interface dialogs search overview search is implemented by the search dialog/window in analyticscreator. function the dialog is defined in searchdialog.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from searchdialog.xaml and searchdialog.xaml.cs. the source defines the visible controls and the action buttons for the search dialog. how to access navigation tree opened from the related workflow. toolbar file -> find on diagram diagram not direct. visual element searchdialog screen overview the search dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 keyword visible label, button, tab, or grid header defined in the source-backed xaml. 2 match whole word visible label, button, tab, or grid header defined in the source-backed xaml. 3 match case visible label, button, tab, or grid header defined in the source-backed xaml. 4 cancel closes the screen without saving changes. 5 find next (f3) visible label, button, tab, or grid header defined in the source-backed xaml. 6 find previous (shift+f3) visible label, button, tab, or grid header defined in the source-backed xaml. related topics preview source data refresh source metadata source constraints synchronize dwh"}
,{"id":386707109059,"name":"Tumbnail diagram","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-tumbnail-diagram","breadcrumb":"Reference › User Interface › Dialogs › Tumbnail diagram","description":"","searchText":"reference user interface dialogs tumbnail diagram overview tumbnail diagram is implemented by the thumbnail diagram dialog/window in analyticscreator. function the dialog is defined in smalldiagram.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from smalldiagram.xaml and smalldiagram.xaml.cs. the source defines the visible controls and the action buttons for the tumbnail diagram dialog. how to access navigation tree opened from the related workflow. toolbar opened from diagram thumbnail actions. diagram architecture -> show thumbnail visual element smalldiagram screen overview the tumbnail diagram dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 thumbnail diagram window or page title defined in the source-backed xaml. related topics source constraints synchronize dwh upgrade repository"}
,{"id":386707109057,"name":"Source constraints","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-source-constraints","breadcrumb":"Reference › User Interface › Dialogs › Source constraints","description":"","searchText":"reference user interface dialogs source constraints overview source constraints is implemented by the sourceconstraint dialog/window in analyticscreator. function the dialog is defined in sourceconstraint.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from sourceconstraint.xaml and sourceconstraint.xaml.cs. the source defines the visible controls and the action buttons for the source constraints dialog. how to access navigation tree opened from the related workflow. toolbar opened from source-reference constraint editing. diagram not direct. visual element sourceconstraint screen overview the source constraints dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 source constraints visible field label or grid column header defined in the source-backed xaml. 2 column visible label, button, tab, or grid header defined in the source-backed xaml. 3 do not import visible label, button, tab, or grid header defined in the source-backed xaml. 4 statement visible label, button, tab, or grid header defined in the source-backed xaml. 5 messagestatement visible label, button, tab, or grid header defined in the source-backed xaml. 6 description visible field label or grid column header defined in the source-backed xaml. 7 save saves the current record. 8 cancel closes the screen without saving changes. related topics refresh source metadata search synchronize dwh tumbnail diagram"}
,{"id":386707109058,"name":"Synchronize DWH","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-synchronize-dwh","breadcrumb":"Reference › User Interface › Dialogs › Synchronize DWH","description":"","searchText":"reference user interface dialogs synchronize dwh overview synchronize dwh is implemented by the synchronize and refresh dialog/window in analyticscreator. function the dialog is defined in synchronise.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from synchronise.xaml and synchronise.xaml.cs. the source defines the visible controls and the action buttons for the synchronize dwh dialog. how to access navigation tree opened from the related workflow. toolbar file -> sync dwh diagram architecture -> synchronize dwh visual element synchronise screen overview the synchronize dwh dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 templates visible label, button, tab, or grid header defined in the source-backed xaml. 2 synchronize visible label, button, tab, or grid header defined in the source-backed xaml. 3 refresh diagram visible label, button, tab, or grid header defined in the source-backed xaml. 4 additional tasks visible label, button, tab, or grid header defined in the source-backed xaml. 5 full visible label, button, tab, or grid header defined in the source-backed xaml. 6 selected group group-related control or command defined in the source-backed ui. 7 new objects visible label, button, tab, or grid header defined in the source-backed xaml. 8 all additional tasks visible label, button, tab, or grid header defined in the source-backed xaml. 9 no additional tasks visible label, button, tab, or grid header defined in the source-backed xaml. 10 full synchronize visible label, button, tab, or grid header defined in the source-backed xaml. related topics search source constraints tumbnail diagram upgrade repository"}
,{"id":386707109050,"name":"Interface settings","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-interface-settings","breadcrumb":"Reference › User Interface › Dialogs › Interface settings","description":"","searchText":"reference user interface dialogs interface settings overview interface settings is implemented by the interface settings dialog/window in analyticscreator. function the dialog is defined in acsettings.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from acsettings.xaml and acsettings.xaml.cs. the source defines the visible controls and the action buttons for the interface settings dialog. how to access navigation tree opened from the related workflow. toolbar options -> interface diagram not direct. visual element acsettings screen overview the interface settings dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 colors visible label, button, tab, or grid header defined in the source-backed xaml. 2 diagram visible label, button, tab, or grid header defined in the source-backed xaml. 3 navigation tree visible label, button, tab, or grid header defined in the source-backed xaml. 4 pages visible label, button, tab, or grid header defined in the source-backed xaml. 5 background arrow visible label, button, tab, or grid header defined in the source-backed xaml. 6 background text visible label, button, tab, or grid header defined in the source-backed xaml. 7 background dimension visible label, button, tab, or grid header defined in the source-backed xaml. 8 background external transformation visible label, button, tab, or grid header defined in the source-backed xaml. 9 background fact visible label, button, tab, or grid header defined in the source-backed xaml. 10 background header visible label, button, tab, or grid header defined in the source-backed xaml. related topics input dialog input dialog with dropbox login object groups"}
,{"id":386707109051,"name":"Login","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-login","breadcrumb":"Reference › User Interface › Dialogs › Login","description":"","searchText":"reference user interface dialogs login overview login is implemented by the login dialog/window in analyticscreator. function the dialog is defined in loginwindow.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from loginwindow.xaml and loginwindow.xaml.cs. the source defines the visible controls and the action buttons for the login dialog. how to access navigation tree opened from the related workflow. toolbar file -> connect diagram not direct. visual element loginwindow screen overview the login dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 sql server settings visible field label or grid column header defined in the source-backed xaml. 2 paths visible label, button, tab, or grid header defined in the source-backed xaml. 3 proxy settings visible label, button, tab, or grid header defined in the source-backed xaml. 4 login visible field label or grid column header defined in the source-backed xaml. 5 password visible field label or grid column header defined in the source-backed xaml. 6 save password visible field label or grid column header defined in the source-backed xaml. 7 sql server to store repository visible field label or grid column header defined in the source-backed xaml. 8 security visible label, button, tab, or grid header defined in the source-backed xaml. 9 sql user visible label, button, tab, or grid header defined in the source-backed xaml. 10 sql password visible field label or grid column header defined in the source-backed xaml. related topics input dialog with dropbox interface settings object groups open/save in cloud"}
,{"id":386707109052,"name":"Object groups","type":"topic","path":"/docs/reference/user-interface/dialogs/dialogs-object-groups","breadcrumb":"Reference › User Interface › Dialogs › Object groups","description":"","searchText":"reference user interface dialogs object groups overview object groups is implemented by the groups dialog/window in analyticscreator. function the dialog is defined in searchgroups.xaml and its companion code-behind handles the dialog actions and state transitions for this workflow. access this topic was rebuilt from searchgroups.xaml and searchgroups.xaml.cs. the source defines the visible controls and the action buttons for the object groups dialog. how to access navigation tree opened from the related workflow. toolbar opened from object-group management flows. diagram object groups -> list groups visual element searchgroups screen overview the object groups dialog exposes the following source-defined labels, tabs, buttons, or grid headers. id property description 1 member visible label, button, tab, or grid header defined in the source-backed xaml. 2 inherit predecessors visible label, button, tab, or grid header defined in the source-backed xaml. 3 inherit successors visible label, button, tab, or grid header defined in the source-backed xaml. 4 inherited visible label, button, tab, or grid header defined in the source-backed xaml. 5 exclude visible label, button, tab, or grid header defined in the source-backed xaml. 6 name visible field label or grid column header defined in the source-backed xaml. 7 description visible field label or grid column header defined in the source-backed xaml. 8 create workflow visible label, button, tab, or grid header defined in the source-backed xaml. 9 ssis configuration complete script visible label, button, tab, or grid header defined in the source-backed xaml. 10 ssis configuration enable script visible label, button, tab, or grid header defined in the source-backed xaml. related topics interface settings login open/save in cloud preview source data"}
,{"id":383509340360,"name":"Wizards","type":"subsection","path":"/docs/reference/user-interface/wizards","breadcrumb":"Reference › User Interface › Wizards","description":"","searchText":"reference user interface wizards the wizards section documents the guided setup flows that help users create common analyticscreator objects and modeling patterns with structured input steps. use these topics when you want to accelerate object creation, standardize implementation choices, or understand which wizard best fits a given warehouse, transformation, snapshot, or scripting scenario. available topics create calendar dimension explains the guided flow for creating a calendar dimension and defining the date-related structures it needs. create datavault object covers the wizard that creates data vault components such as hubs, links, and satellites with guided setup. create export shows how the export wizard guides users through defining outbound data delivery objects. create historization describes the wizard used to create historization objects for tracking changes over time. create import explains the guided setup used to create new import objects from source metadata. create snapshot dimension covers the wizard used to generate snapshot-oriented dimension structures. create source shows how the source wizard guides users through creating a new source object and its metadata. create time dimension describes the wizard used to generate a reusable time dimension structure. create transformation explains the wizard used to create a new transformation and its initial metadata. dwh wizard covers the guided warehouse setup flow for creating foundational dwh structures and decisions. hash keys explains the wizard that creates or refreshes hash keys and their related relationships. persist transformation shows how the persist transformation wizard converts transformation logic into persisted storage structures. run object script describes the guided flow for selecting and executing object scripts against repository objects. how to use this section start with the create-object wizards for source, import, export, historization, and transformation when building common data pipeline components. use the dimension and data vault wizards when you need guided support for established modeling patterns. use dwh wizard and hash keys when the task requires warehouse-wide setup decisions or key-generation behavior. use persist transformation and run object script for advanced guided actions that continue work after the initial object design stage. key takeaway the wizards section helps users choose the right guided workflow for creating recurring analyticscreator patterns with less manual setup and more consistent implementation."}
,{"id":386707109062,"name":"Create calendar dimension","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-calendar-dimension","breadcrumb":"Reference › User Interface › Wizards › Create calendar dimension","description":"","searchText":"reference user interface wizards create calendar dimension overview create calendar dimension is implemented as the new calendar transformation wizard or assistant in analyticscreator. function the wizard is defined in assistent_newdatetrans.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newdatetrans.xaml and assistent_newdatetrans.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create calendar dimension. how to access navigation tree opened from the owning command or workflow. toolbar etl -> calendar dimension diagram architecture -> add -> calendar dimension visual element assistent_newdatetrans screen overview the create calendar dimension wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 schema visible field label or grid column header defined in the source-backed xaml. 2 name visible field label or grid column header defined in the source-backed xaml. 3 date from visible label, button, tab, or grid header defined in the source-backed xaml. 4 date to visible label, button, tab, or grid header defined in the source-backed xaml. 5 date-to-id function visible label, button, tab, or grid header defined in the source-backed xaml. 6 stars visible label, button, tab, or grid header defined in the source-backed xaml. 7 cancel closes the screen without saving changes. 8 finish completes the wizard. related topics create datavault object create export"}
,{"id":386707109063,"name":"Create DataVault object","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-datavault-object","breadcrumb":"Reference › User Interface › Wizards › Create DataVault object","description":"","searchText":"reference user interface wizards create datavault object overview create datavault object is implemented as the vault wizard wizard or assistant in analyticscreator. function the wizard is defined in assistent_newvault.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newvault.xaml and assistent_newvault.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create datavault object. how to access navigation tree opened from the owning command or workflow. toolbar not direct in the ribbon. use the diagram add menu. diagram architecture -> add -> data vault hub / data vault satellite / data vault link visual element assistent_newvault screen overview the create datavault object wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 main tab header defined in the source-backed xaml. 2 link visible label, button, tab, or grid header defined in the source-backed xaml. 3 include visible label, button, tab, or grid header defined in the source-backed xaml. 4 table visible field label or grid column header defined in the source-backed xaml. 5 source table visible field label or grid column header defined in the source-backed xaml. 6 transformation schema visible field label or grid column header defined in the source-backed xaml. 7 transformation name visible field label or grid column header defined in the source-backed xaml. 8 add historization visible label, button, tab, or grid header defined in the source-backed xaml. 9 hub schema visible field label or grid column header defined in the source-backed xaml. 10 hub name visible field label or grid column header defined in the source-backed xaml. 11 hist package visible field label or grid column header defined in the source-backed xaml. 12 create linksat visible label, button, tab, or grid header defined in the source-backed xaml. related topics create calendar dimension create export create historization"}
,{"id":386707109064,"name":"Create export","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-export","breadcrumb":"Reference › User Interface › Wizards › Create export","description":"","searchText":"reference user interface wizards create export overview create export is implemented as the export wizard wizard or assistant in analyticscreator. function the wizard is defined in assistent_newexport.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newexport.xaml and assistent_newexport.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create export. how to access navigation tree opened from the owning command or workflow. toolbar not confirmed in the ribbon. use the related export workflow. diagram architecture object menu -> add -> export visual element assistent_newexport screen overview the create export wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 source visible field label or grid column header defined in the source-backed xaml. 2 connector visible field label or grid column header defined in the source-backed xaml. 3 target visible label, button, tab, or grid header defined in the source-backed xaml. 4 package visible field label or grid column header defined in the source-backed xaml. 5 cancel closes the screen without saving changes. 6 finish completes the wizard. related topics create calendar dimension create datavault object create historization create import"}
,{"id":386707109065,"name":"Create historization","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-historization","breadcrumb":"Reference › User Interface › Wizards › Create historization","description":"","searchText":"reference user interface wizards create historization overview create historization is implemented as the historization wizard wizard or assistant in analyticscreator. function the wizard is defined in assistent_newhist.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newhist.xaml and assistent_newhist.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create historization. how to access navigation tree opened from the owning command or workflow. toolbar not direct in the ribbon. use the diagram add menu or etl list flow. diagram architecture -> add -> historization visual element assistent_newhist screen overview the create historization wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 source table visible field label or grid column header defined in the source-backed xaml. 2 target schema visible field label or grid column header defined in the source-backed xaml. 3 target table name visible field label or grid column header defined in the source-backed xaml. 4 package visible field label or grid column header defined in the source-backed xaml. 5 scd type visible field label or grid column header defined in the source-backed xaml. 6 empty record behaviour visible label, button, tab, or grid header defined in the source-backed xaml. 7 use vault id as pk visible label, button, tab, or grid header defined in the source-backed xaml. 8 scd 0 visible label, button, tab, or grid header defined in the source-backed xaml. 9 scd 1 visible label, button, tab, or grid header defined in the source-backed xaml. 10 scd 2 visible label, button, tab, or grid header defined in the source-backed xaml. 11 close visible label, button, tab, or grid header defined in the source-backed xaml. 12 do not close visible label, button, tab, or grid header defined in the source-backed xaml. related topics create datavault object create export create import create snapshot dimension"}
,{"id":386707109066,"name":"Create import","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-import","breadcrumb":"Reference › User Interface › Wizards › Create import","description":"","searchText":"reference user interface wizards create import overview create import is implemented as the import wizard wizard or assistant in analyticscreator. function the wizard is defined in assistent_newimp.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newimp.xaml and assistent_newimp.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create import. how to access navigation tree opened from the owning command or workflow. toolbar not direct in the ribbon. use the diagram add menu or etl list flow. diagram architecture -> add -> import visual element assistent_newimp screen overview the create import wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 source visible field label or grid column header defined in the source-backed xaml. 2 target schema visible field label or grid column header defined in the source-backed xaml. 3 target table name visible field label or grid column header defined in the source-backed xaml. 4 package visible field label or grid column header defined in the source-backed xaml. 5 cancel closes the screen without saving changes. 6 finish completes the wizard. related topics create export create historization create snapshot dimension create source"}
,{"id":386707109067,"name":"Create snapshot dimension","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-snapshot-dimension","breadcrumb":"Reference › User Interface › Wizards › Create snapshot dimension","description":"","searchText":"reference user interface wizards create snapshot dimension overview create snapshot dimension is implemented as the new snapshot dimension wizard or assistant in analyticscreator. function the wizard is defined in assistent_newsnapshottrans.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newsnapshottrans.xaml and assistent_newsnapshottrans.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create snapshot dimension. how to access navigation tree opened from the owning command or workflow. toolbar etl -> snapshot dimension diagram architecture -> add -> snapshot dimension visual element assistent_newsnapshottrans screen overview the create snapshot dimension wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 schema visible field label or grid column header defined in the source-backed xaml. 2 name visible field label or grid column header defined in the source-backed xaml. 3 stars visible label, button, tab, or grid header defined in the source-backed xaml. 4 transformation visible label, button, tab, or grid header defined in the source-backed xaml. 5 cancel closes the screen without saving changes. 6 finish completes the wizard. related topics create historization create import create source create time dimension"}
,{"id":386707109068,"name":"Create source","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-source","breadcrumb":"Reference › User Interface › Wizards › Create source","description":"","searchText":"reference user interface wizards create source overview create source is implemented as the source wizard wizard or assistant in analyticscreator. function the wizard is defined in assistent_newsource.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newsource.xaml and assistent_newsource.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create source. how to access navigation tree opened from the owning command or workflow. toolbar sources -> add diagram architecture -> add -> data source visual element assistent_newsource screen overview the create source wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 exist visible label, button, tab, or grid header defined in the source-backed xaml. 2 type visible field label or grid column header defined in the source-backed xaml. 3 schema visible field label or grid column header defined in the source-backed xaml. 4 table name visible field label or grid column header defined in the source-backed xaml. 5 description visible field label or grid column header defined in the source-backed xaml. 6 connector visible field label or grid column header defined in the source-backed xaml. 7 table visible field label or grid column header defined in the source-backed xaml. 8 query visible label, button, tab, or grid header defined in the source-backed xaml. 9 filter schema filter-related control or command defined in the source-backed ui. 10 filter table filter-related control or command defined in the source-backed ui. 11 retreive relations visible label, button, tab, or grid header defined in the source-backed xaml. 12 sap description language visible field label or grid column header defined in the source-backed xaml. related topics create import create snapshot dimension create time dimension create transformation"}
,{"id":386707109069,"name":"Create time dimension","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-time-dimension","breadcrumb":"Reference › User Interface › Wizards › Create time dimension","description":"","searchText":"reference user interface wizards create time dimension overview create time dimension is implemented as the new time transformation wizard or assistant in analyticscreator. function the wizard is defined in assistent_newtimetrans.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newtimetrans.xaml and assistent_newtimetrans.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create time dimension. how to access navigation tree opened from the owning command or workflow. toolbar etl -> time dimension diagram architecture -> add -> time dimension visual element assistent_newtimetrans screen overview the create time dimension wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 schema visible field label or grid column header defined in the source-backed xaml. 2 name visible field label or grid column header defined in the source-backed xaml. 3 period (minutes) visible label, button, tab, or grid header defined in the source-backed xaml. 4 time-to-id function visible label, button, tab, or grid header defined in the source-backed xaml. 5 stars visible label, button, tab, or grid header defined in the source-backed xaml. 6 cancel closes the screen without saving changes. 7 finish completes the wizard. related topics create snapshot dimension create source create transformation hash keys"}
,{"id":386707109070,"name":"Create transformation","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-create-transformation","breadcrumb":"Reference › User Interface › Wizards › Create transformation","description":"","searchText":"reference user interface wizards create transformation overview create transformation is implemented as the transformation wizard wizard or assistant in analyticscreator. function the wizard is defined in assistent_newtransformation.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newtransformation.xaml and assistent_newtransformation.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for create transformation. how to access navigation tree opened from the owning command or workflow. toolbar etl -> new transformation diagram architecture -> add -> transformation visual element assistent_newtransformation screen overview the create transformation wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 main tab header defined in the source-backed xaml. 2 tables tab header defined in the source-backed xaml. 3 fields tab header defined in the source-backed xaml. 4 other tab header defined in the source-backed xaml. 5 script tab header defined in the source-backed xaml. 6 table visible field label or grid column header defined in the source-backed xaml. 7 is output table visible field label or grid column header defined in the source-backed xaml. 8 type visible field label or grid column header defined in the source-backed xaml. 9 schema visible field label or grid column header defined in the source-backed xaml. 10 name visible field label or grid column header defined in the source-backed xaml. 11 historizing type visible field label or grid column header defined in the source-backed xaml. 12 main table visible field label or grid column header defined in the source-backed xaml. related topics create source create time dimension hash keys persist transformation"}
,{"id":386707109071,"name":"DWH wizard","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-dwh-wizard","breadcrumb":"Reference › User Interface › Wizards › DWH wizard","description":"","searchText":"reference user interface wizards dwh wizard overview the dwh wizard in analyticscreator provides a metadata-driven interface to import source structures and define how they will be transformed and loaded into the data warehouse. function use the wizard to select source metadata, classify objects as imports, transformations, historized tables, dimensions, or facts, and define naming and generation options before creating dwh objects. access the wizard can be opened from the toolbar, from the connector context menu in the navigation tree, or from the diagram canvas context menu. how to access navigation tree connectors -> connector -> dwh wizard toolbar file -> dwh wizard diagram canvas (right-click) -> dwh wizard visual element not confirmed. screen overview id property description a metadata source and filtering select the connector, choose the dwh type, load metadata from the connector or existing sources, and apply schema or table filters. b source object selection browse and select the source objects that should be included in the generated warehouse model. c object configuration and classification configure the selected objects as imports, transformations, historized tables, dimensions, or facts. id property description 1 exists in dwh read-only. checked if the object already exists and will be refreshed. 2 type object type (table, view, deltaq, odp). 3 schema schema name of the source object. 4 table name name of the source table or view. 5 description marks the object for import. id property description 1 exists in dwh read-only. checked if the object already exists and will be refreshed. 2 connector shows the connector assigned to the selected source object. 3 type object type (table, view, deltaq, odp). 4 schema schema name of the source object. 5 table name name of the source table or view. 6 import marks the object for import. 7 trans creates a transformation for the object after import. 8 hist enables historization (scd type 2). 9 dimension defines the object as a dimension table. 10 fact defines the object as a fact table. id property description 1 tables per package defines the maximum number of tables that will be grouped into a single ssis or adf package during deployment. 2 import package names template used for naming import packages. variables like {connector_name} and {nr} ensure unique and consistent naming. 3 historizing package names naming pattern for packages that handle historization (e.g., slowly changing dimensions). 4 table names naming convention template for physical table names generated in the dwh. 5 transformation names defines how transformation objects (views, procedures, or logic layers) will be named. 6 dimension names template for naming dimension objects derived from source tables. 7 fact names naming convention for fact tables in the dimensional model. 8 hub package name pattern for naming packages responsible for generating hub entities (datavault 2.0 only). 9 sat package name template for naming packages that generate satellite (sat) entities. 10 link package name pattern used to name link package files (relationships between hubs). 11 hub transformation name naming convention for transformation logic related to hubs. 12 sat transformation name template used to name sat transformation views or queries. 13 link transformation name defines naming pattern for transformations related to links. 14 hub table name naming format for physical hub tables in the dwh. 15 sat table name naming template for satellite tables. 16 link table name format used to name link tables, which store relationships. 17 linksat table name naming convention for link-satellite tables (hybrid structures in dv2.0). 18 key field name pattern for foreign key field names, typically prefixed with fk_ . 19 calendar in facts name naming template for calendar-related foreign keys in fact tables. id property description 1 field name appearance choose how field names appear: no changes / upper case / lower case. 2 retrieve relations attempts to detect foreign key relationships from the source database. 3 create snapshot dimension if enabled, creates a snapshot dimension (inactive if one already exists). 4 create calendar dimension if enabled, creates a calendar/time dimension (inactive if one already exists). 5 calendar dimension name name of the calendar dimension to be created. 6 calendar period start and end date for the calendar dimension. 7 include tables in facts n:1 direct related — include directly n:1 related tables in the fact transformation. all direct related — include all directly related tables in the fact transformation. n:1 direct and indirect related — include both directly and indirectly related n:1 tables. all direct and indirect related — include all directly and indirectly related tables. 8 sap deltaq transfer mode idoc — defines the transfer mode for sap deltaq sources. t-rfc — language used to retrieve descriptions from sap. 9 sap description language language used to retrieve descriptions from sap. 10 use friendly names in transformation as column names if enabled, uses friendly names (if available) in generated transformation columns. 11 default transformations no defaults — no predefined transformation templates are used. all defaults — all predefined transformation templates will be applied. selected defaults — only the selected predefined templates will be applied. 12 default transformations (list) list of available transformation templates (used if “selected defaults” is chosen). 13 stars defines star schemas to create facts and dimensions. 14 schemas for the generated objects specifies target schemas for each layer: • import tables • import transformations • historized tables • facts and dimensions 15 column names first row blob-specific: indicates that the first row of the file contains column headers. 16 code page defines text encoding format (e.g., 65001 - unicode utf-8 ). 17 text qualifier character used to wrap values in text fields (e.g., \" or ' ). 18 column delimiter delimiter used in blob files. supports {cr} (carriage return), {lf} (line feed), and {t} (tab). related topics create calendar dimension create datavault object create export create historization"}
,{"id":386707109072,"name":"Hash keys","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-hash-keys","breadcrumb":"Reference › User Interface › Wizards › Hash keys","description":"","searchText":"reference user interface wizards hash keys overview hash keys is implemented as the add or refresh hash keys in all tables wizard or assistant in analyticscreator. function the wizard is defined in assistent_hash.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_hash.xaml and assistent_hash.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for hash keys. how to access navigation tree opened from the owning command or workflow. toolbar not direct in the ribbon. use the diagram hash-key command. diagram architecture -> add/refresh hash keys visual element assistent_hash screen overview the hash keys wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 add or refresh primary hash keys visible label, button, tab, or grid header defined in the source-backed xaml. 2 add or refresh referenced hash keys visible field label or grid column header defined in the source-backed xaml. 3 replace references in transformations due the hash references visible field label or grid column header defined in the source-backed xaml. 4 cancel closes the screen without saving changes. 5 finish completes the wizard. related topics create time dimension create transformation persist transformation run object script"}
,{"id":386707109073,"name":"Persist transformation","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-persist-transformation","breadcrumb":"Reference › User Interface › Wizards › Persist transformation","description":"","searchText":"reference user interface wizards persist transformation overview persist transformation is implemented as the persisting wizard wizard or assistant in analyticscreator. function the wizard is defined in assistent_newpers.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistent_newpers.xaml and assistent_newpers.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for persist transformation. how to access navigation tree opened from the owning command or workflow. toolbar not direct in the ribbon. use the related transformation flow. diagram architecture -> add -> persisting visual element assistent_newpers screen overview the persist transformation wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 transformation visible label, button, tab, or grid header defined in the source-backed xaml. 2 persist table visible field label or grid column header defined in the source-backed xaml. 3 persist package visible field label or grid column header defined in the source-backed xaml. 4 no partition switching visible field label or grid column header defined in the source-backed xaml. 5 partition switching visible field label or grid column header defined in the source-backed xaml. 6 renaming visible label, button, tab, or grid header defined in the source-backed xaml. 7 cancel closes the screen without saving changes. 8 finish completes the wizard. related topics create transformation hash keys run object script"}
,{"id":386707109074,"name":"Run object script","type":"topic","path":"/docs/reference/user-interface/wizards/wizards-run-object-script","breadcrumb":"Reference › User Interface › Wizards › Run object script","description":"","searchText":"reference user interface wizards run object script overview run object script is implemented as the run object script wizard or assistant in analyticscreator. function the wizard is defined in assistentrunscript.xaml and its code-behind manages the step navigation and finish actions for this creation flow. access this topic was rebuilt from assistentrunscript.xaml and assistentrunscript.xaml.cs. the source defines the wizard tabs, fields, and navigation buttons for run object script. how to access navigation tree opened from the owning command or workflow. toolbar not direct. open from the object-script execution flow. diagram not confirmed. visual element assistentrunscript screen overview the run object script wizard exposes the following source-defined tabs, labels, buttons, and grid headers. id property description 1 paramnr visible label, button, tab, or grid header defined in the source-backed xaml. 2 parameter visible label, button, tab, or grid header defined in the source-backed xaml. 3 value visible label, button, tab, or grid header defined in the source-backed xaml. 4 object visible label, button, tab, or grid header defined in the source-backed xaml. 5 object id visible label, button, tab, or grid header defined in the source-backed xaml. 6 timeout (sec) visible label, button, tab, or grid header defined in the source-backed xaml. 7 cancel closes the screen without saving changes. 8 run script visible label, button, tab, or grid header defined in the source-backed xaml. related topics hash keys persist transformation"}
,{"id":383461259455,"name":"Entity types","type":"section","path":"/docs/reference/entity-types","breadcrumb":"Reference › Entity types","description":"","searchText":"reference entity types entity types define the structural and behavioral categories used throughout analyticscreator. they describe how connectors, sources, tables, transformations, packages, scripts, schemas, and historization options are classified and handled within the generated data warehouse model. use this section to understand the available entity type groups and navigate to the appropriate reference area for your modeling and execution scenario. available entity type groups connector types defines how analyticscreator connects to source systems and external providers. relational databases files and cloud storage sap and service-based interfaces open connector types source types defines how source data is read and what technical form the source object takes. table and view sources query-based sources sap source patterns open source types table types defines how tables behave in staging, historization, dimensional models, and data vault models. import, historized, and persisting tables dimension and fact tables datavault hubs, links, and satellites open table types transformation types defines how transformation logic is generated, maintained, or executed. regular and datamart transformations manual, script, and external logic union and connector-related transformations open transformation types join historization types defines how historical validity is handled when joining historized structures. current-state and full history joins historical from and historical to behavior historization-aware join options open join historization types package types defines the execution units used for loading, historization, persisting, orchestration, and external processing. import and workflow packages historization and persisting packages script, export, and external packages open package types sql script types defines when custom sql scripts are executed within creation, workflow, deployment, and repository-extension processes. pre and post creation pre and post workflow pre and post deployment, repository extension open sql script types schema types defines the structural layers used in the generated warehouse architecture. staging and persisted staging transformation and core datamart layer open schema types how to use this section each subsection focuses on one entity type group and explains the available options within that area. use connector types and source types for source integration topics use table types, schema types, and transformation types for warehouse modeling topics use join historization types for historized join behavior use package types and sql script types for execution and lifecycle-related topics key takeaway entity types define the major structural and behavioral categories used in analyticscreator and provide the reference model for connectors, sources, tables, transformations, execution units, scripts, and schemas."}
,{"id":383509396685,"name":"Connector types","type":"subsection","path":"/docs/reference/entity-types/connector-types","breadcrumb":"Reference › Entity types › Connector types","description":"","searchText":"reference entity types connector types connector types define how analyticscreator connects to source systems and external data providers. they determine how metadata is accessed and how source data can be integrated into the generated data warehouse flow. use this section to understand the available connector types and choose the appropriate connector for your source technology and integration scenario. available connector types mssql connector for microsoft sql server sources and metadata import. relational source access table and metadata import common warehouse source type open reference oracle connector for oracle-based source systems. relational source integration metadata-driven access suitable for oracle source landscapes open reference excel connector for excel-based source files. file-based source access structured spreadsheet input useful for departmental data sources open reference csv connector for delimited text file sources. flat file ingestion simple structured source format suitable for exchange files open reference access connector for microsoft access source files and databases. legacy source support file-based database access useful for smaller existing data stores open reference oledb generic connector based on ole db provider access. flexible connectivity option useful for supported provider-based sources suitable for heterogeneous environments open reference sap connector for sap metadata and source integration scenarios. sap metadata import relevant for erp integration supports sap-oriented modeling flows open reference odbc generic connector based on odbc driver access. broad compatibility useful for many relational systems driver-based connection model open reference direct connector type for direct source access scenarios. direct integration pattern reduced abstraction layer useful for specific source access cases open reference oledb.net connector based on ole db .net provider access. .net-based provider model useful for provider-specific integrations extends connectivity options open reference azure blob connector for file-based and object-based sources in azure blob storage. cloud storage integration useful for landing and exchange zones supports azure-based source scenarios open reference odata connector for odata-based service endpoints and api-style data access. service-oriented integration useful for api-style sources supports metadata-driven remote access open reference how to choose a connector type use mssql or oracle for direct relational database integration use excel, csv, or access for file-based and desktop data sources use sap for sap-oriented metadata and source integration use odbc, oledb, or oledb.net for generic provider-based connectivity use azure blob for cloud storage-based source scenarios use odata for service-based or api-style access use direct when a direct connector pattern is required for the source integration scenario key takeaway connector types define how analyticscreator accesses metadata and source data across relational databases, files, enterprise systems, cloud storage, and service-based interfaces."}
,{"id":386708347109,"name":"MSSQL","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-mssql","breadcrumb":"Reference › Entity types › Connector types › MSSQL","description":"","searchText":"reference entity types connector types mssql overview mssql is a connector type in analyticscreator. function this connector type is used to classify connectors of type mssql. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the mssql connector type is configured in the new connector page after selecting mssql in the connector-type dropdown. the page also shows a help note that #encrypted_string# aliases can be used instead of plain-text passwords through options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select mssql. 3 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 4 azure source type select the source type shown in the connector configuration. 5 connection string enter the sql server ole db connection string. the template uses provider={provider};data source=[server];initial catalog=[database];integrated security=sspi;, where the provider is resolved from the installed sql server ole db driver and can be msoledbsql, sqlncli11, or sqlncli10. 6 template inserts the default sql server ole db connection-string template. 7 test connection tests the mssql connection settings. 8 cancel closes the page without saving. 9 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":386708347114,"name":"Oracle","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-oracle","breadcrumb":"Reference › Entity types › Connector types › Oracle","description":"","searchText":"reference entity types connector types oracle overview oracle is a connector type in analyticscreator. function this connector type is used to classify connectors of type oracle. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the oracle connector is configured in the new connector page after selecting oracle in the connector-type dropdown. the page also shows a help note that #encrypted_string# aliases can be used instead of plain-text passwords through options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select oracle. 3 azure source type select the source type shown in the connector configuration. 4 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 5 connection string enter the oracle ole db connection string, for example provider=oraoledb.oracle;data source=(description =(address =(protocol=tcp)(host=[host])(port=[port]))(connectdata=(server=dedicated)(servicename=[servicename])));user id=[user];password=[password];. 6 template inserts the default oracle ole db connection-string template. 7 test connection tests the oracle connection settings. 8 cancel closes the page without saving. 9 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":386708347108,"name":"Excel","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-excel","breadcrumb":"Reference › Entity types › Connector types › Excel","description":"","searchText":"reference entity types connector types excel overview excel is a connector type in analyticscreator. function this connector type is used to classify connectors of type excel. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the excel connector type is configured in the new connector page after selecting excel in the connector-type dropdown. id property description 1 connector name enter the connector name. 2 connector type select excel. 3 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 4 azure source type select the source type shown in the connector configuration. 5 connection string use a connection string such as provider=microsoft.ace.oledb.12.0;data source=[fullpath_to_file];extended properties=\"excel 12.0 xml;hdr=yes;imex=1\";. 6 template select the template used for the excel connector. 7 test connection tests the excel connection settings. 8 cancel closes the page without saving. 9 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":386708347106,"name":"CSV","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-csv","breadcrumb":"Reference › Entity types › Connector types › CSV","description":"","searchText":"reference entity types connector types csv overview csv is a connector type in analyticscreator. function this connector type is used to classify connectors of type csv. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the csv connector type is configured in the new connector page after selecting csv in the connector-type dropdown. the page also states that #encryptedstring# aliases can be used instead of plain-text passwords by using options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select csv. 3 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 4 azure source type select the source type shown in the connector configuration. 5 column names first row controls whether the first row contains column names. 6 unicode controls whether the csv file is read as unicode. 7 locale set the locale, for example english. 8 code page set the code page, for example 1252 - western european (windows). 9 format set the file format value, for example 0. 10 text qualifier specify the character used to qualify text values. 11 header row delimiter (use {cr}, {lf} and {t}) set the header row delimiter, for example {cr}{lf}. 12 header rows to skip set the number of header rows to skip, for example 0. 13 row delimiter (use {cr}, {lf} and {t}) set the row delimiter, for example {cr}{lf}. 14 column delimiter (use {cr}, {lf} and {t}) set the column delimiter, for example ;. 15 cancel closes the page without saving. 16 save saves the connector configuration. related topics access azure blob direct excel"}
,{"id":386708347104,"name":"Access","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-access","breadcrumb":"Reference › Entity types › Connector types › Access","description":"","searchText":"reference entity types connector types access overview access is a connector type in analyticscreator. function this connector type is used to classify connectors of type access. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the access connector type. related topics connector types connector"}
,{"id":386708347112,"name":"OLEDB","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-oledb","breadcrumb":"Reference › Entity types › Connector types › OLEDB","description":"","searchText":"reference entity types connector types oledb overview oledb is a connector type in analyticscreator. function this connector type is used to classify connectors of type oledb. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the oledb connector is configured in the new connector page after selecting oledb in the connector-type dropdown. the page also shows a help note that #encrypted_string# aliases can be used instead of plain-text passwords through options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select oledb. 3 azure source type select the source type shown in the connector configuration. 4 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 5 connection string enter the ole db connection string. 6 template template button for the connection string field. the connector-editor source does not define an oledb-specific default template. 7 test connection tests the oledb connection settings. 8 cancel closes the page without saving. 9 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":386708347115,"name":"SAP","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-sap","breadcrumb":"Reference › Entity types › Connector types › SAP","description":"","searchText":"reference entity types connector types sap overview sap is a connector type in analyticscreator. function this connector type is used to classify connectors of type sap. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the sap connector is configured in the new connector page after selecting sap in the connector-type dropdown. the page also shows a help note that #encrypted_string# aliases can be used instead of plain-text passwords through options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select sap. 3 azure source type select the source type shown in the connector configuration. 4 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 5 connection string enter the sap connection string, for example ashost=[hostname] sysnr=[system_number] client=[mandant] lang=[lanquage] user=[user] passwd=[password]. 6 template inserts the default sap connection-string template. 7 test connection tests the sap connection settings. 8 cancel closes the page without saving. 9 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":386708347111,"name":"ODBC","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-odbc","breadcrumb":"Reference › Entity types › Connector types › ODBC","description":"","searchText":"reference entity types connector types odbc overview odbc is a connector type in analyticscreator. function this connector type is used to classify connectors of type odbc. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the odbc connector is configured in the new connector page after selecting odbc in the connector-type dropdown. the page also shows a help note that #encrypted_string# aliases can be used instead of plain-text passwords through options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select odbc. 3 azure source type select the source type shown in the connector configuration. 4 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 5 connection string enter the odbc connection string, for example dsn=[dsn];uid=[user];pwd=[password]. 6 template inserts the default odbc connection-string template. 7 test connection tests the odbc connection settings. 8 cancel closes the page without saving. 9 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":386708347107,"name":"Direct","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-direct","breadcrumb":"Reference › Entity types › Connector types › Direct","description":"","searchText":"reference entity types connector types direct overview direct is a connector type in analyticscreator. function this connector type is used to classify connectors of type direct. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the direct connector type is configured in the new connector page after selecting direct in the connector-type dropdown. id property description 1 connector name enter the connector name. 2 connector type select direct. 3 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 4 azure source type select the source type shown in the connector configuration. 5 server name enter the server name for the direct connection. 6 server sqlcmd variable enter the sqlcmd variable used for the server name. 7 database name enter the database name for the direct connection. 8 database sqlcmd variable enter the sqlcmd variable used for the database name. related topics access azure blob csv excel"}
,{"id":386708347113,"name":"OLEDB.NET","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-oledb-net","breadcrumb":"Reference › Entity types › Connector types › OLEDB.NET","description":"","searchText":"reference entity types connector types oledb.net overview oledb.net is a connector type in analyticscreator. function this connector type is used to classify connectors of type oledb.net. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the oledb.net connector is configured in the new connector page after selecting oledb.net in the connector-type dropdown. the page also shows a help note that #encrypted_string# aliases can be used instead of plain-text passwords through options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select oledb.net. 3 azure source type select the source type shown in the connector configuration. 4 do not store connection string in cfg.ssis_configurations controls whether the connection string is excluded from cfg.ssis_configurations. 5 connection string enter the ole db .net provider connection string. 6 template template button for the connection string field. the connector-editor source does not define an oledb.net-specific default template. 7 test connection tests the oledb.net connection settings. 8 cancel closes the page without saving. 9 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":386708347105,"name":"Azure BLOB","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-azure-blob","breadcrumb":"Reference › Entity types › Connector types › Azure BLOB","description":"","searchText":"reference entity types connector types azure blob overview azure blob is a connector type in analyticscreator. function this connector type is used to classify connectors of type azure blob. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the azure blob connector type is configured in the new connector page after selecting azure blob in the connector-type dropdown. a later screenshot can use a microsoft contoso example. id property description 1 connector name enter the connector name, for example contoso azure blob. 2 connector type select azure blob from the dropdown list. 3 azure source type select the azure source type required for the connector scenario. 4 storage account enter the storage account name, for example contosodata. 5 azure key enter the azure access key for the selected storage account. related topics access csv direct excel"}
,{"id":386708347110,"name":"Odata","type":"topic","path":"/docs/reference/entity-types/connector-types/connector-types-odata","breadcrumb":"Reference › Entity types › Connector types › Odata","description":"","searchText":"reference entity types connector types odata overview odata is a connector type in analyticscreator. function this connector type is used to classify connectors of type odata. access this connector type belongs to the connector types section in analyticscreator. how to access navigation tree connectors -> right-click -> add connector toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the odata connector is configured in the new connector page after selecting odata in the connector-type dropdown. the page also shows a help note that #encrypted_string# aliases can be used instead of plain-text passwords through options->encrypted strings. id property description 1 connector name enter the connector name. 2 connector type select odata. 3 azure source type select the azure source type shown in the connector configuration. 4 do not store connection string in cfg.ssis_configurations controls whether the connector configuration is excluded from cfg.ssis_configurations. 5 url enter the odata service url. 6 authentication choose the authentication mode: none, windows, or basic. 7 login enter the login when basic authentication is selected. 8 password enter the password when basic authentication is selected. 9 test connection tests the odata connection by requesting the service metadata. 10 cancel closes the page without saving. 11 save saves the connector configuration. related topics access azure blob csv direct"}
,{"id":383509396687,"name":"Source types","type":"subsection","path":"/docs/reference/entity-types/source-types","breadcrumb":"Reference › Entity types › Source types","description":"","searchText":"reference entity types source types source types define how data is read into analyticscreator and how the source object behaves during import and processing. use this section to understand the available source types and choose the appropriate one for your source system and loading pattern. available source types table use a table source when data should be read directly from a physical source table. direct table-based import typical default source type suitable for standard relational loading open reference query use a query source when the input should be defined by a custom sql statement instead of a direct table reference. custom query-based source definition useful for filtered or pre-shaped input more flexible than direct table access open reference sap deltaq use sap deltaq when loading sap extractor-based data with delta handling. sap-specific source type supports extractor-oriented loading scenarios relevant for delta-based sap integration open reference view use a view source when data should be read from a database view instead of a physical table. view-based source access useful for predefined source abstraction suitable when logic is already encapsulated in the source open reference how to choose a source type use table for standard relational source loading use view when the source system already exposes the required structure through a database view use query when the source needs custom filtering or shaping before import use sap deltaq for sap extractor scenarios with delta-oriented loading behavior key takeaway source types define how source data is accessed and should be selected based on the technical structure and loading behavior of the source system."}
,{"id":386708347123,"name":"Table","type":"topic","path":"/docs/reference/entity-types/source-types/entity-types-source-types-table","breadcrumb":"Reference › Entity types › Source types › Table","description":"","searchText":"reference entity types source types table overview table is source type 1 (table). it is the default source type for new sources. function this type defines a source that reads from a physical table. the define source page keeps the query tab hidden and uses the definition tab for source columns. access this source type is configured in the define source page after reading or editing a source and choosing table in the type list. how to access navigation tree sources -> connector -> right-click -> read source from connector toolbar sources -> sources diagram not applicable. visual element define source -> type screen overview id property description 1 source name defines the source name. 2 source schema stores the source schema. 3 connector selects the connector used by the source. 4 group assigns the source to a group. 5 type sets the source type to table. 6 friendly name stores the friendly display name of the source. 7 anonymization check statement stores the anonymization check statement for the source. 8 description stores the source description. 9 definition tab shows the source-column definition grid. 10 column name stores the source-column name. 11 data type stores the source-column data type. 12 referenced column links the source column to a referenced key column when needed. 13 description stores the source-column description. 14 constraints opens the source constraints dialog for a stored source. 15 cancel returns to the previous page without saving. 16 save saves the source definition. related topics query sap_deltaq sap_odp view"}
,{"id":386708347120,"name":"Query","type":"topic","path":"/docs/reference/entity-types/source-types/entity-types-source-types-query","breadcrumb":"Reference › Entity types › Source types › Query","description":"","searchText":"reference entity types source types query overview query is source type 4 (query). it is used for sources defined by a sql query instead of a physical table or view. function selecting query shows the query tab in define source and changes the secondary action button to test query. saving a changed query refreshes the source structure. access this source type is configured in the define source page after creating or editing a source and choosing query in the type list. how to access navigation tree sources -> connector -> right-click -> create new source toolbar sources -> sources diagram not applicable. visual element define source -> type screen overview id property description 1 source name defines the source name. 2 source schema stores the source schema. 3 connector selects the connector used by the source. 4 group assigns the source to a group. 5 type sets the source type to query. 6 friendly name stores the friendly display name of the source. 7 anonymization check statement stores the anonymization check statement for the source. 8 description stores the source description. 9 definition tab shows the source-column definition grid. 10 query tab becomes visible when the source type is query. 11 query stores the sql query. the query cannot be empty for source type query. 12 test query tests the current query text. 13 constraints opens the source constraints dialog for a stored source. 14 cancel returns to the previous page without saving. 15 save saves the source. if the query changed, the source structure is refreshed. related topics sap_deltaq sap_odp table view"}
,{"id":386708347121,"name":"SAP_DELTAQ","type":"topic","path":"/docs/reference/entity-types/source-types/entity-types-source-types-sap-deltaq","breadcrumb":"Reference › Entity types › Source types › SAP_DELTAQ","description":"","searchText":"reference entity types source types sap_deltaq overview sap_deltaq is source type 3. it is used for sap delta queue sources on sap connectors. function selecting sap_deltaq on an sap connector shows the sap deltaq/odp pane in deltaq mode with extractor, update mode, auto sync, queue type, log destination, and rfc destination. access this source type is configured in the define source page after reading or editing a source on an sap connector and choosing sap_deltaq in the type list. how to access navigation tree sources -> connector -> right-click -> read source from connector toolbar sources -> sources diagram not applicable. visual element define source -> type screen overview id property description 1 source name defines the source name. 2 source schema stores the source schema. 3 connector selects the sap connector used by the source. 4 group assigns the source to a group. 5 type sets the source type to sap_deltaq. 6 friendly name stores the friendly display name of the source. 7 anonymization check statement stores the anonymization check statement for the source. 8 description stores the source description. 9 definition tab shows the source-column definition grid. 10 extractor stores the sap extractor name. 11 mode selects the sap deltaq update mode. 12 auto sync. controls automatic synchronization for the source. 13 type selects the sap deltaq source type inside the sap deltaq/odp pane. 14 log.destination selects or stores the sap log destination. 15 rfc destination selects or stores the sap rfc destination. 16 constraints opens the source constraints dialog for a stored source. 17 cancel returns to the previous page without saving. 18 save saves the source definition. related topics query sap_odp table view"}
,{"id":386708347122,"name":"SAP_ODP","type":"topic","path":"/docs/reference/entity-types/source-types/entity-types-source-types-sap-odp","breadcrumb":"Reference › Entity types › Source types › SAP_ODP","description":"","searchText":"reference entity types source types sap_odp overview sap_odp is source type 5. it is used for sap odp sources on sap connectors. function selecting sap_odp on an sap connector shows the sap deltaq/odp pane in odp mode with context, update mode, semantic, and full or delta capability flags. access this source type is configured in the define source page after reading or editing a source on an sap connector and choosing sap_odp in the type list. how to access navigation tree sources -> connector -> right-click -> read source from connector toolbar sources -> sources diagram not applicable. visual element define source -> type screen overview id property description 1 source name defines the source name. 2 source schema stores the source schema. 3 connector selects the sap connector used by the source. 4 group assigns the source to a group. 5 type sets the source type to sap_odp. 6 friendly name stores the friendly display name of the source. 7 anonymization check statement stores the anonymization check statement for the source. 8 description stores the source description. 9 definition tab shows the source-column definition grid. 10 context stores the sap odp context. 11 mode selects the odp update mode. 12 auto sync. controls automatic synchronization for the source. 13 semantic selects the sap odp semantic. 14 supports full shows whether full extraction is supported. 15 supports delta shows whether delta extraction is supported. 16 constraints opens the source constraints dialog for a stored source. 17 cancel returns to the previous page without saving. 18 save saves the source definition. related topics query sap_deltaq table view"}
,{"id":386708347124,"name":"VIEW","type":"topic","path":"/docs/reference/entity-types/source-types/entity-types-source-types-view","breadcrumb":"Reference › Entity types › Source types › VIEW","description":"","searchText":"reference entity types source types view overview view is source type 2 (view). it is used for sources backed by a database view. function this type uses the same source definition page as table and keeps the query tab hidden while the definition tab stores the source columns. access this source type is configured in the define source page after reading or editing a source and choosing view in the type list. how to access navigation tree sources -> connector -> right-click -> read source from connector toolbar sources -> sources diagram not applicable. visual element define source -> type screen overview id property description 1 source name defines the source name. 2 source schema stores the source schema. 3 connector selects the connector used by the source. 4 group assigns the source to a group. 5 type sets the source type to view. 6 friendly name stores the friendly display name of the source. 7 anonymization check statement stores the anonymization check statement for the source. 8 description stores the source description. 9 definition tab shows the source-column definition grid. 10 column name stores the source-column name. 11 data type stores the source-column data type. 12 referenced column links the source column to a referenced key column when needed. 13 description stores the source-column description. 14 constraints opens the source constraints dialog for a stored source. 15 cancel returns to the previous page without saving. 16 save saves the source definition. related topics query sap_deltaq sap_odp table"}
,{"id":383509396688,"name":"Table types","type":"subsection","path":"/docs/reference/entity-types/table-types","breadcrumb":"Reference › Entity types › Table types","description":"","searchText":"reference entity types table types table types define how tables behave in analyticscreator and what role they play in the generated data warehouse structure. use this section to understand the available table types and choose the appropriate one for staging, historization, persistence, dimensional modeling, or data vault modeling. available table types import table used to receive source data during import into the staging layer. entry point for source loading filled by generated workflows basis for downstream processing open reference historized table used to store historized data with validity periods and change tracking. supports history over time typical basis for persistent staging common for scd2-style processing open reference persisting table used to materialize transformation results physically instead of keeping them only as views. improves performance for complex logic stores generated output physically maintained by generated procedures open reference dimension table used to store descriptive business entities for dimensional modeling. typical star schema component contains descriptive attributes referenced by fact tables open reference externally filled table used when table content is populated outside the standard analyticscreator-generated loading process. externally maintained data not filled by standard generated import logic useful for integration scenarios open reference fact table used to store measurable business events and transactions in dimensional models. contains measures and foreign keys central table in star schemas supports analytical aggregation open reference datavault hub used to store stable business keys in data vault models. represents core business entities key-centric structure foundation of hub-based modeling open reference datavault link used to store relationships between business entities in data vault models. connects hubs represents business relationships supports scalable model design open reference datavault satellite used to store descriptive and changing attributes in data vault models. contains contextual attributes often historized by design separated from business keys open reference how to choose a table type use import table for source ingestion into staging use historized table when changes over time must be tracked use persisting table when transformation results should be materialized physically use dimension table and fact table for dimensional modeling use externally filled table when data is maintained outside the generated loading process use datavault hub, datavault link, and datavault satellite for data vault models key takeaway table types define how data is stored and modeled in analyticscreator, from source ingestion and historization to dimensional and data vault structures."}
,{"id":386676751607,"name":"Import table","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-import-table","breadcrumb":"Reference › Entity types › Table types › Import table","description":"","searchText":"reference entity types table types import table overview import table is the repository table type used for imported source tables. function the repository seeds tabletypeid = 1 as imp_table with the description import table. access this type is shown in the detailobjects page in the table type field. for this type the editor allows changing the table name and editing the full column definition grid. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the import table classification is represented in the table editor by the table type field and the editable table-definition controls. id property description 1 table name editable name of the import table. 2 table schema schema that owns the import table. 3 table type shows imp_table (tabletypeid = 1). 4 friendly name optional business-friendly name for the table. 5 description optional description stored with the table. 6 columns grid column definitions are editable and rows can be added or removed. 7 has primary key primary-key controls remain available for this type. related topics historizised table persisting table externally filled table direct-connector transformation"}
,{"id":386676751606,"name":"Historizised table","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-historizised-table","breadcrumb":"Reference › Entity types › Table types › Historizised table","description":"","searchText":"reference entity types table types historizised table overview historizised table is the repository table type used for historying tables. function the repository seeds tabletypeid = 2 as hist_table with the description historying table. access this type is shown in the detailobjects page in the table type field. when this type is selected the editor keeps the columns editable, disables manual identity configuration, and enables the hist of table, hub of table, satellite of table, and link of table selectors. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the historizised table classification is represented in the table editor by the table type field and the additional historization link fields that are enabled for this type. id property description 1 table name name of the historized table. 2 table schema schema that owns the historized table. 3 table type shows hist_table (tabletypeid = 2). 4 hist of table selector for the base table that is historized by this table. 5 hub of table enabled for this table type. 6 satellite of table enabled for this table type. 7 link of table enabled for this table type. 8 columns grid column definitions remain editable for this table type. related topics import table persisting table datavault hub datavault satellite"}
,{"id":386676751608,"name":"Persisting table","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-persisting-table","breadcrumb":"Reference › Entity types › Table types › Persisting table","description":"","searchText":"reference entity types table types persisting table overview persisting table is the repository table type used for persisted result tables. function the repository uses tabletypeid = 5 (persist_table) for the non-historized variant and tabletypeid = 6 (persist_table_hist) for the historized variant. access this type is shown in the detailobjects page in the table type field. for persisting table types the columns remain editable, but the table name is read-only because the persisted name is derived from the owning transformation. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the persisting table classification is represented in the table editor by the table type field and the persistence-related table metadata. id property description 1 table name read-only name of the persisted table. 2 table schema schema that owns the persisted table. 3 table type shows either persist_table or persist_table_hist. 4 persist of table read-only reference to the base table for persisted output. 5 description optional description stored with the table. 6 columns grid column definitions remain editable and rows can be added or removed. 7 definition tab enabled, because persisting tables are not views. related topics import table historizised table dimension table fact table"}
,{"id":386676751603,"name":"Dimension table","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-dimension-table","breadcrumb":"Reference › Entity types › Table types › Dimension table","description":"","searchText":"reference entity types table types dimension table overview dimension table is the datamart dimension table classification in analyticscreator. function the repository uses tabletypeid = 7 (datamart_dim_view) for a datamart dimension view without history and tabletypeid = 8 (datamart_dim_view_hist) for the historized variant. access this type is shown in the detailobjects page in the table type field. the type is marked as a view and as a datamart object, so the table editor exposes the olap controls and keeps the definition tab disabled. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the dimension table classification is represented in the table editor by the table type field and the olap-specific controls that become visible for datamart tables. id property description 1 table name name of the datamart dimension table. 2 table schema schema that owns the datamart object. 3 table type shows either datamart_dim_view or datamart_dim_view_hist. 4 olap perspective visible for datamart fact/dimension output and used to group olap objects. 5 export to olap visible because the selected table type is marked as a datamart type. 6 hidden in olap visibility toggle shown for datamart table types. 7 olap category category selector shown for datamart table types. 8 definition tab disabled because the type is a view. related topics fact table persisting table datamart transformation regular transformation"}
,{"id":386676751604,"name":"Externally filled table","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-externally-filled-table","breadcrumb":"Reference › Entity types › Table types › Externally filled table","description":"","searchText":"reference entity types table types externally filled table overview externally filled table is the table classification used when a result table is loaded by an external transformation. function the repository uses tabletypeid = 11 (extern_table) for the non-historized variant and tabletypeid = 12 (extern_table_hist) for the historized variant. access the detailobjects page binds the table type selector to types 11 and 12 for new and existing external result tables, and it shows the load field definitions from existing table button only for these types. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the externally filled table classification is represented in the table editor by the table type field and the external-load controls that are only enabled for table types 11 and 12. id property description 1 table name name of the external result table. 2 table schema schema that owns the external result table. 3 table type shows either extern_table or extern_table_hist. 4 columns grid column structure is editable for table types 11 and 12. 5 load field definitions from existing table button shown only for external table types so the field list can be loaded from an existing table. 6 definition tab enabled, because these types are not views. 7 has primary key primary-key controls remain available for these external table types. related topics persisting table import table external transformation script transformation"}
,{"id":386676751605,"name":"Fact table","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-fact-table","breadcrumb":"Reference › Entity types › Table types › Fact table","description":"","searchText":"reference entity types table types fact table overview fact table is the datamart fact table classification in analyticscreator. function the repository uses tabletypeid = 9 (datamart_fact_view) for a datamart fact view without history and tabletypeid = 10 (datamart_fact_view_hist) for the historized variant. access this type is shown in the detailobjects page in the table type field. the type is marked as a datamart view, so the olap controls are visible and the definition tab is disabled. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the fact table classification is represented in the table editor by the table type field and the olap-specific controls that are shown for datamart fact tables. id property description 1 table name name of the datamart fact table. 2 table schema schema that owns the datamart object. 3 table type shows either datamart_fact_view or datamart_fact_view_hist. 4 olap perspective visible for fact-table types 9 and 10. 5 export to olap visible because the selected table type is marked as a datamart type. 6 hidden in olap visibility toggle shown for datamart table types. 7 olap category category selector shown for datamart table types. 8 definition tab disabled because the type is a view. related topics dimension table persisting table datamart transformation regular transformation"}
,{"id":386676751600,"name":"DataVault Hub","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-datavault-hub","breadcrumb":"Reference › Entity types › Table types › DataVault Hub","description":"","searchText":"reference entity types table types datavault hub overview datavault hub is a table type used for hub tables in the analyticscreator repository model. function the repository seeds tabletypeid = 13 as vault_hub with the description data vault hub table with history. access this type is shown in the detailobjects page in the table type field. for this type the editor keeps the table name and column definitions read-only, because it falls into the non-editable branch of cbotabletype_selectionchanged. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the datavault hub table type is represented in the table editor by the table type selector and the surrounding table metadata fields. id property description 1 table name name of the table shown in the table editor. 2 table schema schema that owns the table. 3 table type shows the current table classification. for this type the repository value is vault_hub (tabletypeid = 13). 4 friendly name optional business-friendly name for the table. 5 description optional description stored with the table. 6 columns grid the editor keeps the structural column fields read-only for this type. 7 definition tab enabled, because this type is not marked as a view in intern.table_types. related topics datavault link datavault satellite historizised table import table"}
,{"id":386676751601,"name":"DataVault Link","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-datavault-link","breadcrumb":"Reference › Entity types › Table types › DataVault Link","description":"","searchText":"reference entity types table types datavault link overview datavault link is a table type used for link tables in the analyticscreator repository model. function the repository seeds tabletypeid = 15 as vault_link with the description data vault link table with history. access this type is shown in the detailobjects page in the table type field. for this type the editor keeps the table name and column definitions read-only. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the datavault link table type is represented in the table editor by the table type selector and the surrounding table metadata fields. id property description 1 table name name of the table shown in the table editor. 2 table schema schema that owns the table. 3 table type shows the current table classification. for this type the repository value is vault_link (tabletypeid = 15). 4 friendly name optional business-friendly name for the table. 5 description optional description stored with the table. 6 columns grid the editor keeps the structural column fields read-only for this type. 7 definition tab enabled, because this type is not marked as a view. related topics datavault hub datavault satellite historizised table import table"}
,{"id":386676751602,"name":"DataVault Satellite","type":"topic","path":"/docs/reference/entity-types/table-types/entity-types-table-types-datavault-satellite","breadcrumb":"Reference › Entity types › Table types › DataVault Satellite","description":"","searchText":"reference entity types table types datavault satellite overview datavault satellite is a table type used for satellite tables in the analyticscreator repository model. function the repository seeds tabletypeid = 14 as vault_sat with the description data vault satellite table with history. access this type is shown in the detailobjects page in the table type field. for this type the editor keeps the table name and column definitions read-only. how to access navigation tree tables -> open a table toolbar not confirmed. diagram not confirmed. visual element detailobjects -> table type screen overview the datavault satellite table type is represented in the table editor by the table type selector and the surrounding table metadata fields. id property description 1 table name name of the table shown in the table editor. 2 table schema schema that owns the table. 3 table type shows the current table classification. for this type the repository value is vault_sat (tabletypeid = 14). 4 friendly name optional business-friendly name for the table. 5 description optional description stored with the table. 6 columns grid the editor keeps the structural column fields read-only for this type. 7 definition tab enabled, because this type is not marked as a view. related topics datavault hub datavault link historizised table import table"}
,{"id":383509396689,"name":"Transformation types","type":"subsection","path":"/docs/reference/entity-types/transformation-types","breadcrumb":"Reference › Entity types › Transformation types","description":"","searchText":"reference entity types transformation types transformation types define how logic is implemented and executed in analyticscreator. they determine whether a transformation is generated automatically, maintained manually, executed externally, or used for a specific modeling purpose such as data marts or unions. use this section to understand the available transformation types and choose the appropriate one for your modeling and execution scenario. available transformation types datamart transformation used to expose data in a form intended for analytical consumption in the data mart layer. consumption-oriented structure typical basis for facts and dimensions used in reporting-facing models open reference regular transformation standard generated transformation type used for typical sql-based transformation logic. common default transformation type usually generated as sql view logic suitable for most modeling scenarios open reference direct-connector transformation used when transformation logic is tied directly to a connector-based source or source-side access pattern. connector-oriented processing useful for direct source integration scenarios bridges source access and transformation logic open reference external transformation used when transformation logic is implemented outside the standard generated sql transformation flow. external execution logic useful for integration with external processing suitable when logic is not managed as standard generated sql open reference script transformation used when transformation logic is implemented through script-based execution instead of standard generated sql view logic. script-driven transformation behavior useful for non-standard processing steps supports custom execution logic open reference manual transformation used when transformation logic is written manually instead of being generated automatically from metadata. manual sql definition maximum flexibility useful for special-case logic open reference union transformation used to combine multiple compatible inputs into a single transformation result. combines multiple sources or transformations useful for consolidation scenarios supports structurally aligned inputs open reference how to choose a transformation type use regular transformation for standard generated sql-based transformation logic use datamart transformation for reporting and analytical output structures use manual transformation when the logic must be written explicitly use script transformation or external transformation for non-standard execution patterns use union transformation when multiple inputs must be merged into one output use direct-connector transformation when the transformation is tightly coupled to connector-based source access key takeaway transformation types define how transformation logic is generated, maintained, and executed in analyticscreator, and should be selected based on the required level of automation, flexibility, and execution pattern."}
,{"id":386692502720,"name":"Regular transformation","type":"topic","path":"/docs/reference/entity-types/transformation-types/entity-types-transformation-types-regular-transformation","breadcrumb":"Reference › Entity types › Transformation types › Regular transformation","description":"","searchText":"reference entity types transformation types regular transformation overview regular transformation is the standard transformation type in analyticscreator. function the repository seeds transtypeid = 1 as regular with the description regular transformation. access this type is shown in the detailtransformations page in the transtype combo box. it enables the full transformation-definition surface. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> transtype screen overview the regular transformation type is selected in the transformation editor through the transtype field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype shows regular (transtypeid = 1). 4 hist type historization type paired with the transformation. 5 tables grid enabled for regular transformations. 6 references grid enabled for regular transformations. 7 columns grid enabled for regular transformations. 8 joinhisttype visible in the tables/references definition for regular transformations. 9 jointype visible in the tables/references definition for regular transformations. 10 filter editable filter text. 11 having editable having clause. related topics datamart transformation manual transformation script transformation union transformation"}
,{"id":386692502719,"name":"Manual transformation","type":"topic","path":"/docs/reference/entity-types/transformation-types/entity-types-transformation-types-manual-transformation","breadcrumb":"Reference › Entity types › Transformation types › Manual transformation","description":"","searchText":"reference entity types transformation types manual transformation overview manual transformation is the transformation type used for handmade transformation views. function the repository seeds transtypeid = 2 as manual with the description handmade transformation view. access this type is shown in the detailtransformations page in the transtype combo box. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> transtype screen overview the manual transformation type is selected in the transformation editor through the transtype field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype shows manual (transtypeid = 2). 4 view tab selected and editable for manual transformations. 5 rename grid enabled for manual transformations. 6 persist table editable persisted-result table name. 7 persist package editable persisted-result package name. related topics datamart transformation direct-connector transformation regular transformation script transformation"}
,{"id":386692502721,"name":"Script transformation","type":"topic","path":"/docs/reference/entity-types/transformation-types/entity-types-transformation-types-script-transformation","breadcrumb":"Reference › Entity types › Transformation types › Script transformation","description":"","searchText":"reference entity types transformation types script transformation overview script transformation is the transformation type used for sql or executable scripts. function the repository seeds transtypeid = 5 as script with the description sql script. access this type is shown in the detailtransformations page in the transtype combo box. the selection handler exposes the script-specific controls and the script-type selector. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> transtype screen overview the script transformation type is selected in the transformation editor through the transtype field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype shows script (transtypeid = 5). 4 script type visible only for script transformations. when script type 2 is selected and the script text is empty, the editor inserts the executable, arguments, workingdirectory, and timeout template. 5 script tab the normal view tab is relabeled to script and becomes editable. 6 result table replaces the normal persist-table label for this transformation type. 7 ssis package replaces the normal persist-package label for this transformation type. 8 create result table checkbox shown for script transformations. 9 don't detect dependencies visible only for script transformations. 10 is output table available in the transformation tables grid for this type. related topics external transformation manual transformation regular transformation union transformation"}
,{"id":386692502717,"name":"Direct-connector transformation","type":"topic","path":"/docs/reference/entity-types/transformation-types/entity-types-transformation-types-direct-connector-transformation","breadcrumb":"Reference › Entity types › Transformation types › Direct-connector transformation","description":"","searchText":"reference entity types transformation types direct-connector transformation overview direct-connector transformation is the transformation type used to attach direct sources. function the repository seeds transtypeid = 6 as direct with the description attach direct sources. access this type is shown in the detailtransformations page in the transtype combo box. the save handler requires a direct source when this type is selected. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> transtype screen overview the direct-connector transformation type is selected in the transformation editor through the transtype field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype shows direct (transtypeid = 6). 4 direct source becomes editable for this transformation type and is required before saving. 5 view tab the view tab is selected and stays editable for direct transformations. 6 filter editable sql filter text for the direct source. 7 having editable sql having clause for the direct source. 8 persist table editable persisted-result table name. 9 persist package editable persisted-result package name. related topics datamart transformation external transformation manual transformation union transformation"}
,{"id":386692502716,"name":"Datamart transformation","type":"topic","path":"/docs/reference/entity-types/transformation-types/entity-types-transformation-types-datamart-transformation","breadcrumb":"Reference › Entity types › Transformation types › Datamart transformation","description":"","searchText":"reference entity types transformation types datamart transformation overview datamart transformation is the transformation type used for datamart interface views in analyticscreator. function the repository seeds transtypeid = 3 as datamart with the description datamart interface view. access this type is shown in the detailtransformations page in the transtype combo box. the selection handler prevents creating this type directly and locks the type selector once a datamart transformation is opened. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> transtype screen overview the datamart transformation type is selected in the transformation editor through the transtype field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype shows datamart (transtypeid = 3). 4 hist type historization type paired with the transformation. 5 view tab the editor selects the view tab for datamart transformations. 6 transtype lock the type selector becomes read-only for datamart transformations, and the code raises cannot create data mart transformation directly when a direct type change is attempted. related topics direct-connector transformation external transformation manual transformation regular transformation"}
,{"id":386692502722,"name":"Union transformation","type":"topic","path":"/docs/reference/entity-types/transformation-types/entity-types-transformation-types-union-transformation","breadcrumb":"Reference › Entity types › Transformation types › Union transformation","description":"","searchText":"reference entity types transformation types union transformation overview union transformation is the transformation type used to union multiple transformation inputs. function the repository seeds transtypeid = 7 as union with the description union transformation. access this type is shown in the detailtransformations page in the transtype combo box. the selection handler switches the editor to sequence-based union behavior. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> transtype screen overview the union transformation type is selected in the transformation editor through the transtype field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype shows union (transtypeid = 7). 4 seqnr. sequence number used to align source tables and columns in the union. 5 tables grid enabled for union transformations. 6 columns grid enabled for union transformations and aligned by sequence number. 7 union all available in the tables grid for union transformations. 8 distinct available both as a transformation-level flag and as a table-grid flag. 9 persist table editable persisted-result table name. 10 persist package editable persisted-result package name. related topics direct-connector transformation external transformation regular transformation script transformation"}
,{"id":386692502718,"name":"External transformation","type":"topic","path":"/docs/reference/entity-types/transformation-types/entity-types-transformation-types-external-transformation","breadcrumb":"Reference › Entity types › Transformation types › External transformation","description":"","searchText":"reference entity types transformation types external transformation overview external transformation is the transformation type used for external ssis packages. function the repository seeds transtypeid = 4 as external with the description extrernal ssis package. access this type is shown in the detailtransformations page in the transtype combo box. the selection handler switches the persist labels to result table and ssis package and enables the result-table controls. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> transtype screen overview the external transformation type is selected in the transformation editor through the transtype field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype shows external (transtypeid = 4). 4 result table replaces the normal persist-table label for this transformation type. 5 ssis package replaces the normal persist-package label for this transformation type. 6 create result table checkbox shown for external transformations. 7 is output table available in the transformation tables grid for this type. 8 tables grid enabled so source/result tables can be assigned. related topics datamart transformation direct-connector transformation script transformation union transformation"}
,{"id":383509340361,"name":"Transformation historization types","type":"subsection","path":"/docs/reference/entity-types/transformation-historization-types","breadcrumb":"Reference › Entity types › Transformation historization types","description":"","searchText":"reference entity types transformation historization types transformation historization types define how a transformation handles time-dependent data and historical states. use this section to understand the available historization options for transformations and select the appropriate behavior for your modeling scenario. available historization types none use this historization type when only the current state of the transformation output is required. no historical state tracking simplest execution behavior suitable for current-state transformations open reference snapshot use this historization type when transformation output should be evaluated for specific snapshot dates. supports point-in-time views useful for historized transformation logic can be used with snapshot dimensions open reference fullhist use this historization type when the full historical state of the transformation output must remain accessible. tracks historical states across time suitable for full historization scenarios useful when change history must remain queryable open reference how to choose a historization type use none when only current-state output is needed use snapshot when data should be viewed at selected points in time use fullhist when the full historical output of the transformation must be preserved key takeaway transformation historization types control whether a transformation returns only current data, snapshot-based data, or fully historized output."}
,{"id":386676752596,"name":"FullHist","type":"topic","path":"/docs/reference/entity-types/transformation-historization-types/entity-types-transformation-historization-types-fullhist","breadcrumb":"Reference › Entity types › Transformation historization types › FullHist","description":"","searchText":"reference entity types transformation historization types fullhist overview fullhist is a transformation historization type in analyticscreator. function the repository seeds transhisttypeid = 1 as fullhist with the description fully histored transformation with own generated [unique id], [date_from] and [date_to]. access this type is selected in the detailtransformations page in the hist type combo box. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> hist type screen overview the fullhist historization type is selected in the transformation editor through the hist type field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype transformation type selected for the transformation. 4 hist type shows fullhist (transhisttypeid = 1). 5 snapshot grid disabled for this historization type. 6 result historization the result gets its own generated unique id, date_from, and date_to. related topics actualonly none snapshot snapshothist"}
,{"id":386676752598,"name":"Snapshot","type":"topic","path":"/docs/reference/entity-types/transformation-historization-types/entity-types-transformation-historization-types-snapshot","breadcrumb":"Reference › Entity types › Transformation historization types › Snapshot","description":"","searchText":"reference entity types transformation historization types snapshot overview snapshot is a transformation historization type in analyticscreator. function the repository seeds transhisttypeid = 3 as snapshot with the description just for predefined snapshot dates, without own pk, [date_from] and [date_to]. access this type is selected in the detailtransformations page in the hist type combo box. the selection handler enables the snapshot grid for this historization type. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> hist type screen overview the snapshot historization type is selected in the transformation editor through the hist type field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype transformation type selected for the transformation. 4 hist type shows snapshot (transhisttypeid = 3). 5 snapshot grid enabled for this historization type so predefined snapshot groups and snapshots can be assigned. 6 result historization uses predefined snapshot dates without generating its own pk, date_from, or date_to. related topics actualonly fullhist none snapshothist"}
,{"id":386676752599,"name":"SnapshotHist","type":"topic","path":"/docs/reference/entity-types/transformation-historization-types/entity-types-transformation-historization-types-snapshothist","breadcrumb":"Reference › Entity types › Transformation historization types › SnapshotHist","description":"","searchText":"reference entity types transformation historization types snapshothist overview snapshothist is a transformation historization type in analyticscreator. function the repository seeds transhisttypeid = 2 as snapshothist with the description just for predefined snapshot dates: histored transformation with own generated pk, [date_from] and [date_to]. access this type is selected in the detailtransformations page in the hist type combo box. the selection handler enables the snapshot grid for this historization type. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> hist type screen overview the snapshothist historization type is selected in the transformation editor through the hist type field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype transformation type selected for the transformation. 4 hist type shows snapshothist (transhisttypeid = 2). 5 snapshot grid enabled for this historization type so predefined snapshot groups and snapshots can be assigned. 6 result historization uses predefined snapshot dates and generates its own pk, date_from, and date_to. related topics actualonly fullhist none snapshot"}
,{"id":386676752595,"name":"ActualOnly","type":"topic","path":"/docs/reference/entity-types/transformation-historization-types/entity-types-transformation-historization-types-actualonly","breadcrumb":"Reference › Entity types › Transformation historization types › ActualOnly","description":"","searchText":"reference entity types transformation historization types actualonly overview actualonly is a transformation historization type in analyticscreator. function the repository seeds transhisttypeid = 4 as actualonly with the description for actual date, without own generated pk, [date_from] and [date_to]. access this type is selected in the detailtransformations page in the hist type combo box. the historization type also controls whether the snapshot grid is enabled. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> hist type screen overview the actualonly historization type is selected in the transformation editor through the hist type field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype transformation type selected for the transformation. 4 hist type shows actualonly (transhisttypeid = 4). 5 snapshot grid disabled for this historization type. the code only enables snapshots for types 2 and 3. 6 result historization this type does not generate its own pk, date_from, or date_to. related topics fullhist none snapshot snapshothist"}
,{"id":386676752597,"name":"None","type":"topic","path":"/docs/reference/entity-types/transformation-historization-types/entity-types-transformation-historization-types-none","breadcrumb":"Reference › Entity types › Transformation historization types › None","description":"","searchText":"reference entity types transformation historization types none overview none is a transformation historization type in analyticscreator. function the repository seeds transhisttypeid = 5 as none with the description no history information. access this type is selected in the detailtransformations page in the hist type combo box. how to access navigation tree transformations -> open a transformation toolbar not confirmed. diagram not confirmed. visual element detailtransformations -> hist type screen overview the none historization type is selected in the transformation editor through the hist type field. id property description 1 name name of the transformation. 2 schema schema that owns the transformation. 3 transtype transformation type selected for the transformation. 4 hist type shows none (transhisttypeid = 5). 5 snapshot grid disabled for this historization type. 6 result historization no transformation-owned history information is added. related topics actualonly fullhist snapshot snapshothist"}
,{"id":383509340362,"name":"Join historization types","type":"subsection","path":"/docs/reference/entity-types/join-historization-types","breadcrumb":"Reference › Entity types › Join historization types","description":"","searchText":"reference entity types join historization types join historization types define how joins behave when historized data is involved. use this section to understand how analyticscreator resolves joins between historized structures and which time-dependent behavior is applied in each case. available join historization types none use this join historization type when no historization-aware join behavior is required. no historical validity handling suitable for non-historized joins uses standard join logic open reference actual use this join historization type when only the current valid state of the joined data should be considered. current-state join behavior ignores historical versions suitable for active-record scenarios open reference full use this join historization type when the join should consider the full historical range of the participating tables. full historical join behavior includes historical validity logic suitable for complete history analysis open reference historical from use this join historization type when the join should be aligned using the historical start of validity. based on valid-from logic useful for time-entry alignment supports start-point-based historized joins open reference historical to use this join historization type when the join should be aligned using the historical end of validity. based on valid-to logic useful for time-exit alignment supports end-point-based historized joins open reference how to choose a join historization type use none when no historization-aware join handling is required use actual when only the current valid state should be joined use full when full historical validity should be respected use historical from when joins should align on the start of validity use historical to when joins should align on the end of validity key takeaway join historization types define how analyticscreator applies time-dependent validity logic when joining historized data structures."}
,{"id":386676751592,"name":"None","type":"topic","path":"/docs/reference/entity-types/join-historization-types/entity-types-join-historization-types-none","breadcrumb":"Reference › Entity types › Join historization types › None","description":"","searchText":"reference entity types join historization types none overview none is a join historization type used in the transformation editor for joined tables. function none uses the usual join only, regardless of data historying. access this join historization type is available in the transformation detail page for the joinhisttype field of joined tables. how to access navigation tree transformations -> open a transformation -> definition tab toolbar not confirmed. diagram not applicable. visual element transformation tables grid -> joinhisttype screen overview the none join historization type is selected in the detailtransformations page, in the transformation tables grid under the joinhisttype column. id property description 1 definition tab the join historization type is configured in the transformation definition area. 2 transformation tables grid lists the source and joined tables that participate in the transformation. 3 joinhisttype dropdown column used to select the join historization type for each joined table. 4 none represents a non-historying table and uses the usual join only, regardless of data historying. 5 default assignment when a transformation table row is created for transformation historization type 5, and in the default creation branch, the code sets joinhisttypeid to 1, which is none. related topics actual full historical_from historical_to"}
,{"id":386676751588,"name":"Actual","type":"topic","path":"/docs/reference/entity-types/join-historization-types/entity-types-join-historization-types-actual","breadcrumb":"Reference › Entity types › Join historization types › Actual","description":"","searchText":"reference entity types join historization types actual overview actual is a join historization type used in the transformation editor for joined tables. function actual joins the currently actual data row from the joined table. access this join historization type is available in the transformation detail page for the joinhisttype field of joined tables. how to access navigation tree transformations -> open a transformation -> definition tab toolbar not confirmed. diagram not applicable. visual element transformation tables grid -> joinhisttype screen overview the actual join historization type is selected in the detailtransformations page, in the transformation tables grid under the joinhisttype column. id property description 1 definition tab the join historization type is configured in the transformation definition area. 2 transformation tables grid lists the source and joined tables that participate in the transformation. 3 joinhisttype dropdown column used to select the join historization type for each joined table. 4 actual selects the most actual data row from the joined table. 5 default assignment when a transformation table row is created for transformation historization types 1, 2, or 4, the code defaults joinhisttypeid to 2, which is actual. related topics full historical_from historical_to none"}
,{"id":386676751589,"name":"Full","type":"topic","path":"/docs/reference/entity-types/join-historization-types/entity-types-join-historization-types-full","breadcrumb":"Reference › Entity types › Join historization types › Full","description":"","searchText":"reference entity types join historization types full overview full is a join historization type used in the transformation editor for joined tables. function full reproduces the complete history from the joined table, including its generated history columns. access this join historization type is available in the transformation detail page for the joinhisttype field of joined tables. how to access navigation tree transformations -> open a transformation -> definition tab toolbar not confirmed. diagram not applicable. visual element transformation tables grid -> joinhisttype screen overview the full join historization type is selected in the detailtransformations page, in the transformation tables grid under the joinhisttype column. id property description 1 definition tab the join historization type is configured in the transformation definition area. 2 transformation tables grid lists the source and joined tables that participate in the transformation. 3 joinhisttype dropdown column used to select the join historization type for each joined table. 4 full reproduces the complete history from the joined table, including the generated history columns such as unique id, valid-from, and valid-to. 5 default assignment when a transformation table row is created for transformation historization type 3, the code defaults joinhisttypeid to 4, which is full. related topics actual historical_from historical_to none"}
,{"id":386676751590,"name":"Historical_from","type":"topic","path":"/docs/reference/entity-types/join-historization-types/entity-types-join-historization-types-historical-from","breadcrumb":"Reference › Entity types › Join historization types › Historical_from","description":"","searchText":"reference entity types join historization types historical_from overview historical_from is a join historization type used in the transformation editor for joined tables. function historical_from joins the row from the joined table that was actual at the main table's date_from. access this join historization type is available in the transformation detail page for the joinhisttype field of joined tables. how to access navigation tree transformations -> open a transformation -> definition tab toolbar not confirmed. diagram not applicable. visual element transformation tables grid -> joinhisttype screen overview the historical_from join historization type is selected in the detailtransformations page, in the transformation tables grid under the joinhisttype column. id property description 1 definition tab the join historization type is configured in the transformation definition area. 2 transformation tables grid lists the source and joined tables that participate in the transformation. 3 joinhisttype dropdown column used to select the join historization type for each joined table. 4 historical_from selects the row from the joined table that was actual at the main table's date_from. 5 runtime join condition the engine compares the main table date_from against the joined table valid-from and valid-to columns when joinhisttypeid = 3. 6 default assignment this value is not assigned automatically in the transformation-table creation switch; it must be selected explicitly when needed. related topics actual full historical_to none"}
,{"id":386676751591,"name":"Historical_to","type":"topic","path":"/docs/reference/entity-types/join-historization-types/entity-types-join-historization-types-historical-to","breadcrumb":"Reference › Entity types › Join historization types › Historical_to","description":"","searchText":"reference entity types join historization types historical_to overview historical_to is a join historization type used in the transformation editor for joined tables. function historical_to joins the row from the joined table that was actual at the main table's date_to. access this join historization type is available in the transformation detail page for the joinhisttype field of joined tables. how to access navigation tree transformations -> open a transformation -> definition tab toolbar not confirmed. diagram not applicable. visual element transformation tables grid -> joinhisttype screen overview the historical_to join historization type is selected in the detailtransformations page, in the transformation tables grid under the joinhisttype column. id property description 1 definition tab the join historization type is configured in the transformation definition area. 2 transformation tables grid lists the source and joined tables that participate in the transformation. 3 joinhisttype dropdown column used to select the join historization type for each joined table. 4 historical_to selects the row from the joined table that was actual at the main table's date_to. 5 runtime join condition at runtime, joinhisttypeid = 5 compares the main table's date_to against the joined table history interval. 6 default assignment this type is not auto-assigned in the row-creation switch. for transformation historization type 5 and the default branch, the code sets joinhisttypeid to 1, so historical_to must be selected explicitly. related topics actual full historical_from none"}
,{"id":383509340363,"name":"Package types","type":"subsection","path":"/docs/reference/entity-types/package-types","breadcrumb":"Reference › Entity types › Package types","description":"","searchText":"reference entity types package types package types define how execution units are structured in analyticscreator and what role they play in data loading, historization, persisting, workflow orchestration, scripting, exports, and external processing. use this section to understand the available package types and choose the appropriate one for the execution pattern you want to implement. available package types import used to load data from source systems into the staging layer. supports source ingestion typical entry point for execution used in generated loading workflows open reference historization used to execute historization logic and manage validity-based data changes over time. supports change tracking typical for persistent staging used with historized tables open reference persisting used to materialize transformation results physically for performance or architectural reasons. stores generated output physically useful for complex transformations supports persisted execution patterns open reference workflow used to orchestrate execution order and dependencies across multiple processing steps. coordinates execution flow handles dependencies between packages typical orchestration entry point open reference script used when execution logic is implemented as a script instead of a standard generated package flow. script-based execution behavior useful for special-case processing supports custom runtime logic open reference exports used to move processed data or generated outputs to downstream targets. supports outbound data movement useful for interface and delivery scenarios can target external analytical or operational systems open reference external used when execution is handled outside the standard analyticscreator-generated package flow. external execution integration useful for non-standard processing scenarios separates generated logic from external runtime behavior open reference how to choose a package type use import for source-to-staging data loading use historization for change tracking and validity-based updates use persisting when transformation results should be materialized physically use workflow to orchestrate package dependencies and execution order use script for script-based processing logic use exports for outbound delivery to downstream targets use external when execution is managed outside the standard generated package flow key takeaway package types define how execution is structured in analyticscreator, from loading and historization to workflow orchestration, scripting, exports, and external processing."}
,{"id":386711825597,"name":"Import","type":"topic","path":"/docs/reference/entity-types/package-types/entity-types-package-types-import","breadcrumb":"Reference › Entity types › Package types › Import","description":"","searchText":"reference entity types package types import overview import is a package type used for packages that group import table references in analyticscreator. function the imp package type identifies packages that own entries in cfg.imp_table_references and organize import definitions for source objects and target tables. access this package type is shown in the package detail page as the read-only package type field, and import packages are listed in the navigation tree under the packages branch. how to access navigation tree packages -> import -> open a package toolbar not confirmed. diagram not applicable. visual element detailpackages -> package type screen overview the import package type is shown in the detailpackages page. for this type, the content grid lists import references, add content opens the import assistant, and double-clicking a content row opens the import editor. id property description 1 package name name of the package shown in the package detail page. 2 package type read-only field in detailpackages that displays the package type description, which is import package for this type. 3 manually created checkbox indicating whether the package was created manually. 4 external launched checkbox labeled external launched. in code it binds to donotrun; when it is not selected, the manual-dependencies grid can be shown for this package. 5 description optional package description shown in the package detail page. 6 content grid listing import references as source -> table values for the package. 7 add content opens the import assistant to create a new imp_table_reference for this package. 8 import detail double-clicking a content row opens detailimp.xaml to edit the selected import. 9 manual dependencies dependency grid shown for non-workflow packages so related package dependencies can be refreshed and reviewed. related topics exports external historization persisting"}
,{"id":386711825596,"name":"Historization","type":"topic","path":"/docs/reference/entity-types/package-types/entity-types-package-types-historization","breadcrumb":"Reference › Entity types › Package types › Historization","description":"","searchText":"reference entity types package types historization overview historization is a package type used for packages that group historization table references in analyticscreator. function the hist package type identifies packages that own entries in cfg.hist_table_references and organize historization processing for tables. access this package type is shown in the package detail page as the read-only package type field, and historization packages are listed in the navigation tree under the packages branch. how to access navigation tree packages -> historization -> open a package toolbar not confirmed. diagram not applicable. visual element detailpackages -> package type screen overview the historization package type is shown in the detailpackages page. for this type, the content grid lists historization references, add content opens the historization assistant, and double-clicking a content row opens the historization editor. id property description 1 package name name of the package shown in the package detail page. 2 package type read-only field in detailpackages that displays the package type description, which is historizising package for this type. 3 manually created checkbox indicating whether the package was created manually. 4 external launched checkbox labeled external launched. in code it binds to donotrun; when it is not selected, the manual-dependencies grid can be shown for this package. 5 description optional package description shown in the package detail page. 6 content grid listing historization references as hist_table -> table values for the package. 7 add content opens the historization assistant to create a new hist_table_reference for this package. 8 historization detail double-clicking a content row opens detailhist.xaml to edit the selected historization. 9 manual dependencies dependency grid shown for non-workflow packages so related package dependencies can be refreshed and reviewed. related topics exports external import persisting"}
,{"id":386711825598,"name":"Persisting","type":"topic","path":"/docs/reference/entity-types/package-types/entity-types-package-types-persisting","breadcrumb":"Reference › Entity types › Package types › Persisting","description":"","searchText":"reference entity types package types persisting overview persisting is a package type used for packages that group persisting table references in analyticscreator. function the pers package type identifies packages that own entries in cfg.pers_table_references and organize persisting definitions for transformations and their persist tables. access this package type is shown in the package detail page as the read-only package type field, and persisting packages are listed in the navigation tree under the packages branch. how to access navigation tree packages -> persisting -> open a package toolbar not confirmed. diagram not applicable. visual element detailpackages -> package type screen overview the persisting package type is shown in the detailpackages page. for this type, the content grid lists persisting references, add content opens the persisting assistant, and double-clicking a content row opens the persisting editor. id property description 1 package name name of the package shown in the package detail page. 2 package type read-only field in detailpackages that displays the package type description, which is persisting package for this type. 3 manually created checkbox indicating whether the package was created manually. 4 external launched checkbox labeled external launched. in code it binds to donotrun; when it is not selected, the manual-dependencies grid can be shown for this package. 5 description optional package description shown in the package detail page. 6 content grid listing persisting references as schema.transformation -> persist_table values for the package. 7 add content opens the persisting assistant to create a new pers_table_reference for this package. 8 persisting detail double-clicking a content row opens detailpers.xaml to edit the selected persisting definition. 9 manual dependencies dependency grid shown for non-workflow packages so related package dependencies can be refreshed and reviewed. related topics exports import script workflow"}
,{"id":386711825600,"name":"Workflow","type":"topic","path":"/docs/reference/entity-types/package-types/entity-types-package-types-workflow","breadcrumb":"Reference › Entity types › Package types › Workflow","description":"","searchText":"reference entity types package types workflow overview workflow is a package type used for packages that orchestrate the execution of other packages in analyticscreator. function the flow package type identifies workflow packages that own entries in cfg.workflow_package_references and define which child packages run, whether errors interrupt execution, and how retries are handled. access this package type is shown in the package detail page as the read-only package type field, and workflow packages are listed in the navigation tree under the packages branch. how to access navigation tree packages -> workflow -> open a package toolbar not confirmed. diagram not applicable. visual element detailpackages -> package type screen overview the workflow package type is shown in the detailpackages page. for this type, the content grid lists child packages and workflow execution settings, while the dependency grid is hidden. id property description 1 package name name of the package shown in the package detail page. 2 package type read-only field in detailpackages that displays the package type description, which is workflow packge for this type. 3 manually created checkbox indicating whether the package was created manually. 4 process olap cube in package for workflow packages, the fourth checkbox label changes from external launched to process olap cube in package. 5 description optional package description shown in the package detail page. 6 content grid listing child packages included in the workflow. 7 include controls whether the child package is included in the workflow. when no references exist yet, packages are initialized as included in the main workflow list. 8 interrupt on error controls whether an error in the child package interrupts the workflow execution. 9 retry attempts number of retry attempts for the child package. existing references default to 1 when null. 10 retry interval (min) retry interval in minutes for the child package. existing references default to 0 in the page model, while repository cleanup scripts normalize nulls. related topics external import persisting script"}
,{"id":386711825599,"name":"Script","type":"topic","path":"/docs/reference/entity-types/package-types/entity-types-package-types-script","breadcrumb":"Reference › Entity types › Package types › Script","description":"","searchText":"reference entity types package types script overview script is a package type used for script-launching packages in analyticscreator. function the script package type identifies packages used to launch script-based transformations and is used where the transformation assistant filters package selections to packagetypeid = 6. access this package type is shown in the package detail page as the read-only package type field, and script packages are listed in the navigation tree under the packages branch. how to access navigation tree packages -> script -> open a package toolbar not confirmed. diagram not applicable. visual element detailpackages -> package type screen overview the script package type is shown in the detailpackages page. for package types above 4, the content grid is hidden and the page shows the manual-dependencies grid instead. id property description 1 package name name of the package shown in the package detail page. 2 package type read-only field in detailpackages that displays the package type description, which is script launching package for this type. 3 manually created checkbox indicating whether the package was created manually. 4 external launched checkbox labeled external launched. in code it binds to donotrun; when it is not selected, the manual-dependencies grid can be shown for this package. 5 description optional package description shown in the package detail page. 6 manual dependencies dependency grid shown for non-workflow packages so related package dependencies can be refreshed and reviewed. 7 script package filter in the transformation assistant, script-based transformations bind the package selector to packages where packagetypeid = 6. related topics external import persisting workflow"}
,{"id":386711825594,"name":"Exports","type":"topic","path":"/docs/reference/entity-types/package-types/entity-types-package-types-exports","breadcrumb":"Reference › Entity types › Package types › Exports","description":"","searchText":"reference entity types package types exports overview exports is a package type used for export packages in analyticscreator. function the export package type identifies packages that are used by export definitions. access this package type is shown in the package detail page as the read-only package type field, and export detail pages only list packages of this type in the package selector. how to access navigation tree packages -> open a package toolbar not confirmed. diagram not applicable. visual element detailpackages -> package type screen overview the exports package type is shown in the detailpackages page in the read-only package type field, and the detailexport page only offers packages whose packagetypeid is 7. id property description 1 package name name of the package shown in the package detail page. 2 package type read-only field in detailpackages that displays the package type description, which is export package for this type. 3 manually created checkbox indicating whether the package was created manually. 4 external launched checkbox that controls whether the package is launched externally. 5 description optional package description shown in the package detail page. 6 export package filter the detailexport page binds its package selector to packages where packagetypeid = 7, so only export packages can be chosen. related topics external historization import persisting"}
,{"id":386711825595,"name":"External","type":"topic","path":"/docs/reference/entity-types/package-types/entity-types-package-types-external","breadcrumb":"Reference › Entity types › Package types › External","description":"","searchText":"reference entity types package types external overview external is a package type used for external transformation packages in analyticscreator. function the trans package type identifies external ssis packages that are assigned to external transformations. access this package type is shown in the package detail page as the read-only package type field, and the transformation assistant filters the ssis package selector to packages whose packagetypeid is 5. how to access navigation tree packages -> open a package toolbar not confirmed. diagram not applicable. visual element detailpackages -> package type screen overview the external package type is shown in the detailpackages page in the read-only package type field, and the transformation assistant only lists packages of this type when the transformation type is external ssis. id property description 1 package name name of the package shown in the package detail page. 2 package type read-only field in detailpackages that displays the package type description, which is external transformation package for this type. 3 manually created checkbox indicating whether the package was created manually. new packages default to handmade when packagetypeid = 5. 4 external launched checkbox that controls whether the package is launched externally. 5 description optional package description shown in the package detail page. 6 manual dependencies for package types above 4, the package detail page hides the content grid and shows the manual dependencies grid instead. 7 external ssis package filter in the transformation assistant, external ssis transformations bind the ssis package selector to packages where packagetypeid = 5. related topics exports historization import persisting"}
,{"id":383509396690,"name":"SQL Script types","type":"subsection","path":"/docs/reference/entity-types/sql-script-types","breadcrumb":"Reference › Entity types › SQL Script types","description":"","searchText":"reference entity types sql script types sql script types define when custom sql scripts are executed in analyticscreator and which phase of creation, workflow execution, deployment, or repository extension they belong to. use this section to understand the available sql script types and choose the correct execution point for custom sql logic. available sql script types pre-creation used to execute sql logic before object creation takes place. runs before creation steps useful for preparation logic supports setup before generated objects are created open reference post-creation used to execute sql logic after object creation has completed. runs after creation steps useful for follow-up logic supports post-processing after generated objects exist open reference pre-workflow used to execute sql logic before a workflow or execution package starts. runs before workflow execution useful for preparation or cleanup logic supports workflow-specific setup open reference post-workflow used to execute sql logic after a workflow or execution package has finished. runs after workflow execution useful for validation or cleanup supports follow-up logic after processing open reference pre-deployment used to execute sql logic before deployment starts. runs before deployment steps useful for environment preparation supports deployment-specific setup logic open reference post-deployment used to execute sql logic after deployment has completed. runs after deployment steps useful for finalization logic supports post-deployment adjustments open reference repository extension used to extend or customize repository-related behavior with sql logic. repository-focused customization supports metadata extension scenarios useful for repository-specific enhancements open reference how to choose a sql script type use pre-creation or post-creation when the script belongs to object creation timing use pre-workflow or post-workflow when the script belongs to execution timing use pre-deployment or post-deployment when the script belongs to deployment timing use repository extension when the script is intended to extend repository behavior or metadata-related logic key takeaway sql script types define the lifecycle stage at which custom sql logic is executed in analyticscreator, from creation and workflow execution to deployment and repository extension."}
,{"id":386708347128,"name":"Pre-creation","type":"topic","path":"/docs/reference/entity-types/sql-script-types/entity-types-sql-script-types-pre-creation","breadcrumb":"Reference › Entity types › SQL Script types › Pre-creation","description":"","searchText":"reference entity types sql script types pre-creation overview pre-creation is an sql script type in analyticscreator. it is stored in intern.script_types and selected through the script type field on the sql script page. function scripts of this type run before the database is created. access this type is exposed through the scripts branch in the navigation tree. the filtered list opens searchscripts.xaml for the current scripttypeid, and the editor page is detailscript.xaml. how to access navigation tree scripts -> pre-creation scripts -> right-click -> list pre-creation scripts toolbar scripts diagram not applicable. visual element define script -> script type screen overview id property description 1 script type selects the sql script type. the page is prefiltered to the current type when it is opened from the navigation tree. 2 name defines the unique script name. 3 description stores the optional script description. 4 sequence number controls the execution order inside the same script type. 5 inactive excludes the script from execution without deleting it. 6 original shows the editable original sql script text. 7 parsed shows the macro-parsed preview generated by parse_macro. 8 script contains the sql script body. 9 cancel returns to the previous page without saving the current changes. 10 save validates the script fields and stores the sql script. related topics post-creation post-deployment post-workflow pre-deployment"}
,{"id":386708347125,"name":"Post-creation","type":"topic","path":"/docs/reference/entity-types/sql-script-types/entity-types-sql-script-types-post-creation","breadcrumb":"Reference › Entity types › SQL Script types › Post-creation","description":"","searchText":"reference entity types sql script types post-creation overview post-creation is an sql script type in analyticscreator. it is stored in intern.script_types and selected through the script type field on the sql script page. function scripts of this type run after the database is created. access this type is exposed through the scripts branch in the navigation tree. the filtered list opens searchscripts.xaml for the current scripttypeid, and the editor page is detailscript.xaml. how to access navigation tree scripts -> post-creation scripts -> right-click -> list post-creation scripts toolbar scripts diagram not applicable. visual element define script -> script type screen overview id property description 1 script type selects the sql script type. the page is prefiltered to the current type when it is opened from the navigation tree. 2 name defines the unique script name. 3 description stores the optional script description. 4 sequence number controls the execution order inside the same script type. 5 inactive excludes the script from execution without deleting it. 6 original shows the editable original sql script text. 7 parsed shows the macro-parsed preview generated by parse_macro. 8 script contains the sql script body. 9 cancel returns to the previous page without saving the current changes. 10 save validates the script fields and stores the sql script. related topics post-deployment post-workflow pre-creation pre-deployment"}
,{"id":386708348090,"name":"Pre-workflow","type":"topic","path":"/docs/reference/entity-types/sql-script-types/entity-types-sql-script-types-pre-workflow","breadcrumb":"Reference › Entity types › SQL Script types › Pre-workflow","description":"","searchText":"reference entity types sql script types pre-workflow overview pre-workflow is an sql script type in analyticscreator. it is stored in intern.script_types and selected through the script type field on the sql script page. function scripts of this type run before the workflow is started. access this type is exposed through the scripts branch in the navigation tree. the filtered list opens searchscripts.xaml for the current scripttypeid, and the editor page is detailscript.xaml. how to access navigation tree scripts -> pre-workflow scripts -> right-click -> list pre-workflow scripts toolbar scripts diagram not applicable. visual element define script -> script type screen overview id property description 1 script type selects the sql script type. the page is prefiltered to the current type when it is opened from the navigation tree. 2 name defines the unique script name. 3 description stores the optional script description. 4 sequence number controls the execution order inside the same script type. 5 inactive excludes the script from execution without deleting it. 6 original shows the editable original sql script text. 7 parsed shows the macro-parsed preview generated by parse_macro. 8 script contains the sql script body. 9 package lists workflow packages that can trigger the script. 10 run assigns or removes the script for the selected workflow package. 11 cancel returns to the previous page without saving the current changes. 12 save validates the script fields and stores the sql script. related topics post-creation post-deployment post-workflow pre-creation"}
,{"id":386708347127,"name":"Post-workflow","type":"topic","path":"/docs/reference/entity-types/sql-script-types/entity-types-sql-script-types-post-workflow","breadcrumb":"Reference › Entity types › SQL Script types › Post-workflow","description":"","searchText":"reference entity types sql script types post-workflow overview post-workflow is an sql script type in analyticscreator. it is stored in intern.script_types and selected through the script type field on the sql script page. function scripts of this type run after the workflow is finished. access this type is exposed through the scripts branch in the navigation tree. the filtered list opens searchscripts.xaml for the current scripttypeid, and the editor page is detailscript.xaml. how to access navigation tree scripts -> post-workflow scripts -> right-click -> list post-workflow scripts toolbar scripts diagram not applicable. visual element define script -> script type screen overview id property description 1 script type selects the sql script type. the page is prefiltered to the current type when it is opened from the navigation tree. 2 name defines the unique script name. 3 description stores the optional script description. 4 sequence number controls the execution order inside the same script type. 5 inactive excludes the script from execution without deleting it. 6 original shows the editable original sql script text. 7 parsed shows the macro-parsed preview generated by parse_macro. 8 script contains the sql script body. 9 package lists workflow packages that can trigger the script. 10 run assigns or removes the script for the selected workflow package. 11 cancel returns to the previous page without saving the current changes. 12 save validates the script fields and stores the sql script. related topics post-creation post-deployment pre-creation pre-deployment"}
,{"id":386708347129,"name":"Pre-deployment","type":"topic","path":"/docs/reference/entity-types/sql-script-types/entity-types-sql-script-types-pre-deployment","breadcrumb":"Reference › Entity types › SQL Script types › Pre-deployment","description":"","searchText":"reference entity types sql script types pre-deployment overview pre-deployment is an sql script type in analyticscreator. it is stored in intern.script_types and selected through the script type field on the sql script page. function scripts of this type run before the database is deployed. access this type is exposed through the scripts branch in the navigation tree. the filtered list opens searchscripts.xaml for the current scripttypeid, and the editor page is detailscript.xaml. how to access navigation tree scripts -> pre-deployment scripts -> right-click -> list pre-deployment scripts toolbar scripts diagram not applicable. visual element define script -> script type screen overview id property description 1 script type selects the sql script type. the page is prefiltered to the current type when it is opened from the navigation tree. 2 name defines the unique script name. 3 description stores the optional script description. 4 sequence number controls the execution order inside the same script type. 5 inactive excludes the script from execution without deleting it. 6 original shows the editable original sql script text. 7 parsed shows the macro-parsed preview generated by parse_macro. 8 script contains the sql script body. 9 cancel returns to the previous page without saving the current changes. 10 save validates the script fields and stores the sql script. related topics post-creation post-deployment post-workflow pre-creation"}
,{"id":386708347126,"name":"Post-deployment","type":"topic","path":"/docs/reference/entity-types/sql-script-types/entity-types-sql-script-types-post-deployment","breadcrumb":"Reference › Entity types › SQL Script types › Post-deployment","description":"","searchText":"reference entity types sql script types post-deployment overview post-deployment is an sql script type in analyticscreator. it is stored in intern.script_types and selected through the script type field on the sql script page. function scripts of this type run after the database is deployed. access this type is exposed through the scripts branch in the navigation tree. the filtered list opens searchscripts.xaml for the current scripttypeid, and the editor page is detailscript.xaml. how to access navigation tree scripts -> post-deployment scripts -> right-click -> list post-deployment scripts toolbar scripts diagram not applicable. visual element define script -> script type screen overview id property description 1 script type selects the sql script type. the page is prefiltered to the current type when it is opened from the navigation tree. 2 name defines the unique script name. 3 description stores the optional script description. 4 sequence number controls the execution order inside the same script type. 5 inactive excludes the script from execution without deleting it. 6 original shows the editable original sql script text. 7 parsed shows the macro-parsed preview generated by parse_macro. 8 script contains the sql script body. 9 cancel returns to the previous page without saving the current changes. 10 save validates the script fields and stores the sql script. related topics post-creation post-workflow pre-creation pre-deployment"}
,{"id":386708348091,"name":"Repository extension","type":"topic","path":"/docs/reference/entity-types/sql-script-types/entity-types-sql-script-types-repository-extension","breadcrumb":"Reference › Entity types › SQL Script types › Repository extension","description":"","searchText":"reference entity types sql script types repository extension overview repository extension is an sql script type in analyticscreator. it is stored in intern.script_types and selected through the script type field on the sql script page. function scripts of this type run on the repository after creation or update. the repository context menu can also run all active repository extension scripts in sequence order. access this type is exposed through the scripts branch in the navigation tree. the filtered list opens searchscripts.xaml for the current scripttypeid, and the editor page is detailscript.xaml. how to access navigation tree scripts -> repository extension scripts -> right-click -> list repository extension scripts toolbar scripts diagram not applicable. visual element define script -> script type screen overview id property description 1 script type selects the sql script type. the page is prefiltered to the current type when it is opened from the navigation tree. 2 name defines the unique script name. 3 description stores the optional script description. 4 sequence number controls the execution order inside the same script type. 5 inactive excludes the script from execution without deleting it. 6 original shows the editable original sql script text. 7 parsed shows the macro-parsed preview generated by parse_macro. 8 script contains the sql script body. 9 cancel returns to the previous page without saving the current changes. 10 save validates the script fields and stores the sql script. related topics post-creation post-deployment post-workflow pre-creation"}
,{"id":383509340364,"name":"Schema types","type":"subsection","path":"/docs/reference/entity-types/schema-types","breadcrumb":"Reference › Entity types › Schema types","description":"","searchText":"reference entity types schema types schema types define how database schemas are organized in analyticscreator and what role each schema plays in the generated data warehouse architecture. use this section to understand the available schema types and how they structure staging, historization, transformation, core, and data mart layers. available schema types staging used to store imported source data before further processing. initial landing layer holds imported source structures basis for downstream historization and transformation open reference persisted staging used to store persistent and historized source data for further processing. persistent source-related layer supports historization and reprocessing separates source loading from downstream logic open reference transformation used for generated transformation logic that shapes and combines source data. transformation-oriented layer typically contains generated views or logic objects used between source-related and business-oriented layers open reference core used to store business-oriented structures such as integrated dimensions, facts, or data vault-based core models. central business logic layer contains integrated warehouse structures feeds downstream analytical layers open reference datamart used to expose data in a form intended for analytical consumption and reporting. consumption-oriented layer typically contains facts and dimensions for reporting basis for semantic models and bi tools open reference how to choose a schema type use staging for imported source data use persisted staging when persistent and historized source data is required use transformation for intermediate transformation logic use core for integrated business-oriented warehouse structures use datamart for reporting-ready analytical structures key takeaway schema types define the structural layers of the generated data warehouse, from source-oriented staging through core integration to reporting-ready data marts."}
,{"id":386676751597,"name":"Staging","type":"topic","path":"/docs/reference/entity-types/schema-types/entity-types-schema-types-staging","breadcrumb":"Reference › Entity types › Schema types › Staging","description":"","searchText":"reference entity types schema types staging overview staging is the schema type used for schemas in the staging layer. in the seed data, the default staging schema name is imp. function schemas of this type are placed in the staging layer. their schema node exposes the import package entry in the navigation tree. access this schema type is configured in the list schemas page, where each schema row has a name, schematype, layer, and description. how to access navigation tree dwh -> staging layer -> right-click -> add schema toolbar dwh -> schemas diagram not applicable. visual element list schemas -> schematype screen overview id property description 1 search criteria filters the schema list by schema name, schema type id, or description. 2 search applies the entered filter to the schema grid. 3 delete filter clears the active filter and reloads the full schema list. 4 name shows the schema name, for example imp. 5 schematype sets the schema type to staging. 6 layer assigns the schema to the staging layer. saving is blocked when a schema row has no layer assigned. 7 description stores the free-text description for the schema row. 8 save saves the schema changes. when a schema row specifies a missing database, the page prompts to create it. 9 cancel returns to the previous page without saving. related topics core datamart persisted staging transformation"}
,{"id":386676751596,"name":"Persisted staging","type":"topic","path":"/docs/reference/entity-types/schema-types/entity-types-schema-types-persisted-staging","breadcrumb":"Reference › Entity types › Schema types › Persisted staging","description":"","searchText":"reference entity types schema types persisted staging overview persisted staging is the schema type used for schemas in the persisted staging layer. in the seed data, the default persisted staging schema name is stg. function schemas of this type are placed in the persisted staging layer. their schema node exposes the historization package entry in the navigation tree. access this schema type is configured in the list schemas page, where each schema row has a name, schematype, layer, and description. how to access navigation tree dwh -> persisted staging layer -> right-click -> add schema toolbar dwh -> schemas diagram not applicable. visual element list schemas -> schematype screen overview id property description 1 search criteria filters the schema list by schema name, schema type id, or description. 2 search applies the entered filter to the schema grid. 3 delete filter clears the active filter and reloads the full schema list. 4 name shows the schema name, for example stg. 5 schematype sets the schema type to persisted staging. 6 layer assigns the schema to the persisted staging layer. saving is blocked when a schema row has no layer assigned. 7 description stores the free-text description for the schema row. 8 save saves the schema changes. when a schema row specifies a missing database, the page prompts to create it. 9 cancel returns to the previous page without saving. related topics core datamart staging transformation"}
,{"id":386676751598,"name":"Transformation","type":"topic","path":"/docs/reference/entity-types/schema-types/entity-types-schema-types-transformation","breadcrumb":"Reference › Entity types › Schema types › Transformation","description":"","searchText":"reference entity types schema types transformation overview transformation is the schema type used for schemas in the transformation layer. in the seed data, the default transformation schema name is trn. function schemas of this type are placed in the transformation layer and are used for transformation objects managed from the schema node. access this schema type is configured in the list schemas page, where each schema row has a name, schematype, layer, and description. how to access navigation tree dwh -> transformation layer -> right-click -> add schema toolbar dwh -> schemas diagram not applicable. visual element list schemas -> schematype screen overview id property description 1 search criteria filters the schema list by schema name, schema type id, or description. 2 search applies the entered filter to the schema grid. 3 delete filter clears the active filter and reloads the full schema list. 4 name shows the schema name, for example trn. 5 schematype sets the schema type to transformation. 6 layer assigns the schema to the transformation layer. saving is blocked when a schema row has no layer assigned. 7 description stores the free-text description for the schema row. 8 save saves the schema changes. when a schema row specifies a missing database, the page prompts to create it. 9 cancel returns to the previous page without saving. related topics core datamart persisted staging staging"}
,{"id":386676751594,"name":"Core","type":"topic","path":"/docs/reference/entity-types/schema-types/entity-types-schema-types-core","breadcrumb":"Reference › Entity types › Schema types › Core","description":"","searchText":"reference entity types schema types core overview core is the schema type used for schemas in the core layer. in the seed data, the default core schema name is dwh. function schemas of this type are placed in the core layer and are used for core dwh objects managed from the schema node. access this schema type is configured in the list schemas page, where each schema row has a name, schematype, layer, and description. how to access navigation tree dwh -> core layer -> right-click -> add schema toolbar dwh -> schemas diagram not applicable. visual element list schemas -> schematype screen overview id property description 1 search criteria filters the schema list by schema name, schema type id, or description. 2 search applies the entered filter to the schema grid. 3 delete filter clears the active filter and reloads the full schema list. 4 name shows the schema name, for example dwh. 5 schematype sets the schema type to core. 6 layer assigns the schema to the core layer. saving is blocked when a schema row has no layer assigned. 7 description stores the free-text description for the schema row. 8 save saves the schema changes. when a schema row specifies a missing database, the page prompts to create it. 9 cancel returns to the previous page without saving. related topics datamart persisted staging staging transformation"}
,{"id":386676751595,"name":"Datamart","type":"topic","path":"/docs/reference/entity-types/schema-types/entity-types-schema-types-datamart","breadcrumb":"Reference › Entity types › Schema types › Datamart","description":"","searchText":"reference entity types schema types datamart overview datamart is the schema type used for schemas in the datamart layer. in the seed data, the default datamart schema name is star. function schemas of this type are placed in the datamart layer and are used for data mart objects managed from the schema node. access this schema type is configured in the list schemas page, where each schema row has a name, schematype, layer, and description. how to access navigation tree dwh -> datamart layer -> right-click -> add schema toolbar dwh -> schemas diagram not applicable. visual element list schemas -> schematype screen overview id property description 1 search criteria filters the schema list by schema name, schema type id, or description. 2 search applies the entered filter to the schema grid. 3 delete filter clears the active filter and reloads the full schema list. 4 name shows the schema name, for example star. 5 schematype sets the schema type to datamart. 6 layer assigns the schema to the datamart layer. saving is blocked when a schema row has no layer assigned. 7 description stores the free-text description for the schema row. 8 save saves the schema changes. when a schema row specifies a missing database, the page prompts to create it. 9 cancel returns to the previous page without saving. related topics core persisted staging staging transformation"}
,{"id":383461259456,"name":"Entities ","type":"section","path":"/docs/reference/entities","breadcrumb":"Reference › Entities ","description":"","searchText":"reference entities entities"}
,{"id":383509340365,"name":"Layer","type":"subsection","path":"/docs/reference/entities/entities-layer","breadcrumb":"Reference › Entities › Layer","description":"","searchText":"reference entities layer overview layer is an entity in analyticscreator. function this entity is used to represent layer objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the layer entity. related topics entities layer"}
,{"id":383509340366,"name":"Schema","type":"subsection","path":"/docs/reference/entities/entities-schema","breadcrumb":"Reference › Entities › Schema","description":"","searchText":"reference entities schema overview schema is an entity in analyticscreator. function this entity is used to represent schema objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the schema entity. related topics entities schema"}
,{"id":383509396692,"name":"Connector","type":"subsection","path":"/docs/reference/entities/entities-connector","breadcrumb":"Reference › Entities › Connector","description":"","searchText":"reference entities connector overview connector is an entity in analyticscreator. function this entity is used to represent connector objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the connector entity. related topics entities connector"}
,{"id":383509340368,"name":"Source","type":"subsection","path":"/docs/reference/entities/entities-source","breadcrumb":"Reference › Entities › Source","description":"","searchText":"reference entities source overview source is an entity in analyticscreator. function this entity is used to represent source objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the source entity. related topics entities source"}
,{"id":383509340369,"name":"Table","type":"subsection","path":"/docs/reference/entities/entities-table","breadcrumb":"Reference › Entities › Table","description":"","searchText":"reference entities table overview table is an entity in analyticscreator. function this entity is used to represent table objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the table entity. related topics entities table"}
,{"id":383509396693,"name":"Transformation","type":"subsection","path":"/docs/reference/entities/entities-transformation","breadcrumb":"Reference › Entities › Transformation","description":"","searchText":"reference entities transformation overview transformation is an entity in analyticscreator. function this entity is used to represent transformation objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the transformation entity. related topics entities transformation"}
,{"id":383509396694,"name":"Package","type":"subsection","path":"/docs/reference/entities/entities-package","breadcrumb":"Reference › Entities › Package","description":"","searchText":"reference entities package overview package is an entity in analyticscreator. function this entity is used to represent package objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the package entity. related topics entities package"}
,{"id":383509340370,"name":"Index","type":"subsection","path":"/docs/reference/entities/entities-index","breadcrumb":"Reference › Entities › Index","description":"","searchText":"reference entities index overview index is an entity in analyticscreator. function this entity is used to represent index objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the index entity. related topics entities index"}
,{"id":383509396695,"name":"Partition","type":"subsection","path":"/docs/reference/entities/entities-partition","breadcrumb":"Reference › Entities › Partition","description":"","searchText":"reference entities partition overview partition is an entity in analyticscreator. function this entity is used to represent partition objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the partition entity. related topics entities partition"}
,{"id":383509396696,"name":"Hierarchy","type":"subsection","path":"/docs/reference/entities/entities-hierarchy","breadcrumb":"Reference › Entities › Hierarchy","description":"","searchText":"reference entities hierarchy overview hierarchy is an entity in analyticscreator. function this entity is used to represent hierarchy objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the hierarchy entity. related topics entities hierarchy"}
,{"id":383509340372,"name":"Macro","type":"subsection","path":"/docs/reference/entities/entities-macro","breadcrumb":"Reference › Entities › Macro","description":"","searchText":"reference entities macro overview macro is an entity in analyticscreator. function this entity is used to represent macro objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the macro entity. related topics entities macro"}
,{"id":383509340373,"name":"SQL Script","type":"subsection","path":"/docs/reference/entities/entities-sql-script","breadcrumb":"Reference › Entities › SQL Script","description":"","searchText":"reference entities sql script overview sql script is an entity in analyticscreator. function this entity is used to represent sql script objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the sql script entity. related topics entities sql script"}
,{"id":383509340375,"name":"Object script","type":"subsection","path":"/docs/reference/entities/entities-object-script","breadcrumb":"Reference › Entities › Object script","description":"","searchText":"reference entities object script overview object script is an entity in analyticscreator. function this entity is used to represent object script objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the object script entity. related topics entities object script"}
,{"id":383509396699,"name":"Deployment","type":"subsection","path":"/docs/reference/entities/entities-deployment","breadcrumb":"Reference › Entities › Deployment","description":"","searchText":"reference entities deployment overview deployment is an entity in analyticscreator. function this entity is used to represent deployment objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the deployment entity. related topics entities deployment"}
,{"id":388515715288,"name":"Table Compression Type","type":"topic","path":"/docs/reference/entities/entities-deployment/parameters-deployment-table-compression-type","breadcrumb":"Reference › Entities › Deployment › Table Compression Type","description":"","searchText":"reference entities deployment table compression type overview technical parameter name: table_compression_type default table compression type: 1-none, 2-page, 3-row, 4-columnstore index function table compression type is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":389871310016,"name":"Index Compression Type","type":"topic","path":"/docs/reference/entities/entities-deployment/parameters-deployment-index-compression-type","breadcrumb":"Reference › Entities › Deployment › Index Compression Type","description":"","searchText":"reference entities deployment index compression type overview technical parameter name: index_compression_type default index compression type in case table compression type is none or columnstore index (otherwise indexes will have the same compression type like tables: 1-none, 2-page, 3-row function index compression type is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":389871310017,"name":"Deployment Do Not Drop Object Types","type":"topic","path":"/docs/reference/entities/entities-deployment/parameters-deployment-deployment-do-not-drop-object-types","breadcrumb":"Reference › Entities › Deployment › Deployment Do Not Drop Object Types","description":"","searchText":"reference entities deployment deployment do not drop object types overview technical parameter name: deployment_do_not_drop_object_types comma-separated list of object types (see description of sqlpackage.exe) function deployment do not drop object types is a parameter in analyticscreator. default value aggregates,applicationroles,assemblies,asymmetrickeys,brokerpriorities,certificates,contracts,databaseroles,databasetriggers,fulltextcatalogs,fulltextstoplists,messagetypes,partitionfunctions,partitionschemes,permissions,queues,remoteservicebindings,rolemembership,rules,searchpropertylists,sequences,services,signatures,symmetrickeys,synonyms,userdefineddatatypes,userdefinedtabletypes,clruserdefinedtypes,users,xmlschemacollections,audits,credentials,cryptographicproviders,databaseauditspecifications,endpoints,errormessages,eventnotifications,eventsessions,linkedserverlogins,linkedservers,logins,routes,serverauditspecifications,serverrolemembership,serverroles,servertriggers custom value not set. parameter groups deployment database options storage"}
,{"id":388515715281,"name":"Deployment Create Subdirectory","type":"topic","path":"/docs/reference/entities/entities-deployment/parameters-deployment-deployment-create-subdirectory","breadcrumb":"Reference › Entities › Deployment › Deployment Create Subdirectory","description":"","searchText":"reference entities deployment deployment create subdirectory overview technical parameter name: deployment_create_subdirectory create subdirectory for every createted deployment package. 0-no (all files in output directory will be deleted), 1-yes. default - 1 function deployment create subdirectory is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":389871310018,"name":"DACPAC Model Storage Type","type":"topic","path":"/docs/reference/entities/entities-deployment/parameters-deployment-dacpac-model-storage-type","breadcrumb":"Reference › Entities › Deployment › DACPAC Model Storage Type","description":"","searchText":"reference entities deployment dacpac model storage type overview technical parameter name: dacpac_model_storage_type dacpac model storage type: 0-file, 1-memory function dacpac model storage type is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":388515715283,"name":"DWH Metadata In Extended Properties","type":"topic","path":"/docs/reference/entities/entities-deployment/parameters-deployment-dwh-metadata-in-extended-properties","breadcrumb":"Reference › Entities › Deployment › DWH Metadata In Extended Properties","description":"","searchText":"reference entities deployment dwh metadata in extended properties overview technical parameter name: dwh_metadata_in_extended_properties store metadata as extended properties of database objects function dwh metadata in extended properties is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":383509396700,"name":"Object group","type":"subsection","path":"/docs/reference/entities/entities-object-group","breadcrumb":"Reference › Entities › Object group","description":"","searchText":"reference entities object group overview object group is an entity in analyticscreator. function this entity is used to represent object group objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the object group entity. related topics entities object group"}
,{"id":383509396701,"name":"Filter","type":"subsection","path":"/docs/reference/entities/entities-filter","breadcrumb":"Reference › Entities › Filter","description":"","searchText":"reference entities filter overview filter is an entity in analyticscreator. function this entity is used to represent filter objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the filter entity. related topics entities filter"}
,{"id":383509396702,"name":"Model","type":"subsection","path":"/docs/reference/entities/entities-model","breadcrumb":"Reference › Entities › Model","description":"","searchText":"reference entities model overview model is an entity in analyticscreator. function this entity is used to represent model objects in analyticscreator. access this entity belongs to the entities section in analyticscreator. how to access navigation tree not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the model entity. related topics entities model"}
,{"id":383461259457,"name":"Parameters ","type":"section","path":"/docs/reference/parameters","breadcrumb":"Reference › Parameters ","description":"","searchText":"reference parameters parameters"}
,{"id":389870784705,"name":"Data Vault","type":"subsection","path":"/docs/reference/parameters/parameters-data-vault","breadcrumb":"Reference › Parameters › Data Vault","description":"","searchText":"reference parameters data vault vault fk field name pattern show hub deps data vault 2 create hubs"}
,{"id":389871308993,"name":"Vault FK Field Name Pattern","type":"topic","path":"/docs/reference/parameters/parameters-data-vault/parameters-data-vault-vault-fk-field-name-pattern","breadcrumb":"Reference › Parameters › Data Vault › Vault FK Field Name Pattern","description":"","searchText":"reference parameters data vault vault fk field name pattern overview technical parameter name: vault_fk_fieldname_pattern autogenerated foreign key field name correponding to vault hub id. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid}, {tableid} and {columnname} placeholders function vault fk field name pattern is a parameter in analyticscreator. default value vault_hub_id_{tablename} custom value not set. parameter groups data vault vault & deps vault"}
,{"id":389871308994,"name":"Show Hub Deps","type":"topic","path":"/docs/reference/parameters/parameters-data-vault/parameters-data-vault-show-hub-deps","breadcrumb":"Reference › Parameters › Data Vault › Show Hub Deps","description":"","searchText":"reference parameters data vault show hub deps overview technical parameter name: show_hub_deps show vault hub dependencies function show hub deps is a parameter in analyticscreator. default value 0 custom value not set. parameter groups data vault vault & deps vault"}
,{"id":389871308995,"name":"Data Vault 2 Create Hubs","type":"topic","path":"/docs/reference/parameters/parameters-data-vault/parameters-data-vault-data-vault-2-create-hubs","breadcrumb":"Reference › Parameters › Data Vault › Data Vault 2 Create Hubs","description":"","searchText":"reference parameters data vault data vault 2 create hubs overview technical parameter name: datavault2_create_hubs datavault2 create hubs: 0 - no, 1 - yes function datavault2 create hubs is a parameter in analyticscreator. default value 1 custom value not set. parameter groups data vault vault & deps vault"}
,{"id":389870784706,"name":"SAP Connector","type":"subsection","path":"/docs/reference/parameters/parameters-sap-connector","breadcrumb":"Reference › Parameters › SAP Connector","description":"","searchText":"reference parameters sap connector sap ssis custom function name sap ac custom function name sap automatic date conversion sap substitution date value sap substitution mindate value sap substitution maxdate value sap p type additional length sap deltaq transfermode sap deltaq autosync sap max record count sap theobald version sap description language"}
,{"id":389871308996,"name":"SAP SSIS Custom Function Name","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-ssis-custom-function-name","breadcrumb":"Reference › Parameters › SAP Connector › SAP SSIS Custom Function Name","description":"","searchText":"reference parameters sap connector sap ssis custom function name overview technical parameter name: sap_ssis_custom_function_name sap custom function name for theobald connector in ssis packages. please read theobald documentation about xtractis to get the correct function name. function sap ssis custom function name is a parameter in analyticscreator. default value z_xtract_is_table_compression custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871308997,"name":"SAP AC Custom Function Name","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-ac-custom-function-name","breadcrumb":"Reference › Parameters › SAP Connector › SAP AC Custom Function Name","description":"","searchText":"reference parameters sap connector sap ac custom function name overview technical parameter name: sap_ac_custom_function_name sap custom function name for analyticscreator. the default sap function is rfc_read_table function sap ac custom function name is a parameter in analyticscreator. default value z_xtract_is_table custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871308998,"name":"SAP Automatic Date Conversion","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-automatic-date-conversion","breadcrumb":"Reference › Parameters › SAP Connector › SAP Automatic Date Conversion","description":"","searchText":"reference parameters sap connector sap automatic date conversion overview technical parameter name: sap_automatic_date_conversion sap automatic date conversion. 0 - no, 1 - yes function sap automatic date conversion is a parameter in analyticscreator. default value 0 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871308999,"name":"SAP Substitution Date Value","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-substitution-date-value","breadcrumb":"Reference › Parameters › SAP Connector › SAP Substitution Date Value","description":"","searchText":"reference parameters sap connector sap substitution date value overview technical parameter name: sap_substitution_date_value sap value for invalid date (yyymmdd) in case automatic data conversion is on. function sap substitution date value is a parameter in analyticscreator. default value 1970-01-01 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309000,"name":"SAP Substitution Mindate Value","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-substitution-mindate-value","breadcrumb":"Reference › Parameters › SAP Connector › SAP Substitution Mindate Value","description":"","searchText":"reference parameters sap connector sap substitution mindate value overview technical parameter name: sap_substitution_mindate_value sap value for 0000xxxx date (yyymmdd) in case automatic data conversion is on. function sap substitution mindate value is a parameter in analyticscreator. default value 1970-01-01 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309001,"name":"SAP Substitution Maxdate Value","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-substitution-maxdate-value","breadcrumb":"Reference › Parameters › SAP Connector › SAP Substitution Maxdate Value","description":"","searchText":"reference parameters sap connector sap substitution maxdate value overview technical parameter name: sap_substitution_maxdate_value sap value for 9999xxxx date (yyymmdd) in case automatic data conversion is on. function sap substitution maxdate value is a parameter in analyticscreator. default value 2099-12-31 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309002,"name":"SAP P Type Additional Length","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-p-type-additional-length","breadcrumb":"Reference › Parameters › SAP Connector › SAP P Type Additional Length","description":"","searchText":"reference parameters sap connector sap p type additional length overview technical parameter name: sap_p_type_additional_length sap: sometimes the length of the p type columns should be increased by this parameter. function sap p type additional length is a parameter in analyticscreator. default value 1 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309003,"name":"SAP Deltaq Transfermode","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-deltaq-transfermode","breadcrumb":"Reference › Parameters › SAP Connector › SAP Deltaq Transfermode","description":"","searchText":"reference parameters sap connector sap deltaq transfermode overview technical parameter name: sap_deltaq_transfermode i-idoc, t- trfc function sap deltaq transfermode is a parameter in analyticscreator. default value t custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309004,"name":"SAP Deltaq Autosync","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-deltaq-autosync","breadcrumb":"Reference › Parameters › SAP Connector › SAP Deltaq Autosync","description":"","searchText":"reference parameters sap connector sap deltaq autosync overview technical parameter name: sap_deltaq_autosync 0-disable, 1- enable function sap deltaq autosync is a parameter in analyticscreator. default value 1 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309005,"name":"SAP Max Record Count","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-max-record-count","breadcrumb":"Reference › Parameters › SAP Connector › SAP Max Record Count","description":"","searchText":"reference parameters sap connector sap max record count overview technical parameter name: sap_max_record_count max count of records returned by sap function sap max record count is a parameter in analyticscreator. default value 1000 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309006,"name":"SAP Theobald Version","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-theobald-version","breadcrumb":"Reference › Parameters › SAP Connector › SAP Theobald Version","description":"","searchText":"reference parameters sap connector sap theobald version overview technical parameter name: sap_theobald_version 0 - match the sql server version, or number (2008, 2012 etc) function sap theobald version is a parameter in analyticscreator. default value 0 custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389871309007,"name":"SAP Description Language","type":"topic","path":"/docs/reference/parameters/parameters-sap-connector/parameters-sap-connector-sap-description-language","breadcrumb":"Reference › Parameters › SAP Connector › SAP Description Language","description":"","searchText":"reference parameters sap connector sap description language overview technical parameter name: sap_description_language sap language to get table and field descriptions function sap description language is a parameter in analyticscreator. default value e custom value not set. parameter groups sap connector sap settings sap"}
,{"id":389870784707,"name":"Source Refresh","type":"subsection","path":"/docs/reference/parameters/parameters-source-refresh","breadcrumb":"Reference › Parameters › Source Refresh","description":"","searchText":"reference parameters source refresh source preview rows source preview timeout source refresh del missing sources source refresh refresh src desc source refresh refresh imp cols source refresh del missing imp cols source refresh refresh pk source refresh refresh imp desc source refresh existing columns source refresh references"}
,{"id":389871309008,"name":"Source Preview Rows","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-preview-rows","breadcrumb":"Reference › Parameters › Source Refresh › Source Preview Rows","description":"","searchText":"reference parameters source refresh source preview rows overview technical parameter name: source_preview_rows count of rows returning during preview function source preview rows is a parameter in analyticscreator. default value 100 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309009,"name":"Source Preview Timeout","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-preview-timeout","breadcrumb":"Reference › Parameters › Source Refresh › Source Preview Timeout","description":"","searchText":"reference parameters source refresh source preview timeout overview technical parameter name: source_preview_timeout timeout for source preview, sec function source preview timeout is a parameter in analyticscreator. default value 180 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309010,"name":"Source Refresh Del Missing Sources","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-del-missing-sources","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh Del Missing Sources","description":"","searchText":"reference parameters source refresh source refresh del missing sources overview technical parameter name: source_refresh_del_missing_sources source refresh - delete missing sources: 0 - no, 1 - yes function source refresh del missing sources is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309011,"name":"Source Refresh Refresh Src Desc","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-refresh-src-desc","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh Refresh Src Desc","description":"","searchText":"reference parameters source refresh source refresh refresh src desc overview technical parameter name: source_refresh_refresh_src_desc source refresh - refresh source descriptions: 0 - no, 1 - yes function source refresh refresh src desc is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309012,"name":"Source Refresh Refresh Imp Cols","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-refresh-imp-cols","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh Refresh Imp Cols","description":"","searchText":"reference parameters source refresh source refresh refresh imp cols overview technical parameter name: source_refresh_refresh_imp_cols source refresh - refresh import columns: 0 - no, 1 - yes function source refresh refresh imp cols is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309013,"name":"Source Refresh Del Missing Imp Cols","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-del-missing-imp-cols","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh Del Missing Imp Cols","description":"","searchText":"reference parameters source refresh source refresh del missing imp cols overview technical parameter name: source_refresh_del_missing_imp_cols source refresh - delete missing import columns: 0 - no, 1 - yes function source refresh del missing imp cols is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309014,"name":"Source Refresh Refresh PK","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-refresh-pk","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh Refresh PK","description":"","searchText":"reference parameters source refresh source refresh refresh pk overview technical parameter name: source_refresh_refresh_pk source refresh - refresh primary keys in import tables: 0 - no, 1 - yes function source refresh refresh pk is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309015,"name":"Source Refresh Refresh Imp Desc","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-refresh-imp-desc","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh Refresh Imp Desc","description":"","searchText":"reference parameters source refresh source refresh refresh imp desc overview technical parameter name: source_refresh_refresh_imp_desc source refresh - refresh import descriptions: 0 - no, 1 - yes function source refresh refresh imp desc is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309016,"name":"Source Refresh Existing Columns","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-existing-columns","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh Existing Columns","description":"","searchText":"reference parameters source refresh source refresh existing columns overview technical parameter name: source_refresh_existing_columns source refresh - refresh existing source columns: 0 - no, 1 - yes function source refresh existing columns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389871309017,"name":"Source Refresh References","type":"topic","path":"/docs/reference/parameters/parameters-source-refresh/parameters-source-refresh-source-refresh-references","breadcrumb":"Reference › Parameters › Source Refresh › Source Refresh References","description":"","searchText":"reference parameters source refresh source refresh references overview technical parameter name: source_refresh_references source refresh - refresh source references: 0 - no, 1 - yes function source refresh references is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source refresh source preview refresh"}
,{"id":389870784708,"name":"DWH Wizard","type":"subsection","path":"/docs/reference/parameters/parameters-dwh-wizard","breadcrumb":"Reference › Parameters › DWH Wizard","description":"","searchText":"reference parameters dwh wizard dwh wizard table name dwh wizard imppackagename dwh wizard histpackagename dwh wizard transname dwh wizard dimname dwh wizard factname dwh wizard tablesperpackage dwh wizard hub packagename dwh wizard sat packagename dwh wizard link packagename dwh wizard hub transname dwh wizard sat transname dwh wizard link transname dwh wizard linksat transname dwh wizard hub table name dwh wizard sat table name dwh wizard link table name dwh wizard dwhtype dwh wizard snapshot dwh wizard calendar dwh wizard calendar transname dwh wizard calendar from dwh wizard calendar to dwh wizard fact dwh wizard fact calendar dwh wizard vaultlinksat dwh wizard predefined transformations dwh wizard sap tables dwh wizard sap deltaq dwh wizard sap odp"}
,{"id":389871309018,"name":"DWH Wizard Table Name","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-table-name","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Table Name","description":"","searchText":"reference parameters dwh wizard dwh wizard table name overview technical parameter name: dwhwizard_tablename template for generated table names function dwhwizard table name is a parameter in analyticscreator. default value {src_name} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309019,"name":"DWH Wizard Imppackagename","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-imppackagename","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Imppackagename","description":"","searchText":"reference parameters dwh wizard dwh wizard imppackagename overview technical parameter name: dwhwizard_imppackagename template for generated import package names function dwhwizard imppackagename is a parameter in analyticscreator. default value imp_{connector_name}{nr} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309020,"name":"DWH Wizard Histpackagename","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-histpackagename","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Histpackagename","description":"","searchText":"reference parameters dwh wizard dwh wizard histpackagename overview technical parameter name: dwhwizard_histpackagename template for generated hist package names function dwhwizard histpackagename is a parameter in analyticscreator. default value hist_{connector_name}{nr} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309021,"name":"DWH Wizard Transname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-transname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Transname","description":"","searchText":"reference parameters dwh wizard dwh wizard transname overview technical parameter name: dwhwizard_transname template for generated transformations function dwhwizard transname is a parameter in analyticscreator. default value {src_name}_v custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309022,"name":"DWH Wizard Dimname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-dimname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Dimname","description":"","searchText":"reference parameters dwh wizard dwh wizard dimname overview technical parameter name: dwhwizard_dimname template for generated dimensions function dwhwizard dimname is a parameter in analyticscreator. default value dim_{src_name} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309023,"name":"DWH Wizard Factname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-factname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Factname","description":"","searchText":"reference parameters dwh wizard dwh wizard factname overview technical parameter name: dwhwizard_factname template for generated facts function dwhwizard factname is a parameter in analyticscreator. default value fact_{src_name} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309024,"name":"DWH Wizard Tablesperpackage","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-tablesperpackage","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Tablesperpackage","description":"","searchText":"reference parameters dwh wizard dwh wizard tablesperpackage overview technical parameter name: dwhwizard_tablesperpackage tables per package function dwhwizard tablesperpackage is a parameter in analyticscreator. default value 10 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309025,"name":"DWH Wizard Hub Packagename","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-hub-packagename","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Hub Packagename","description":"","searchText":"reference parameters dwh wizard dwh wizard hub packagename overview technical parameter name: dwhwizard_hub_packagename template for generated hub packages function dwhwizard hub packagename is a parameter in analyticscreator. default value hist_{connector_name}_hub{nr} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309026,"name":"DWH Wizard Sat Packagename","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-sat-packagename","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Sat Packagename","description":"","searchText":"reference parameters dwh wizard dwh wizard sat packagename overview technical parameter name: dwhwizard_sat_packagename template for generated sat packages function dwhwizard sat packagename is a parameter in analyticscreator. default value hist_{connector_name}_sat{nr} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309027,"name":"DWH Wizard Link Packagename","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-link-packagename","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Link Packagename","description":"","searchText":"reference parameters dwh wizard dwh wizard link packagename overview technical parameter name: dwhwizard_link_packagename template for generated link packages function dwhwizard link packagename is a parameter in analyticscreator. default value hist_{connector_name}_link{nr} custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309028,"name":"DWH Wizard Hub Transname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-hub-transname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Hub Transname","description":"","searchText":"reference parameters dwh wizard dwh wizard hub transname overview technical parameter name: dwhwizard_hub_transname template for generated hub transformations function dwhwizard hub transname is a parameter in analyticscreator. default value {src_name}_hub custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309029,"name":"DWH Wizard Sat Transname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-sat-transname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Sat Transname","description":"","searchText":"reference parameters dwh wizard dwh wizard sat transname overview technical parameter name: dwhwizard_sat_transname template for generated sat transformations function dwhwizard sat transname is a parameter in analyticscreator. default value {src_name}_sat custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309030,"name":"DWH Wizard Link Transname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-link-transname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Link Transname","description":"","searchText":"reference parameters dwh wizard dwh wizard link transname overview technical parameter name: dwhwizard_link_transname template for generated link transformations function dwhwizard link transname is a parameter in analyticscreator. default value {src_name}_link custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309031,"name":"DWH Wizard Linksat Transname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-linksat-transname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Linksat Transname","description":"","searchText":"reference parameters dwh wizard dwh wizard linksat transname overview technical parameter name: dwhwizard_linksat_transname template for generated linksat transformations function dwhwizard linksat transname is a parameter in analyticscreator. default value {link_name}sat custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309032,"name":"DWH Wizard Hub Table Name","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-hub-table-name","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Hub Table Name","description":"","searchText":"reference parameters dwh wizard dwh wizard hub table name overview technical parameter name: dwhwizard_hub_tablename template for generated hub tables function dwhwizard hub table name is a parameter in analyticscreator. default value {src_name}_hub custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309033,"name":"DWH Wizard Sat Table Name","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-sat-table-name","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Sat Table Name","description":"","searchText":"reference parameters dwh wizard dwh wizard sat table name overview technical parameter name: dwhwizard_sat_tablename template for generated sat tables function dwhwizard sat table name is a parameter in analyticscreator. default value {src_name}_sat custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309034,"name":"DWH Wizard Link Table Name","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-link-table-name","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Link Table Name","description":"","searchText":"reference parameters dwh wizard dwh wizard link table name overview technical parameter name: dwhwizard_link_tablename template for generated link tables function dwhwizard link table name is a parameter in analyticscreator. default value {src_name}_link custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309035,"name":"DWH Wizard Dwhtype","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-dwhtype","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Dwhtype","description":"","searchText":"reference parameters dwh wizard dwh wizard dwhtype overview technical parameter name: dwhwizard_dwhtype 1 - classic, 2 - datavault 1.0, 3 - datavault 2.0 function dwhwizard dwhtype is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309036,"name":"DWH Wizard Snapshot","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-snapshot","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Snapshot","description":"","searchText":"reference parameters dwh wizard dwh wizard snapshot overview technical parameter name: dwhwizard_snapshot 1 - create, 0 - do not create function dwhwizard snapshot is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309037,"name":"DWH Wizard Calendar","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-calendar","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Calendar","description":"","searchText":"reference parameters dwh wizard dwh wizard calendar overview technical parameter name: dwhwizard_calendar 1 - create, 0 - do not create function dwhwizard calendar is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309038,"name":"DWH Wizard Calendar Transname","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-calendar-transname","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Calendar Transname","description":"","searchText":"reference parameters dwh wizard dwh wizard calendar transname overview technical parameter name: dwhwizard_calendar_transname calendar dimension name function dwhwizard calendar transname is a parameter in analyticscreator. default value dim_calendar custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309039,"name":"DWH Wizard Calendar From","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-calendar-from","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Calendar From","description":"","searchText":"reference parameters dwh wizard dwh wizard calendar from overview technical parameter name: dwhwizard_calendar_from calendar start date function dwhwizard calendar from is a parameter in analyticscreator. default value 19800101 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309040,"name":"DWH Wizard Calendar To","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-calendar-to","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Calendar To","description":"","searchText":"reference parameters dwh wizard dwh wizard calendar to overview technical parameter name: dwhwizard_calendar_to calendar end date function dwhwizard calendar to is a parameter in analyticscreator. default value 20401231 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309041,"name":"DWH Wizard Fact","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-fact","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Fact","description":"","searchText":"reference parameters dwh wizard dwh wizard fact overview technical parameter name: dwhwizard_fact 1 - n:1 direct related, 2 - all direct related, 3 - n:1 direct and indirect related, 4 - all direct and indirect related function dwhwizard fact is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389871309042,"name":"DWH Wizard Fact Calendar","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-fact-calendar","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Fact Calendar","description":"","searchText":"reference parameters dwh wizard dwh wizard fact calendar overview technical parameter name: dwhwizard_fact_calendar 1 - use calendar in facts, 0 - do not use calendar in facts function dwhwizard fact calendar is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389872719057,"name":"DWH Wizard Vaultlinksat","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-vaultlinksat","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Vaultlinksat","description":"","searchText":"reference parameters dwh wizard dwh wizard vaultlinksat overview technical parameter name: dwhwizard_vaultlinksat 1 - create vault link satellite, 0 - do not create vault link satellite function dwhwizard vaultlinksat is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389872719058,"name":"DWH Wizard Predefined Transformations","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-predefined-transformations","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard Predefined Transformations","description":"","searchText":"reference parameters dwh wizard dwh wizard predefined transformations overview technical parameter name: dwhwizard_predefined_transformations 0 - none, 1 - selected, 2 - all function dwhwizard predefined transformations is a parameter in analyticscreator. default value 2 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389872719059,"name":"DWH Wizard SAP Tables","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-sap-tables","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard SAP Tables","description":"","searchText":"reference parameters dwh wizard dwh wizard sap tables overview technical parameter name: dwhwizard_sap_tables search in sap tables function dwhwizard sap tables is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389872719060,"name":"DWH Wizard SAP Deltaq","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-sap-deltaq","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard SAP Deltaq","description":"","searchText":"reference parameters dwh wizard dwh wizard sap deltaq overview technical parameter name: dwhwizard_sap_deltaq search in sap deltaq function dwhwizard sap deltaq is a parameter in analyticscreator. default value 0 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389872719061,"name":"DWH Wizard SAP ODP","type":"topic","path":"/docs/reference/parameters/parameters-dwh-wizard/parameters-dwh-wizard-dwh-wizard-sap-odp","breadcrumb":"Reference › Parameters › DWH Wizard › DWH Wizard SAP ODP","description":"","searchText":"reference parameters dwh wizard dwh wizard sap odp overview technical parameter name: dwhwizard_sap_odp search in sap odp function dwhwizard sap odp is a parameter in analyticscreator. default value 1 custom value not set. parameter groups dwh wizard wizard defaults wizard"}
,{"id":389870784709,"name":"Transformations","type":"subsection","path":"/docs/reference/parameters/parameters-transformations","breadcrumb":"Reference › Parameters › Transformations","description":"","searchText":"reference parameters transformations transformation unknown members transformation key null to zero transformation hist id pattern transformation calendar fact pattern transformations createviews default calendar macro trans default use relations trans friendly names as column names trans field alias trans column alias trans alias alias trans use no lock"}
,{"id":389872719062,"name":"Transformation Unknown Members","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-transformation-unknown-members","breadcrumb":"Reference › Parameters › Transformations › Transformation Unknown Members","description":"","searchText":"reference parameters transformations transformation unknown members overview technical parameter name: transformation_unknown_members transformation wizard defaults. create unknown members. 0 - no, 1 - yes function transformation unknown members is a parameter in analyticscreator. default value 1 custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719063,"name":"Transformation Key Null To Zero","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-transformation-key-null-to-zero","breadcrumb":"Reference › Parameters › Transformations › Transformation Key Null To Zero","description":"","searchText":"reference parameters transformations transformation key null to zero overview technical parameter name: transformation_key_null_to_zero transformation wizard defaults. - key fields null to zero. 0 - no, 1 - yes function transformation key null to zero is a parameter in analyticscreator. default value 1 custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719064,"name":"Transformation Hist ID Pattern","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-transformation-hist-id-pattern","breadcrumb":"Reference › Parameters › Transformations › Transformation Hist ID Pattern","description":"","searchText":"reference parameters transformations transformation hist id pattern overview technical parameter name: transformation_hist_id_pattern pattern of key fields in transformations. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid}, {tableid} and {columnname} placeholders function transformation hist id pattern is a parameter in analyticscreator. default value fk_{tablename} custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719065,"name":"Transformation Calendar Fact Pattern","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-transformation-calendar-fact-pattern","breadcrumb":"Reference › Parameters › Transformations › Transformation Calendar Fact Pattern","description":"","searchText":"reference parameters transformations transformation calendar fact pattern overview technical parameter name: transformation_calendar_fact_pattern pattern of calendar fields in transformations. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid}, {tableid} and {columnname} placeholders function transformation calendar fact pattern is a parameter in analyticscreator. default value fk_{tablename}_{columnname} custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719066,"name":"Transformations Createviews","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-transformations-createviews","breadcrumb":"Reference › Parameters › Transformations › Transformations Createviews","description":"","searchText":"reference parameters transformations transformations createviews overview technical parameter name: transformations_createviews create view when saving transformation: 2-yes, 1-compile only, 0-no function transformations createviews is a parameter in analyticscreator. default value 0 custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719067,"name":"Default Calendar Macro","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-default-calendar-macro","breadcrumb":"Reference › Parameters › Transformations › Default Calendar Macro","description":"","searchText":"reference parameters transformations default calendar macro overview technical parameter name: default_calendar_macro name of default calendar macro function default calendar macro is a parameter in analyticscreator. default value not set. custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719068,"name":"Trans Default Use Relations","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-trans-default-use-relations","breadcrumb":"Reference › Parameters › Transformations › Trans Default Use Relations","description":"","searchText":"reference parameters transformations trans default use relations overview technical parameter name: trans_default_use_relations 1 - use business key references rather than hash key references. 2 - use hash key references rather than business key references. 3 - use hash key references only. 4 - use business key references only function trans default use relations is a parameter in analyticscreator. default value 2 custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719069,"name":"Trans Friendly Names As Column Names","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-trans-friendly-names-as-column-names","breadcrumb":"Reference › Parameters › Transformations › Trans Friendly Names As Column Names","description":"","searchText":"reference parameters transformations trans friendly names as column names overview technical parameter name: trans_friendly_names_as_column_names use friendly names as column names in transformations: 0 - no, 1 - yes function trans friendly names as column names is a parameter in analyticscreator. default value 1 custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719070,"name":"Trans Field Alias","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-trans-field-alias","breadcrumb":"Reference › Parameters › Transformations › Trans Field Alias","description":"","searchText":"reference parameters transformations trans field alias overview technical parameter name: trans_field_alias alias to use as current field name function trans field alias is a parameter in analyticscreator. default value @this custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719071,"name":"Trans Column Alias","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-trans-column-alias","breadcrumb":"Reference › Parameters › Transformations › Trans Column Alias","description":"","searchText":"reference parameters transformations trans column alias overview technical parameter name: trans_column_alias alias to use as current field name function trans column alias is a parameter in analyticscreator. default value @thiscol custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719072,"name":"Trans Alias Alias","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-trans-alias-alias","breadcrumb":"Reference › Parameters › Transformations › Trans Alias Alias","description":"","searchText":"reference parameters transformations trans alias alias overview technical parameter name: trans_alias_alias alias to use as current field name function trans alias alias is a parameter in analyticscreator. default value @thisalias custom value not set. parameter groups transformations modeling transform"}
,{"id":389872719073,"name":"Trans Use No Lock","type":"topic","path":"/docs/reference/parameters/parameters-transformations/parameters-transformations-trans-use-no-lock","breadcrumb":"Reference › Parameters › Transformations › Trans Use No Lock","description":"","searchText":"reference parameters transformations trans use no lock overview technical parameter name: trans_use_nolock use nolock hint in regular transformations: 0 - no, 1 - yes function trans use nolock is a parameter in analyticscreator. default value 1 custom value not set. parameter groups transformations modeling transform"}
,{"id":389870784710,"name":"SSIS Packages","type":"subsection","path":"/docs/reference/parameters/parameters-ssis-packages","breadcrumb":"Reference › Parameters › SSIS Packages","description":"","searchText":"reference parameters ssis packages this section contains parameters that control the behavior of generated ssis packages in analyticscreator. use these parameters to adjust buffering, fast load behavior, validation, connection handling, and package execution settings for import, export, and historization scenarios. available parameters ssis replace decimal separator controls decimal separator replacement behavior in generated ssis packages. ssis command timeout defines the command timeout used by generated ssis operations. ssis imp default buffer max rows controls the maximum number of rows per default import buffer. ssis imp default buffer size defines the default buffer size for import processing. ssis imp fastload max insert commit size controls the commit size used during fast load import operations. ssis imp fastload keep identity controls whether identity values are preserved during fast load import. ssis imp fastload keep nulls controls whether null values are preserved during fast load import. ssis imp fastload table lock controls whether table locking is used during fast load import. ssis imp fastload check constraints controls whether constraints are checked during fast load import. ssis imp fastload rows per batch defines the rows-per-batch setting for fast load import. ssis export default buffer max rows controls the maximum number of rows per default export buffer. ssis export default buffer size defines the default buffer size for export processing. ssis export fastload max insert commit size controls the commit size used during fast load export operations. ssis export fastload keep identity controls whether identity values are preserved during fast load export. ssis export fastload keep nulls controls whether null values are preserved during fast load export. ssis export fastload table lock controls whether table locking is used during fast load export. ssis export fastload check constraints controls whether constraints are checked during fast load export. ssis export fastload rows per batch defines the rows-per-batch setting for fast load export. ssis export bulk insert controls whether bulk insert behavior is used for export scenarios. ssis hist default buffer max rows controls the maximum number of rows per default historization buffer. ssis hist default buffer size defines the default buffer size for historization processing. ssis hist fastload max insert commit size controls the commit size used during fast load historization operations. ssis hist fastload keep identity controls whether identity values are preserved during fast load historization. ssis hist fastload keep nulls controls whether null values are preserved during fast load historization. ssis hist fastload table lock controls whether table locking is used during fast load historization. ssis hist fastload check constraints controls whether constraints are checked during fast load historization. ssis hist fastload rows per batch defines the rows-per-batch setting for fast load historization. ssis delay connection validation controls whether connection validation is delayed in generated ssis packages. ssis not store connection strings in package controls whether connection strings are excluded from stored package definitions. how to use this section use imp parameters for import package behavior use export parameters for export package behavior use hist parameters for historization package behavior use the general ssis parameters for connection handling, validation, and package-wide execution behavior key takeaway these parameters control the runtime behavior of generated ssis packages for import, export, historization, buffering, validation, and connection handling."}
,{"id":389872719074,"name":"SSIS Replace Decimal Separator","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-replace-decimal-separator","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Replace Decimal Separator","description":"","searchText":"reference parameters ssis packages ssis replace decimal separator overview technical parameter name: ssis_replace_decimal_separator 0 - do not replace, 1 - replace point by comma, 2 - replace comma by point function ssis replace decimal separator is a parameter in analyticscreator. default value 1 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719075,"name":"SSIS Command Timeout","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-command-timeout","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Command Timeout","description":"","searchText":"reference parameters ssis packages ssis command timeout overview technical parameter name: ssis_command_timeout ssis commandtimeout property. will be not set if empty function ssis command timeout is a parameter in analyticscreator. default value not set. custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719076,"name":"SSIS Imp Default Buffer Max Rows","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-default-buffer-max-rows","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Default Buffer Max Rows","description":"","searchText":"reference parameters ssis packages ssis imp default buffer max rows overview technical parameter name: ssis_imp_defaultbuffermaxrows ssis parameter for import package function ssis imp defaultbuffermaxrows is a parameter in analyticscreator. default value 10000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719077,"name":"SSIS Imp Default Buffer Size","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-default-buffer-size","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Default Buffer Size","description":"","searchText":"reference parameters ssis packages ssis imp default buffer size overview technical parameter name: ssis_imp_defaultbuffersize ssis parameter for import package function ssis imp defaultbuffersize is a parameter in analyticscreator. default value 10485760 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719078,"name":"SSIS Imp Fastload Max Insert Commit Size","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-fastload-max-insert-commit-size","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Fastload Max Insert Commit Size","description":"","searchText":"reference parameters ssis packages ssis imp fastload max insert commit size overview technical parameter name: ssis_imp_fastload_maxinsertcommitsize ssis parameter for import package function ssis imp fastload maxinsertcommitsize is a parameter in analyticscreator. default value 50000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719079,"name":"SSIS Imp Fastload Keep Identity","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-fastload-keep-identity","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Fastload Keep Identity","description":"","searchText":"reference parameters ssis packages ssis imp fastload keep identity overview technical parameter name: ssis_imp_fastload_keepidentity ssis parameter for import package function ssis imp fastload keepidentity is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719080,"name":"SSIS Imp Fastload Keep Nulls","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-fastload-keep-nulls","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Fastload Keep Nulls","description":"","searchText":"reference parameters ssis packages ssis imp fastload keep nulls overview technical parameter name: ssis_imp_fastload_keepnulls ssis parameter for import package function ssis imp fastload keepnulls is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719081,"name":"SSIS Imp Fastload Table Lock","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-fastload-table-lock","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Fastload Table Lock","description":"","searchText":"reference parameters ssis packages ssis imp fastload table lock overview technical parameter name: ssis_imp_fastload_tablelock ssis parameter for import package function ssis imp fastload tablelock is a parameter in analyticscreator. default value 1 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719082,"name":"SSIS Imp Fastload Check Constraints","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-fastload-check-constraints","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Fastload Check Constraints","description":"","searchText":"reference parameters ssis packages ssis imp fastload check constraints overview technical parameter name: ssis_imp_fastload_checkconstraints ssis parameter for import package function ssis imp fastload checkconstraints is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719083,"name":"SSIS Imp Fastload Rows Per Batch","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-imp-fastload-rows-per-batch","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Imp Fastload Rows Per Batch","description":"","searchText":"reference parameters ssis packages ssis imp fastload rows per batch overview technical parameter name: ssis_imp_fastload_rowsperbatch ssis parameter for import package function ssis imp fastload rowsperbatch is a parameter in analyticscreator. default value 10000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719084,"name":"SSIS Export Default Buffer Max Rows","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-default-buffer-max-rows","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Default Buffer Max Rows","description":"","searchText":"reference parameters ssis packages ssis export default buffer max rows overview technical parameter name: ssis_export_defaultbuffermaxrows ssis parameter for export package function ssis export defaultbuffermaxrows is a parameter in analyticscreator. default value 10000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719085,"name":"SSIS Export Default Buffer Size","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-default-buffer-size","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Default Buffer Size","description":"","searchText":"reference parameters ssis packages ssis export default buffer size overview technical parameter name: ssis_export_defaultbuffersize ssis parameter for export package function ssis export defaultbuffersize is a parameter in analyticscreator. default value 10485760 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719086,"name":"SSIS Export Fastload Max Insert Commit Size","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-fastload-max-insert-commit-size","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Fastload Max Insert Commit Size","description":"","searchText":"reference parameters ssis packages ssis export fastload max insert commit size overview technical parameter name: ssis_export_fastload_maxinsertcommitsize ssis parameter for export package function ssis export fastload maxinsertcommitsize is a parameter in analyticscreator. default value 50000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719087,"name":"SSIS Export Fastload Keep Identity","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-fastload-keep-identity","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Fastload Keep Identity","description":"","searchText":"reference parameters ssis packages ssis export fastload keep identity overview technical parameter name: ssis_export_fastload_keepidentity ssis parameter for export package function ssis export fastload keepidentity is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719088,"name":"SSIS Export Fastload Keep Nulls","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-fastload-keep-nulls","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Fastload Keep Nulls","description":"","searchText":"reference parameters ssis packages ssis export fastload keep nulls overview technical parameter name: ssis_export_fastload_keepnulls ssis parameter for export package function ssis export fastload keepnulls is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719089,"name":"SSIS Export Fastload Table Lock","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-fastload-table-lock","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Fastload Table Lock","description":"","searchText":"reference parameters ssis packages ssis export fastload table lock overview technical parameter name: ssis_export_fastload_tablelock ssis parameter for export package function ssis export fastload tablelock is a parameter in analyticscreator. default value 1 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719090,"name":"SSIS Export Fastload Check Constraints","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-fastload-check-constraints","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Fastload Check Constraints","description":"","searchText":"reference parameters ssis packages ssis export fastload check constraints overview technical parameter name: ssis_export_fastload_checkconstraints ssis parameter for export package function ssis export fastload checkconstraints is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719091,"name":"SSIS Export Fastload Rows Per Batch","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-fastload-rows-per-batch","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Fastload Rows Per Batch","description":"","searchText":"reference parameters ssis packages ssis export fastload rows per batch overview technical parameter name: ssis_export_fastload_rowsperbatch ssis parameter for export package function ssis export fastload rowsperbatch is a parameter in analyticscreator. default value 10000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719092,"name":"SSIS Export Bulk Insert","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-export-bulk-insert","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Export Bulk Insert","description":"","searchText":"reference parameters ssis packages ssis export bulk insert overview technical parameter name: ssis_export_bulk_insert ssis parameter for export package function ssis export bulk insert is a parameter in analyticscreator. default value 1 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719093,"name":"SSIS Hist Default Buffer Max Rows","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-default-buffer-max-rows","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Default Buffer Max Rows","description":"","searchText":"reference parameters ssis packages ssis hist default buffer max rows overview technical parameter name: ssis_hist_defaultbuffermaxrows ssis parameter for hist package function ssis hist defaultbuffermaxrows is a parameter in analyticscreator. default value 10000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719094,"name":"SSIS Hist Default Buffer Size","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-default-buffer-size","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Default Buffer Size","description":"","searchText":"reference parameters ssis packages ssis hist default buffer size overview technical parameter name: ssis_hist_defaultbuffersize ssis parameter for hist package function ssis hist defaultbuffersize is a parameter in analyticscreator. default value 10485760 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719095,"name":"SSIS Hist Fastload Max Insert Commit Size","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-fastload-max-insert-commit-size","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Fastload Max Insert Commit Size","description":"","searchText":"reference parameters ssis packages ssis hist fastload max insert commit size overview technical parameter name: ssis_hist_fastload_maxinsertcommitsize ssis parameter for hist package function ssis hist fastload maxinsertcommitsize is a parameter in analyticscreator. default value 50000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719096,"name":"SSIS Hist Fastload Keep Identity","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-fastload-keep-identity","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Fastload Keep Identity","description":"","searchText":"reference parameters ssis packages ssis hist fastload keep identity overview technical parameter name: ssis_hist_fastload_keepidentity ssis parameter for hist package function ssis hist fastload keepidentity is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872719097,"name":"SSIS Hist Fastload Keep Nulls","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-fastload-keep-nulls","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Fastload Keep Nulls","description":"","searchText":"reference parameters ssis packages ssis hist fastload keep nulls overview technical parameter name: ssis_hist_fastload_keepnulls ssis parameter for hist package function ssis hist fastload keepnulls is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872720058,"name":"SSIS Hist Fastload Table Lock","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-fastload-table-lock","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Fastload Table Lock","description":"","searchText":"reference parameters ssis packages ssis hist fastload table lock overview technical parameter name: ssis_hist_fastload_tablelock ssis parameter for hist package function ssis hist fastload tablelock is a parameter in analyticscreator. default value 1 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872720059,"name":"SSIS Hist Fastload Check Constraints","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-fastload-check-constraints","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Fastload Check Constraints","description":"","searchText":"reference parameters ssis packages ssis hist fastload check constraints overview technical parameter name: ssis_hist_fastload_checkconstraints ssis parameter for hist package function ssis hist fastload checkconstraints is a parameter in analyticscreator. default value 1 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872720060,"name":"SSIS Hist Fastload Rows Per Batch","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-hist-fastload-rows-per-batch","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Hist Fastload Rows Per Batch","description":"","searchText":"reference parameters ssis packages ssis hist fastload rows per batch overview technical parameter name: ssis_hist_fastload_rowsperbatch ssis parameter for hist package function ssis hist fastload rowsperbatch is a parameter in analyticscreator. default value 10000 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872720061,"name":"SSIS Delay Connection Validation","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-delay-connection-validation","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Delay Connection Validation","description":"","searchText":"reference parameters ssis packages ssis delay connection validation overview technical parameter name: ssis_delay_connection_validation delay ssis connection validation. 0-no, 1-yes function ssis delay connection validation is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389872720062,"name":"SSIS Not Store Connection Strings In Package","type":"topic","path":"/docs/reference/parameters/parameters-ssis-packages/parameters-ssis-packages-ssis-not-store-connection-strings-in-package","breadcrumb":"Reference › Parameters › SSIS Packages › SSIS Not Store Connection Strings In Package","description":"","searchText":"reference parameters ssis packages ssis not store connection strings in package overview technical parameter name: ssis_not_store_connection_strings_in_package d not store connection strings in ssis package. 0-store, 1-not store function ssis not store connection strings in package is a parameter in analyticscreator. default value 0 custom value not set. parameter groups ssis packages ssis runtime ssis"}
,{"id":389870784711,"name":"CSV Import","type":"subsection","path":"/docs/reference/parameters/parameters-csv-import","breadcrumb":"Reference › Parameters › CSV Import","description":"","searchText":"reference parameters csv import csv scan rows csv empty string length csv min string length"}
,{"id":389872720063,"name":"CSV Scan Rows","type":"topic","path":"/docs/reference/parameters/parameters-csv-import/parameters-csv-import-csv-scan-rows","breadcrumb":"Reference › Parameters › CSV Import › CSV Scan Rows","description":"","searchText":"reference parameters csv import csv scan rows overview technical parameter name: csv_scan_rows count of rows scanned to get the field properties function csv scan rows is a parameter in analyticscreator. default value 500 custom value not set. parameter groups csv import csv profiling csv"}
,{"id":389872720064,"name":"CSV Empty String Length","type":"topic","path":"/docs/reference/parameters/parameters-csv-import/parameters-csv-import-csv-empty-string-length","breadcrumb":"Reference › Parameters › CSV Import › CSV Empty String Length","description":"","searchText":"reference parameters csv import csv empty string length overview technical parameter name: csv_empty_string_length length of empty string fields function csv empty string length is a parameter in analyticscreator. default value 50 custom value not set. parameter groups csv import csv profiling csv"}
,{"id":389872720065,"name":"CSV Min String Length","type":"topic","path":"/docs/reference/parameters/parameters-csv-import/parameters-csv-import-csv-min-string-length","breadcrumb":"Reference › Parameters › CSV Import › CSV Min String Length","description":"","searchText":"reference parameters csv import csv min string length overview technical parameter name: csv_min_string_length minimum length of string fields function csv min string length is a parameter in analyticscreator. default value 50 custom value not set. parameter groups csv import csv profiling csv"}
,{"id":389870784712,"name":"Synchronization","type":"subsection","path":"/docs/reference/parameters/parameters-synchronization","breadcrumb":"Reference › Parameters › Synchronization","description":"","searchText":"reference parameters synchronization sync timeout synchronize num attempts synchronization fix repo synchronization renew relations synchronization update descriptions synchronization update friendly names synchronization update anonymization synchronization update column dependencies synchronization update object groups synchronization update olap references synchronization update test cases synchronization sync synchronization refresh"}
,{"id":389872720066,"name":"Sync Timeout","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-sync-timeout","breadcrumb":"Reference › Parameters › Synchronization › Sync Timeout","description":"","searchText":"reference parameters synchronization sync timeout overview technical parameter name: sync_timeout timeout for dwh synchronization, sec function sync timeout is a parameter in analyticscreator. default value 900 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871309043,"name":"Synchronize Num Attempts","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronize-num-attempts","breadcrumb":"Reference › Parameters › Synchronization › Synchronize Num Attempts","description":"","searchText":"reference parameters synchronization synchronize num attempts overview technical parameter name: synchronize_num_attempts count of attempts to create transformation due synchronization function synchronize num attempts is a parameter in analyticscreator. default value 6 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871309044,"name":"Synchronization Fix Repo","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-fix-repo","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Fix Repo","description":"","searchText":"reference parameters synchronization synchronization fix repo overview technical parameter name: synchronization_fix_repo check and fix repository. 0-no, 1-yes function synchronization fix repo is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871309045,"name":"Synchronization Renew Relations","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-renew-relations","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Renew Relations","description":"","searchText":"reference parameters synchronization synchronization renew relations overview technical parameter name: synchronization_renew_relations recalculate relations. 0-no, 1-yes function synchronization renew relations is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871309046,"name":"Synchronization Update Descriptions","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-update-descriptions","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Update Descriptions","description":"","searchText":"reference parameters synchronization synchronization update descriptions overview technical parameter name: synchronization_update_descriptions update object descriptions. 0-no, 1-yes function synchronization update descriptions is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871309047,"name":"Synchronization Update Friendly Names","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-update-friendly-names","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Update Friendly Names","description":"","searchText":"reference parameters synchronization synchronization update friendly names overview technical parameter name: synchronization_update_friendly_names update object friendly names. 0-no, 1-yes function synchronization update friendly names is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871309048,"name":"Synchronization Update Anonymization","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-update-anonymization","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Update Anonymization","description":"","searchText":"reference parameters synchronization synchronization update anonymization overview technical parameter name: synchronization_update_anonymization update anonymization properties. 0-no, 1-yes function synchronization update anonymization is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871309049,"name":"Synchronization Update Column Dependencies","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-update-column-dependencies","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Update Column Dependencies","description":"","searchText":"reference parameters synchronization synchronization update column dependencies overview technical parameter name: synchronization_update_column_dependencies recalculate column dependencies. 0-no, 1-yes function synchronization update column dependencies is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871310010,"name":"Synchronization Update Object Groups","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-update-object-groups","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Update Object Groups","description":"","searchText":"reference parameters synchronization synchronization update object groups overview technical parameter name: synchronization_update_object_groups update object group membership. 0-no, 1-yes function synchronization update object groups is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871310011,"name":"Synchronization Update OLAP References","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-update-olap-references","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Update OLAP References","description":"","searchText":"reference parameters synchronization synchronization update olap references overview technical parameter name: synchronization_update_olap_references set empty olap references based on relations between datamart objects. 0-no, 1-yes function synchronization update olap references is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871310012,"name":"Synchronization Update Test Cases","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-update-test-cases","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Update Test Cases","description":"","searchText":"reference parameters synchronization synchronization update test cases overview technical parameter name: synchronization_update_test_cases update testcase stored procedures 0-no, 1-yes function synchronization update test cases is a parameter in analyticscreator. default value 1 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871310013,"name":"Synchronization Sync","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-sync","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Sync","description":"","searchText":"reference parameters synchronization synchronization sync overview technical parameter name: synchronization_sync synchronization: 0-full, 1-selected group function synchronization sync is a parameter in analyticscreator. default value 0 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389871310014,"name":"Synchronization Refresh","type":"topic","path":"/docs/reference/parameters/parameters-synchronization/parameters-synchronization-synchronization-refresh","breadcrumb":"Reference › Parameters › Synchronization › Synchronization Refresh","description":"","searchText":"reference parameters synchronization synchronization refresh overview technical parameter name: synchronization_refresh refresh diagram: 0-full, 1-selected group, 2-new objects, 3-none function synchronization refresh is a parameter in analyticscreator. default value 0 custom value not set. parameter groups synchronization sync & retry sync"}
,{"id":389870784713,"name":"Engine Timeout","type":"subsection","path":"/docs/reference/parameters/parameters-engine-timeout","breadcrumb":"Reference › Parameters › Engine Timeout","description":"","searchText":"reference parameters engine timeout objectscript timeout"}
,{"id":389871310015,"name":"Objectscript Timeout","type":"topic","path":"/docs/reference/parameters/parameters-engine-timeout/parameters-engine-timeout-objectscript-timeout","breadcrumb":"Reference › Parameters › Engine Timeout › Objectscript Timeout","description":"","searchText":"reference parameters engine timeout objectscript timeout overview technical parameter name: objectscript_timeout timeout for object scripts, sec function objectscript timeout is a parameter in analyticscreator. default value 180 custom value not set. parameter groups engine timeout runtime timeout"}
,{"id":389870784714,"name":"Deployment","type":"subsection","path":"/docs/reference/parameters/parameters-deployment","breadcrumb":"Reference › Parameters › Deployment","description":"","searchText":"reference parameters deployment table compression type index compression type deployment do not drop object types deployment create subdirectory dacpac model storage type dwh metadata in extended properties"}
,{"id":388515715288,"name":"Table Compression Type","type":"topic","path":"/docs/reference/parameters/parameters-deployment/parameters-deployment-table-compression-type","breadcrumb":"Reference › Parameters › Deployment › Table Compression Type","description":"","searchText":"reference parameters deployment table compression type overview technical parameter name: table_compression_type default table compression type: 1-none, 2-page, 3-row, 4-columnstore index function table compression type is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":389871310016,"name":"Index Compression Type","type":"topic","path":"/docs/reference/parameters/parameters-deployment/parameters-deployment-index-compression-type","breadcrumb":"Reference › Parameters › Deployment › Index Compression Type","description":"","searchText":"reference parameters deployment index compression type overview technical parameter name: index_compression_type default index compression type in case table compression type is none or columnstore index (otherwise indexes will have the same compression type like tables: 1-none, 2-page, 3-row function index compression type is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":389871310017,"name":"Deployment Do Not Drop Object Types","type":"topic","path":"/docs/reference/parameters/parameters-deployment/parameters-deployment-deployment-do-not-drop-object-types","breadcrumb":"Reference › Parameters › Deployment › Deployment Do Not Drop Object Types","description":"","searchText":"reference parameters deployment deployment do not drop object types overview technical parameter name: deployment_do_not_drop_object_types comma-separated list of object types (see description of sqlpackage.exe) function deployment do not drop object types is a parameter in analyticscreator. default value aggregates,applicationroles,assemblies,asymmetrickeys,brokerpriorities,certificates,contracts,databaseroles,databasetriggers,fulltextcatalogs,fulltextstoplists,messagetypes,partitionfunctions,partitionschemes,permissions,queues,remoteservicebindings,rolemembership,rules,searchpropertylists,sequences,services,signatures,symmetrickeys,synonyms,userdefineddatatypes,userdefinedtabletypes,clruserdefinedtypes,users,xmlschemacollections,audits,credentials,cryptographicproviders,databaseauditspecifications,endpoints,errormessages,eventnotifications,eventsessions,linkedserverlogins,linkedservers,logins,routes,serverauditspecifications,serverrolemembership,serverroles,servertriggers custom value not set. parameter groups deployment database options storage"}
,{"id":388515715281,"name":"Deployment Create Subdirectory","type":"topic","path":"/docs/reference/parameters/parameters-deployment/parameters-deployment-deployment-create-subdirectory","breadcrumb":"Reference › Parameters › Deployment › Deployment Create Subdirectory","description":"","searchText":"reference parameters deployment deployment create subdirectory overview technical parameter name: deployment_create_subdirectory create subdirectory for every createted deployment package. 0-no (all files in output directory will be deleted), 1-yes. default - 1 function deployment create subdirectory is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":389871310018,"name":"DACPAC Model Storage Type","type":"topic","path":"/docs/reference/parameters/parameters-deployment/parameters-deployment-dacpac-model-storage-type","breadcrumb":"Reference › Parameters › Deployment › DACPAC Model Storage Type","description":"","searchText":"reference parameters deployment dacpac model storage type overview technical parameter name: dacpac_model_storage_type dacpac model storage type: 0-file, 1-memory function dacpac model storage type is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":388515715283,"name":"DWH Metadata In Extended Properties","type":"topic","path":"/docs/reference/parameters/parameters-deployment/parameters-deployment-dwh-metadata-in-extended-properties","breadcrumb":"Reference › Parameters › Deployment › DWH Metadata In Extended Properties","description":"","searchText":"reference parameters deployment dwh metadata in extended properties overview technical parameter name: dwh_metadata_in_extended_properties store metadata as extended properties of database objects function dwh metadata in extended properties is a parameter in analyticscreator. default value 1 custom value not set. parameter groups deployment database options storage"}
,{"id":389870784715,"name":"Historization","type":"subsection","path":"/docs/reference/parameters/parameters-historization","breadcrumb":"Reference › Parameters › Historization","description":"","searchText":"reference parameters historization pers default part switch hist default type hist do not close hist default use vaultid hist valid to mode hist proc use hash join hist proc use no lock persist num attempts persist pause between attempts persist use transactions hist empty record field name"}
,{"id":388515715286,"name":"Pers Default Part Switch","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-pers-default-part-switch","breadcrumb":"Reference › Parameters › Historization › Pers Default Part Switch","description":"","searchText":"reference parameters historization pers default part switch overview technical parameter name: pers_default_partswitch 0 - none, 1 - partition switching, 2 - renaming function pers default part switch is a parameter in analyticscreator. default value 2 custom value not set. parameter groups historization persisting history"}
,{"id":389871310019,"name":"Hist Default Type","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-hist-default-type","breadcrumb":"Reference › Parameters › Historization › Hist Default Type","description":"","searchText":"reference parameters historization hist default type overview technical parameter name: hist_default_type 1- ssis package, 2 - stored procedure function hist default type is a parameter in analyticscreator. default value 2 custom value not set. parameter groups historization persisting history"}
,{"id":389871310020,"name":"Hist Do Not Close","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-hist-do-not-close","breadcrumb":"Reference › Parameters › Historization › Hist Do Not Close","description":"","searchText":"reference parameters historization hist do not close overview technical parameter name: hist_do_not_close default value of \"missing record behaviour\" parameter for new historizations. 0 - close, 1 - don't close function hist do not close is a parameter in analyticscreator. default value 0 custom value not set. parameter groups historization persisting history"}
,{"id":389871310021,"name":"Hist Default Use Vaultid","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-hist-default-use-vaultid","breadcrumb":"Reference › Parameters › Historization › Hist Default Use Vaultid","description":"","searchText":"reference parameters historization hist default use vaultid overview technical parameter name: hist_default_use_vaultid 0 - don't use vault_hub_id as primary key. 1 - use vault_hub_id as primary key function hist default use vaultid is a parameter in analyticscreator. default value 1 custom value not set. parameter groups historization persisting history"}
,{"id":389871310022,"name":"Hist Valid To Mode","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-hist-valid-to-mode","breadcrumb":"Reference › Parameters › Historization › Hist Valid To Mode","description":"","searchText":"reference parameters historization hist valid to mode overview technical parameter name: hist_valid_to_mode subtract 2 milliseconds: 0 - yes, 1 - no function hist valid to mode is a parameter in analyticscreator. default value 0 custom value not set. parameter groups historization persisting history"}
,{"id":388515715284,"name":"Hist Proc Use Hash Join","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-hist-proc-use-hash-join","breadcrumb":"Reference › Parameters › Historization › Hist Proc Use Hash Join","description":"","searchText":"reference parameters historization hist proc use hash join overview technical parameter name: hist_proc_use_hash_join use hash join hint in historizing sp to speedup sql except command. 0-no, 1-yes function hist proc use hash join is a parameter in analyticscreator. default value 1 custom value not set. parameter groups historization persisting history"}
,{"id":389871310023,"name":"Hist Proc Use No Lock","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-hist-proc-use-no-lock","breadcrumb":"Reference › Parameters › Historization › Hist Proc Use No Lock","description":"","searchText":"reference parameters historization hist proc use no lock overview technical parameter name: hist_proc_use_nolock use nolock hint in historizing stored procedures: 0 - no, 1 - yes function hist proc use nolock is a parameter in analyticscreator. default value 1 custom value not set. parameter groups historization persisting history"}
,{"id":389871310024,"name":"Persist Num Attempts","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-persist-num-attempts","breadcrumb":"Reference › Parameters › Historization › Persist Num Attempts","description":"","searchText":"reference parameters historization persist num attempts overview technical parameter name: persist_num_attempts number of attempts to persist transformation in persisting stored procedure. function persist num attempts is a parameter in analyticscreator. default value 5 custom value not set. parameter groups historization persisting history"}
,{"id":389871310025,"name":"Persist Pause Between Attempts","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-persist-pause-between-attempts","breadcrumb":"Reference › Parameters › Historization › Persist Pause Between Attempts","description":"","searchText":"reference parameters historization persist pause between attempts overview technical parameter name: persist_pause_between_attempts pause between attempts to persist transformation in persisting stored procedure. format: hh:mm:ss function persist pause between attempts is a parameter in analyticscreator. default value 00:00:10 custom value not set. parameter groups historization persisting history"}
,{"id":389871310026,"name":"Persist Use Transactions","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-persist-use-transactions","breadcrumb":"Reference › Parameters › Historization › Persist Use Transactions","description":"","searchText":"reference parameters historization persist use transactions overview technical parameter name: persist_use_transactions use transaction in persisting procedures. 0 - no, 1 - yes (default) function persist use transactions is a parameter in analyticscreator. default value 1 custom value not set. parameter groups historization persisting history"}
,{"id":389871310027,"name":"Hist Empty Record Field Name","type":"topic","path":"/docs/reference/parameters/parameters-historization/parameters-historization-hist-empty-record-field-name","breadcrumb":"Reference › Parameters › Historization › Hist Empty Record Field Name","description":"","searchText":"reference parameters historization hist empty record field name overview technical parameter name: hist_empty_record_fieldname name of the column to identify empty records in the historized tables function hist empty record field name is a parameter in analyticscreator. default value is_empty_record custom value not set. parameter groups historization persisting history"}
,{"id":389870784716,"name":"Diagrams","type":"subsection","path":"/docs/reference/parameters/parameters-diagrams","breadcrumb":"Reference › Parameters › Diagrams","description":"","searchText":"reference parameters diagrams thumbnail diagram show thumbnail diagram width thumbnail diagram height thumbnail diagram left thumbnail diagram top thumbnail diagram dock thumbnail diagram margin diagram to picture scale"}
,{"id":389871310028,"name":"Thumbnail Diagram Show","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-thumbnail-diagram-show","breadcrumb":"Reference › Parameters › Diagrams › Thumbnail Diagram Show","description":"","searchText":"reference parameters diagrams thumbnail diagram show overview technical parameter name: thumbnail_diagram_show 0 - do not show, 1 - show function thumbnail diagram show is a parameter in analyticscreator. default value 1 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389871310029,"name":"Thumbnail Diagram Width","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-thumbnail-diagram-width","breadcrumb":"Reference › Parameters › Diagrams › Thumbnail Diagram Width","description":"","searchText":"reference parameters diagrams thumbnail diagram width overview technical parameter name: thumbnail_diagram_width width (points) function thumbnail diagram width is a parameter in analyticscreator. default value 300 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389871310030,"name":"Thumbnail Diagram Height","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-thumbnail-diagram-height","breadcrumb":"Reference › Parameters › Diagrams › Thumbnail Diagram Height","description":"","searchText":"reference parameters diagrams thumbnail diagram height overview technical parameter name: thumbnail_diagram_height height (points) function thumbnail diagram height is a parameter in analyticscreator. default value 300 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389871310031,"name":"Thumbnail Diagram Left","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-thumbnail-diagram-left","breadcrumb":"Reference › Parameters › Diagrams › Thumbnail Diagram Left","description":"","searchText":"reference parameters diagrams thumbnail diagram left overview technical parameter name: thumbnail_diagram_left left (points) function thumbnail diagram left is a parameter in analyticscreator. default value 0 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389871310032,"name":"Thumbnail Diagram Top","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-thumbnail-diagram-top","breadcrumb":"Reference › Parameters › Diagrams › Thumbnail Diagram Top","description":"","searchText":"reference parameters diagrams thumbnail diagram top overview technical parameter name: thumbnail_diagram_top top (points) function thumbnail diagram top is a parameter in analyticscreator. default value 0 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389871310033,"name":"Thumbnail Diagram Dock","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-thumbnail-diagram-dock","breadcrumb":"Reference › Parameters › Diagrams › Thumbnail Diagram Dock","description":"","searchText":"reference parameters diagrams thumbnail diagram dock overview technical parameter name: thumbnail_diagram_dock 0 - no dock, 1 - left top corner, 2 - right top corner, 3 - left down corner, 4 - right down corner function thumbnail diagram dock is a parameter in analyticscreator. default value 4 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389871310034,"name":"Thumbnail Diagram Margin","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-thumbnail-diagram-margin","breadcrumb":"Reference › Parameters › Diagrams › Thumbnail Diagram Margin","description":"","searchText":"reference parameters diagrams thumbnail diagram margin overview technical parameter name: thumbnail_diagram_margin margin (points). function thumbnail diagram margin is a parameter in analyticscreator. default value 30 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389871310035,"name":"Diagram To Picture Scale","type":"topic","path":"/docs/reference/parameters/parameters-diagrams/parameters-diagrams-diagram-to-picture-scale","breadcrumb":"Reference › Parameters › Diagrams › Diagram To Picture Scale","description":"","searchText":"reference parameters diagrams diagram to picture scale overview technical parameter name: diagram_to_picture_scale scale of the diagram by saving as picture. floating number between 0.0 and 2.0 using dot as decimal separator. the more the better the picture quality and the greather the file size. when 0, the current diagram scale will be used. default: 1.0 function diagram to picture scale is a parameter in analyticscreator. default value 1.0 custom value not set. parameter groups diagrams diagram view diagram"}
,{"id":389870784717,"name":"Governance","type":"subsection","path":"/docs/reference/parameters/parameters-governance","breadcrumb":"Reference › Parameters › Governance","description":"","searchText":"reference parameters governance force anonymization inheritance force friendlynames inheritance force display folder inheritance columns anonymization types"}
,{"id":389871310036,"name":"Force Anonymization Inheritance","type":"topic","path":"/docs/reference/parameters/parameters-governance/parameters-governance-force-anonymization-inheritance","breadcrumb":"Reference › Parameters › Governance › Force Anonymization Inheritance","description":"","searchText":"reference parameters governance force anonymization inheritance overview technical parameter name: force_anonymization_inheritance force inheritance of anonymization properties: 0 - no, 1 - yes function force anonymization inheritance is a parameter in analyticscreator. default value 0 custom value not set. parameter groups governance object rules inheritance"}
,{"id":389871310037,"name":"Force Friendlynames Inheritance","type":"topic","path":"/docs/reference/parameters/parameters-governance/parameters-governance-force-friendlynames-inheritance","breadcrumb":"Reference › Parameters › Governance › Force Friendlynames Inheritance","description":"","searchText":"reference parameters governance force friendlynames inheritance overview technical parameter name: force_friendlynames_inheritance force inheritance of table and column friendly names: 0 - no, 1 - yes function force friendlynames inheritance is a parameter in analyticscreator. default value 0 custom value not set. parameter groups governance object rules inheritance"}
,{"id":389871310038,"name":"Force Display Folder Inheritance","type":"topic","path":"/docs/reference/parameters/parameters-governance/parameters-governance-force-display-folder-inheritance","breadcrumb":"Reference › Parameters › Governance › Force Display Folder Inheritance","description":"","searchText":"reference parameters governance force display folder inheritance overview technical parameter name: force_displayfolder_inheritance force inheritance of column display folders: 0 - no, 1 - yes function force displayfolder inheritance is a parameter in analyticscreator. default value 0 custom value not set. parameter groups governance object rules inheritance"}
,{"id":389871310039,"name":"Columns Anonymization Types","type":"topic","path":"/docs/reference/parameters/parameters-governance/parameters-governance-columns-anonymization-types","breadcrumb":"Reference › Parameters › Governance › Columns Anonymization Types","description":"","searchText":"reference parameters governance columns anonymization types overview technical parameter name: columns_anonymization_types comma separated list of anonymization types and names. function columns anonymization types is a parameter in analyticscreator. default value 0,no,1,yes custom value not set. parameter groups governance object rules inheritance"}
,{"id":389870784718,"name":"Naming & Metadata","type":"subsection","path":"/docs/reference/parameters/parameters-naming-and-metadata","breadcrumb":"Reference › Parameters › Naming & Metadata","description":"","searchText":"reference parameters naming & metadata diagram name pattern description pattern hist id description pattern date from description pattern date to description pattern snapshot id description pattern calendar id description pattern statement friendly name pattern hist id friendly name pattern date from friendly name pattern date to friendly name pattern snapshot id friendly name pattern calendar id friendly name pattern duplicated columns friendly name pattern duplicated tables source reference description pattern table reference description pattern source reference onecol description pattern table reference onecol description pattern description inherit tables description inherit trans description inherit trans tables description inherit table columns description inherit trans columns description inherit trans table columns description set special description use statements friendly name inherit tables friendly name inherit trans friendly name inherit trans tables friendly name inherit table columns friendly name inherit trans columns friendly name inherit trans table columns friendly name set special display folder inherit table columns display folder inherit trans columns display folder inherit trans table columns"}
,{"id":388515715282,"name":"Diagram Name Pattern","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-diagram-name-pattern","breadcrumb":"Reference › Parameters › Naming & Metadata › Diagram Name Pattern","description":"","searchText":"reference parameters naming & metadata diagram name pattern overview technical parameter name: diagram_name_pattern object name in diagram. you can use {name}, {friendly name}, {fullfriendlyname}, {fullfriendlynamecr}, {id} and {cr} placeholders function diagram name pattern is a parameter in analyticscreator. default value {fullfriendlynamecr} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310040,"name":"Description Pattern Hist ID","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-pattern-hist-id","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Pattern Hist ID","description":"","searchText":"reference parameters naming & metadata description pattern hist id overview technical parameter name: description_pattern_hist_id autogenerated description of hist_id (satz_id) field. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function description pattern hist id is a parameter in analyticscreator. default value {tablename}: surrogate key custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310041,"name":"Description Pattern Date From","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-pattern-date-from","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Pattern Date From","description":"","searchText":"reference parameters naming & metadata description pattern date from overview technical parameter name: description_pattern_datefrom autogenerated description of datefrom (dat_von_hist) field. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function description pattern date from is a parameter in analyticscreator. default value {tablename}: start of validity period custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310042,"name":"Description Pattern Date To","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-pattern-date-to","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Pattern Date To","description":"","searchText":"reference parameters naming & metadata description pattern date to overview technical parameter name: description_pattern_dateto autogenerated description of dateto (dat_bis_hist) field. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function description pattern date to is a parameter in analyticscreator. default value {tablename}: end of validity period custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310043,"name":"Description Pattern Snapshot ID","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-pattern-snapshot-id","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Pattern Snapshot ID","description":"","searchText":"reference parameters naming & metadata description pattern snapshot id overview technical parameter name: description_pattern_snapshot_id autogenerated description of hist_id (satz_id) field in snapshot dimension . you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function description pattern snapshot id is a parameter in analyticscreator. default value snapshot id custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310044,"name":"Description Pattern Calendar ID","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-pattern-calendar-id","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Pattern Calendar ID","description":"","searchText":"reference parameters naming & metadata description pattern calendar id overview technical parameter name: description_pattern_calendar_id autogenerated description of hist_id (satz_id) field in calendar dimension. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function description pattern calendar id is a parameter in analyticscreator. default value calendar id custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310045,"name":"Description Pattern Statement","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-pattern-statement","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Pattern Statement","description":"","searchText":"reference parameters naming & metadata description pattern statement overview technical parameter name: description_pattern_statement autogenerated description in case of using statement as description of transformation fields. you can use {statement}, {friendlyname}, {columnname}, {columnid} and {cr} placeholders function description pattern statement is a parameter in analyticscreator. default value {statement} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310046,"name":"Friendly Name Pattern Hist ID","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-pattern-hist-id","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Pattern Hist ID","description":"","searchText":"reference parameters naming & metadata friendly name pattern hist id overview technical parameter name: friendlyname_pattern_hist_id autogenerated friendly name of hist_id (satz_id) field. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function friendly name pattern hist id is a parameter in analyticscreator. default value {friendlyname} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310047,"name":"Friendly Name Pattern Date From","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-pattern-date-from","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Pattern Date From","description":"","searchText":"reference parameters naming & metadata friendly name pattern date from overview technical parameter name: friendlyname_pattern_datefrom autogenerated friendly name of datefrom (dat_von_hist) field. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function friendly name pattern date from is a parameter in analyticscreator. default value {friendlyname}_validfrom custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310048,"name":"Friendly Name Pattern Date To","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-pattern-date-to","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Pattern Date To","description":"","searchText":"reference parameters naming & metadata friendly name pattern date to overview technical parameter name: friendlyname_pattern_dateto autogenerated friendly name of dateto (dat_bis_hist) field. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function friendly name pattern date to is a parameter in analyticscreator. default value {friendlyname}_validto custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310049,"name":"Friendly Name Pattern Snapshot ID","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-pattern-snapshot-id","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Pattern Snapshot ID","description":"","searchText":"reference parameters naming & metadata friendly name pattern snapshot id overview technical parameter name: friendlyname_pattern_snapshot_id autogenerated friendly name of hist_id (satz_id) field in snapshot dimension . you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function friendly name pattern snapshot id is a parameter in analyticscreator. default value snapshot custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310050,"name":"Friendly Name Pattern Calendar ID","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-pattern-calendar-id","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Pattern Calendar ID","description":"","searchText":"reference parameters naming & metadata friendly name pattern calendar id overview technical parameter name: friendlyname_pattern_calendar_id autogenerated friendly name of hist_id (satz_id) field in calendar dimension. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid} and {tableid} placeholders function friendly name pattern calendar id is a parameter in analyticscreator. default value calendar custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310051,"name":"Friendly Name Pattern Duplicated Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-pattern-duplicated-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Pattern Duplicated Columns","description":"","searchText":"reference parameters naming & metadata friendly name pattern duplicated columns overview technical parameter name: friendlyname_pattern_duplicated_columns autogenerated replacement of duplicated friendly names. you can use {friendlyname}, {columnname}, {columnid} and {nr} (autoincrement number) placeholders function friendly name pattern duplicated columns is a parameter in analyticscreator. default value {friendlyname}{nr} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389871310052,"name":"Friendly Name Pattern Duplicated Tables","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-pattern-duplicated-tables","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Pattern Duplicated Tables","description":"","searchText":"reference parameters naming & metadata friendly name pattern duplicated tables overview technical parameter name: friendlyname_pattern_duplicated_tables autogenerated replacement of duplicated friendly names. you can use {schemaname}, {tablename}, {friendlyname}, {schemaid}, {tableid} and {nr} (autoincrement number) placeholders function friendly name pattern duplicated tables is a parameter in analyticscreator. default value {friendlyname}{nr} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937274,"name":"Source Reference Description Pattern","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-source-reference-description-pattern","breadcrumb":"Reference › Parameters › Naming & Metadata › Source Reference Description Pattern","description":"","searchText":"reference parameters naming & metadata source reference description pattern overview technical parameter name: source_reference_description_pattern autogenerated source reference description. you can use {sourceschema1}, {sourcename1}, {sourceid1}, {friendlyname1}, {sourceschema2}, {sourcename2}, {sourceid2} and {friendlyname2} placeholders function source reference description pattern is a parameter in analyticscreator. default value fk_{sourcename1}_{sourcename2} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937275,"name":"Table Reference Description Pattern","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-table-reference-description-pattern","breadcrumb":"Reference › Parameters › Naming & Metadata › Table Reference Description Pattern","description":"","searchText":"reference parameters naming & metadata table reference description pattern overview technical parameter name: table_reference_description_pattern autogenerated table reference description. you can use {tableschema1}, {tablename1}, {tableid1}, {friendlyname1}, {tableschema2}, {tablename2}, {tableid2} and {friendlyname2} placeholders function table reference description pattern is a parameter in analyticscreator. default value fk_{tablename1}_{tablename2} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937276,"name":"Source Reference Onecol Description Pattern","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-source-reference-onecol-description-pattern","breadcrumb":"Reference › Parameters › Naming & Metadata › Source Reference Onecol Description Pattern","description":"","searchText":"reference parameters naming & metadata source reference onecol description pattern overview technical parameter name: source_reference_onecol_description_pattern autogenerated one-column source reference description. you can use {sourceschema1}, {sourcename1}, {sourceid1}, {friendlyname1}, {sourceschema2}, {sourcename2}, {sourceid2}, {friendlyname2}, {columnname}, {columnid} and {columnfriendlyname} placeholders function source reference onecol description pattern is a parameter in analyticscreator. default value rc_{sourcename1}_{sourcename2}_{columnname} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937277,"name":"Table Reference Onecol Description Pattern","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-table-reference-onecol-description-pattern","breadcrumb":"Reference › Parameters › Naming & Metadata › Table Reference Onecol Description Pattern","description":"","searchText":"reference parameters naming & metadata table reference onecol description pattern overview technical parameter name: table_reference_onecol_description_pattern autogenerated one-column table reference description. you can use {tableschema1}, {tablename1}, {tableid1}, {friendlyname1}, {tableschema2}, {tablename2}, {tableid2}, {friendlyname2}, {columnname}, {columnid} and {columnfriendlyname} placeholders function table reference onecol description pattern is a parameter in analyticscreator. default value rc_{tablename1}_{tablename2}_{columnname} custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937278,"name":"Description Inherit Tables","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-inherit-tables","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Inherit Tables","description":"","searchText":"reference parameters naming & metadata description inherit tables overview technical parameter name: description_inherit_tables description inheritance from the tables to the dependent tables: 0 - inherit if empty, 1 - always, 2 - never function description inherit tables is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937279,"name":"Description Inherit Trans","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-inherit-trans","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Inherit Trans","description":"","searchText":"reference parameters naming & metadata description inherit trans overview technical parameter name: description_inherit_trans description inheritance from the first transformation table to the transformation: 0 - inherit if empty, 1 - always, 2 - never function description inherit trans is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937280,"name":"Description Inherit Trans Tables","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-inherit-trans-tables","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Inherit Trans Tables","description":"","searchText":"reference parameters naming & metadata description inherit trans tables overview technical parameter name: description_inherit_transtables description inheritance from the transformations to the transtables and persistend tables: 0 - inherit if empty, 1 - always, 2 - never function description inherit transtables is a parameter in analyticscreator. default value 1 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937281,"name":"Description Inherit Table Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-inherit-table-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Inherit Table Columns","description":"","searchText":"reference parameters naming & metadata description inherit table columns overview technical parameter name: description_inherit_tablecolumns description inheritance from the table columns to the dependent table columns: 0 - inherit if empty, 1 - always, 2 - never function description inherit tablecolumns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937282,"name":"Description Inherit Trans Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-inherit-trans-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Inherit Trans Columns","description":"","searchText":"reference parameters naming & metadata description inherit trans columns overview technical parameter name: description_inherit_transcolumns description inheritance from the table columns of the data source to the transformation columns: 0 - inherit if empty, 1 - always, 2 - never function description inherit transcolumns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937283,"name":"Description Inherit Trans Table Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-inherit-trans-table-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Inherit Trans Table Columns","description":"","searchText":"reference parameters naming & metadata description inherit trans table columns overview technical parameter name: description_inherit_transtable_columns description inheritance from the transformation columns to the transtable columns and persistend table columns: 0 - inherit if empty, 1 - always, 2 - never function description inherit transtable columns is a parameter in analyticscreator. default value 1 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937284,"name":"Description Set Special","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-set-special","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Set Special","description":"","searchText":"reference parameters naming & metadata description set special overview technical parameter name: description_set_special automatically set description of special columns (snapshotid, surrogate key, calendarid) : 0 - yes if empty, 1 - always, 2 - never function description set special is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937285,"name":"Description Use Statements","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-description-use-statements","breadcrumb":"Reference › Parameters › Naming & Metadata › Description Use Statements","description":"","searchText":"reference parameters naming & metadata description use statements overview technical parameter name: description_use_statements use statement as description: 0 - yes if empty (priority over inherited description), 1 - always, 2 - yes if empty (inherited description has priority), 3 - never function description use statements is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937286,"name":"Friendly Name Inherit Tables","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-inherit-tables","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Inherit Tables","description":"","searchText":"reference parameters naming & metadata friendly name inherit tables overview technical parameter name: friendlyname_inherit_tables friendly name inheritance from the tables to the dependent tables: 0 - inherit if empty, 1 - always, 2 - never function friendly name inherit tables is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937287,"name":"Friendly Name Inherit Trans","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-inherit-trans","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Inherit Trans","description":"","searchText":"reference parameters naming & metadata friendly name inherit trans overview technical parameter name: friendlyname_inherit_trans friendly name inheritance from the first transformation table to the transformation: 0 - inherit if empty, 1 - always, 2 - never function friendly name inherit trans is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937288,"name":"Friendly Name Inherit Trans Tables","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-inherit-trans-tables","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Inherit Trans Tables","description":"","searchText":"reference parameters naming & metadata friendly name inherit trans tables overview technical parameter name: friendlyname_inherit_transtables friendly name inheritance from the transformations to the transtables and persistend tables: 0 - inherit if empty, 1 - always, 2 - never function friendly name inherit transtables is a parameter in analyticscreator. default value 1 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937289,"name":"Friendly Name Inherit Table Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-inherit-table-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Inherit Table Columns","description":"","searchText":"reference parameters naming & metadata friendly name inherit table columns overview technical parameter name: friendlyname_inherit_tablecolumns friendly name inheritance from the table columns to the dependent table columns: 0 - inherit if empty, 1 - always, 2 - never function friendly name inherit tablecolumns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937290,"name":"Friendly Name Inherit Trans Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-inherit-trans-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Inherit Trans Columns","description":"","searchText":"reference parameters naming & metadata friendly name inherit trans columns overview technical parameter name: friendlyname_inherit_transcolumns friendly name inheritance from the table columns to the transformation columns: 0 - inherit if empty, 1 - always, 2 - never function friendly name inherit transcolumns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937291,"name":"Friendly Name Inherit Trans Table Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-inherit-trans-table-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Inherit Trans Table Columns","description":"","searchText":"reference parameters naming & metadata friendly name inherit trans table columns overview technical parameter name: friendlyname_inherit_transtable_columns friendly name inheritance from the transformation columns to the transtable columns and persistend table columns: 0 - inherit if empty, 1 - always, 2 - never function friendly name inherit transtable columns is a parameter in analyticscreator. default value 1 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937292,"name":"Friendly Name Set Special","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-friendly-name-set-special","breadcrumb":"Reference › Parameters › Naming & Metadata › Friendly Name Set Special","description":"","searchText":"reference parameters naming & metadata friendly name set special overview technical parameter name: friendlyname_set_special automatically set friendly name of special columns (snapshotid, surrogate key, calendarid) : 0 - yes if empty, 1 - always, 2 - never function friendly name set special is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937293,"name":"Display Folder Inherit Table Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-display-folder-inherit-table-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Display Folder Inherit Table Columns","description":"","searchText":"reference parameters naming & metadata display folder inherit table columns overview technical parameter name: displayfolder_inherit_tablecolumns olap display folder inheritance from the table columns to the dependent table columns: 0 - inherit if empty, 1 - always, 2 - never function displayfolder inherit tablecolumns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937294,"name":"Display Folder Inherit Trans Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-display-folder-inherit-trans-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Display Folder Inherit Trans Columns","description":"","searchText":"reference parameters naming & metadata display folder inherit trans columns overview technical parameter name: displayfolder_inherit_transcolumns olap display folder inheritance from the table columns to the transformation columns: 0 - inherit if empty, 1 - always, 2 - never function displayfolder inherit transcolumns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870937295,"name":"Display Folder Inherit Trans Table Columns","type":"topic","path":"/docs/reference/parameters/parameters-naming-and-metadata/parameters-naming-and-metadata-display-folder-inherit-trans-table-columns","breadcrumb":"Reference › Parameters › Naming & Metadata › Display Folder Inherit Trans Table Columns","description":"","searchText":"reference parameters naming & metadata display folder inherit trans table columns overview technical parameter name: displayfolder_inherit_transtable_columns olap display folder inheritance from the transformation columns to the transtable columns and persistend table columns: 0 - inherit if empty, 1 - always, 2 - never function displayfolder inherit transtable columns is a parameter in analyticscreator. default value 1 custom value not set. parameter groups naming & metadata names & metadata naming"}
,{"id":389870784719,"name":"References","type":"subsection","path":"/docs/reference/parameters/parameters-references","breadcrumb":"Reference › Parameters › References","description":"","searchText":"reference parameters references autocreated references use friendly name ref tables recursion depth dwh create references references inheritance references datamart references inheritance force manually created reference pk to pk cardinality delete unused references on delete columns"}
,{"id":389870937296,"name":"Autocreated References Use Friendly Name","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-autocreated-references-use-friendly-name","breadcrumb":"Reference › Parameters › References › Autocreated References Use Friendly Name","description":"","searchText":"reference parameters references autocreated references use friendly name overview technical parameter name: autocreated_references_use_friendly_name use friendly names instead of table names in description of autocreated references: 0- no, 1 - yes function autocreated references use friendly name is a parameter in analyticscreator. default value 0 custom value not set. parameter groups references relationships links"}
,{"id":389870937297,"name":"Ref Tables Recursion Depth","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-ref-tables-recursion-depth","breadcrumb":"Reference › Parameters › References › Ref Tables Recursion Depth","description":"","searchText":"reference parameters references ref tables recursion depth overview technical parameter name: ref_tables_recursion_depth max recursion depth due the detection of referenced tables in transformation wizard function ref tables recursion depth is a parameter in analyticscreator. default value 5 custom value not set. parameter groups references relationships links"}
,{"id":389870937298,"name":"DWH Create References","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-dwh-create-references","breadcrumb":"Reference › Parameters › References › DWH Create References","description":"","searchText":"reference parameters references dwh create references overview technical parameter name: dwh_create_references create disabled references between tables in data warehouse function dwh create references is a parameter in analyticscreator. default value 0 custom value not set. parameter groups references relationships links"}
,{"id":389870937299,"name":"References Inheritance","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-references-inheritance","breadcrumb":"Reference › Parameters › References › References Inheritance","description":"","searchText":"reference parameters references references inheritance overview technical parameter name: references_inheritance 0 - within schema only, 1 - within layer only, 2 - within layer and its neighbourhood, 3 - everywhere function references inheritance is a parameter in analyticscreator. default value 0 custom value not set. parameter groups references relationships links"}
,{"id":389870937300,"name":"References Datamart","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-references-datamart","breadcrumb":"Reference › Parameters › References › References Datamart","description":"","searchText":"reference parameters references references datamart overview technical parameter name: references_datamart 0 - all references are allowed, 1 - only references between objects in the same star are allowed, 2 - only references between the objects in the same schema are allowed function references datamart is a parameter in analyticscreator. default value 0 custom value not set. parameter groups references relationships links"}
,{"id":389870937301,"name":"References Inheritance Force Manually Created","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-references-inheritance-force-manually-created","breadcrumb":"Reference › Parameters › References › References Inheritance Force Manually Created","description":"","searchText":"reference parameters references references inheritance force manually created overview technical parameter name: references_inheritance_force_manually_created 0 - manually created references will be inherited like all other references, 1 - manually created references will be always inherited, 2 - manually created references and their successors will be always inherited function references inheritance force manually created is a parameter in analyticscreator. default value 0 custom value not set. parameter groups references relationships links"}
,{"id":389870937302,"name":"Reference PK To PK Cardinality","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-reference-pk-to-pk-cardinality","breadcrumb":"Reference › Parameters › References › Reference PK To PK Cardinality","description":"","searchText":"reference parameters references reference pk to pk cardinality overview technical parameter name: reference_pk_to_pk_cardinality cardinality of pk-to-pk reference. 0 - n:1, 1 - 1:1 function reference pk to pk cardinality is a parameter in analyticscreator. default value 0 custom value not set. parameter groups references relationships links"}
,{"id":389870937303,"name":"Delete Unused References On Delete Columns","type":"topic","path":"/docs/reference/parameters/parameters-references/parameters-references-delete-unused-references-on-delete-columns","breadcrumb":"Reference › Parameters › References › Delete Unused References On Delete Columns","description":"","searchText":"reference parameters references delete unused references on delete columns overview technical parameter name: delete_unused_references_on_delete_columns delete unused references on delete columns 0-no, 1-yes function delete unused references on delete columns is a parameter in analyticscreator. default value 0 custom value not set. parameter groups references relationships links"}
,{"id":389870784720,"name":"Connectors","type":"subsection","path":"/docs/reference/parameters/parameters-connectors","breadcrumb":"Reference › Parameters › Connectors","description":"","searchText":"reference parameters connectors oledb provider sql server azure blob connection string odata connection string"}
,{"id":388515715285,"name":"OLEDB Provider SQL Server","type":"topic","path":"/docs/reference/parameters/parameters-connectors/parameters-connectors-oledb-provider-sql-server","breadcrumb":"Reference › Parameters › Connectors › OLEDB Provider SQL Server","description":"","searchText":"reference parameters connectors oledb provider sql server overview technical parameter name: oledbprovider_sqlserver oledb provider for sql server function oledbprovider sql server is a parameter in analyticscreator. default value msoledbsql custom value not set. parameter groups connectors connections connector setup"}
,{"id":389870937304,"name":"Azure BLOB Connection String","type":"topic","path":"/docs/reference/parameters/parameters-connectors/parameters-connectors-azure-blob-connection-string","breadcrumb":"Reference › Parameters › Connectors › Azure BLOB Connection String","description":"","searchText":"reference parameters connectors azure blob connection string overview technical parameter name: azure_blob_connection_string connection string for azure blob storage function azure blob connection string is a parameter in analyticscreator. default value defaultendpointsprotocol=https;accountname={0};accountkey={1};endpointsuffix=core.windows.net custom value not set. parameter groups connectors connections connector setup"}
,{"id":389870937305,"name":"OData Connection String","type":"topic","path":"/docs/reference/parameters/parameters-connectors/parameters-connectors-odata-connection-string","breadcrumb":"Reference › Parameters › Connectors › OData Connection String","description":"","searchText":"reference parameters connectors odata connection string overview technical parameter name: odata_connection_string connection string for odata service function odata connection string is a parameter in analyticscreator. default value service document url={0};include atom elements=auto;include expanded entities=false;persist security info=false;time out=600;schema sample size=25;retry count=5;retry sleep=100;keep alive=false;max received message size=4398046511104 custom value not set. parameter groups connectors connections connector setup"}
,{"id":389870784721,"name":"Repository Names","type":"subsection","path":"/docs/reference/parameters/parameters-repository-names","breadcrumb":"Reference › Parameters › Repository Names","description":"","searchText":"reference parameters repository names layer1 name layer2 name layer3 name layer4 name layer5 name layer6 name repository name"}
,{"id":389870937306,"name":"Layer1 Name","type":"topic","path":"/docs/reference/parameters/parameters-repository-names/parameters-repository-names-layer1-name","breadcrumb":"Reference › Parameters › Repository Names › Layer1 Name","description":"","searchText":"reference parameters repository names layer1 name overview technical parameter name: layer1_name source layer name function layer1 name is a parameter in analyticscreator. default value source layer custom value not set. parameter groups repository names layer names names"}
,{"id":389870937307,"name":"Layer2 Name","type":"topic","path":"/docs/reference/parameters/parameters-repository-names/parameters-repository-names-layer2-name","breadcrumb":"Reference › Parameters › Repository Names › Layer2 Name","description":"","searchText":"reference parameters repository names layer2 name overview technical parameter name: layer2_name staging layer name function layer2 name is a parameter in analyticscreator. default value staging layer custom value not set. parameter groups repository names layer names names"}
,{"id":389870937308,"name":"Layer3 Name","type":"topic","path":"/docs/reference/parameters/parameters-repository-names/parameters-repository-names-layer3-name","breadcrumb":"Reference › Parameters › Repository Names › Layer3 Name","description":"","searchText":"reference parameters repository names layer3 name overview technical parameter name: layer3_name persisted staging layer name function layer3 name is a parameter in analyticscreator. default value persisted staging layer custom value not set. parameter groups repository names layer names names"}
,{"id":389870937309,"name":"Layer4 Name","type":"topic","path":"/docs/reference/parameters/parameters-repository-names/parameters-repository-names-layer4-name","breadcrumb":"Reference › Parameters › Repository Names › Layer4 Name","description":"","searchText":"reference parameters repository names layer4 name overview technical parameter name: layer4_name transformation layer name function layer4 name is a parameter in analyticscreator. default value transformation layer custom value not set. parameter groups repository names layer names names"}
,{"id":389870937310,"name":"Layer5 Name","type":"topic","path":"/docs/reference/parameters/parameters-repository-names/parameters-repository-names-layer5-name","breadcrumb":"Reference › Parameters › Repository Names › Layer5 Name","description":"","searchText":"reference parameters repository names layer5 name overview technical parameter name: layer5_name data warehouse layer name function layer5 name is a parameter in analyticscreator. default value data warehouse layer custom value not set. parameter groups repository names layer names names"}
,{"id":389870937311,"name":"Layer6 Name","type":"topic","path":"/docs/reference/parameters/parameters-repository-names/parameters-repository-names-layer6-name","breadcrumb":"Reference › Parameters › Repository Names › Layer6 Name","description":"","searchText":"reference parameters repository names layer6 name overview technical parameter name: layer6_name data mart layer name function layer6 name is a parameter in analyticscreator. default value data mart layer custom value not set. parameter groups repository names layer names names"}
,{"id":389870937312,"name":"Repository Name","type":"topic","path":"/docs/reference/parameters/parameters-repository-names/parameters-repository-names-repository-name","breadcrumb":"Reference › Parameters › Repository Names › Repository Name","description":"","searchText":"reference parameters repository names repository name overview technical parameter name: repository_name repository name function repository name is a parameter in analyticscreator. default value not set. custom value not set. parameter groups repository names layer names names"}
,{"id":389870784722,"name":"Logging","type":"subsection","path":"/docs/reference/parameters/parameters-logging","breadcrumb":"Reference › Parameters › Logging","description":"","searchText":"reference parameters logging ac log"}
,{"id":388515715280,"name":"AC Log","type":"topic","path":"/docs/reference/parameters/parameters-logging/parameters-logging-ac-log","breadcrumb":"Reference › Parameters › Logging › AC Log","description":"","searchText":"reference parameters logging ac log overview technical parameter name: ac_log add log info. 0 - no, 1 - yes function ac log is a parameter in analyticscreator. default value 0 custom value not set. parameter groups logging diagnostics log"}
,{"id":389870784723,"name":"Semantic Model","type":"subsection","path":"/docs/reference/parameters/parameters-semantic-model","breadcrumb":"Reference › Parameters › Semantic Model","description":"","searchText":"reference parameters semantic model measure default display folder attribute default display folder measure default name tabular olap isavailableinmdx"}
,{"id":389870937313,"name":"Measure Default Display Folder","type":"topic","path":"/docs/reference/parameters/parameters-semantic-model/parameters-semantic-model-measure-default-display-folder","breadcrumb":"Reference › Parameters › Semantic Model › Measure Default Display Folder","description":"","searchText":"reference parameters semantic model measure default display folder overview technical parameter name: measure_default_display_folder default measure display folder function measure default display folder is a parameter in analyticscreator. default value measures custom value not set. parameter groups semantic model olap model olap"}
,{"id":389870937314,"name":"Attribute Default Display Folder","type":"topic","path":"/docs/reference/parameters/parameters-semantic-model/parameters-semantic-model-attribute-default-display-folder","breadcrumb":"Reference › Parameters › Semantic Model › Attribute Default Display Folder","description":"","searchText":"reference parameters semantic model attribute default display folder overview technical parameter name: attribute_default_display_folder default attribute display folder function attribute default display folder is a parameter in analyticscreator. default value not set. custom value not set. parameter groups semantic model olap model olap"}
,{"id":389870937315,"name":"Measure Default Name","type":"topic","path":"/docs/reference/parameters/parameters-semantic-model/parameters-semantic-model-measure-default-name","breadcrumb":"Reference › Parameters › Semantic Model › Measure Default Name","description":"","searchText":"reference parameters semantic model measure default name overview technical parameter name: measure_default_name default measure name pattern function measure default name is a parameter in analyticscreator. default value {aggregationname} of {columnname} ({tablename}) custom value not set. parameter groups semantic model olap model olap"}
,{"id":389870937316,"name":"Tabular OLAP Isavailableinmdx","type":"topic","path":"/docs/reference/parameters/parameters-semantic-model/parameters-semantic-model-tabular-olap-isavailableinmdx","breadcrumb":"Reference › Parameters › Semantic Model › Tabular OLAP Isavailableinmdx","description":"","searchText":"reference parameters semantic model tabular olap isavailableinmdx overview technical parameter name: tabular_olap_isavailableinmdx isavailableinmdx option for the tabular olap attributes. 0-no, 1 - yes function tabular olap isavailableinmdx is a parameter in analyticscreator. default value 1 custom value not set. parameter groups semantic model olap model olap"}
,{"id":389870784724,"name":"SQL Templates","type":"subsection","path":"/docs/reference/parameters/parameters-sql-templates","breadcrumb":"Reference › Parameters › SQL Templates","description":"","searchText":"reference parameters sql templates update statistics hist template update statistics persist template main dwh sqlcmd variable"}
,{"id":389870937317,"name":"Update Statistics Hist Template","type":"topic","path":"/docs/reference/parameters/parameters-sql-templates/parameters-sql-templates-update-statistics-hist-template","breadcrumb":"Reference › Parameters › SQL Templates › Update Statistics Hist Template","description":"","searchText":"reference parameters sql templates update statistics hist template overview technical parameter name: update_statistics_hist_template pattern to create update statistics statement in historizing stored procedure. {tablename} cal be used as alias function update statistics hist template is a parameter in analyticscreator. default value update statistics {tablename} custom value not set. parameter groups sql templates sql variables sql"}
,{"id":389870937318,"name":"Update Statistics Persist Template","type":"topic","path":"/docs/reference/parameters/parameters-sql-templates/parameters-sql-templates-update-statistics-persist-template","breadcrumb":"Reference › Parameters › SQL Templates › Update Statistics Persist Template","description":"","searchText":"reference parameters sql templates update statistics persist template overview technical parameter name: update_statistics_persist_template pattern to create update statistics statement in persisting stored procedure. {tablename} cal be used as alias function update statistics persist template is a parameter in analyticscreator. default value update statistics {tablename} custom value not set. parameter groups sql templates sql variables sql"}
,{"id":389870937319,"name":"Main DWH SQLCMD Variable","type":"topic","path":"/docs/reference/parameters/parameters-sql-templates/parameters-sql-templates-main-dwh-sqlcmd-variable","breadcrumb":"Reference › Parameters › SQL Templates › Main DWH SQLCMD Variable","description":"","searchText":"reference parameters sql templates main dwh sqlcmd variable overview technical parameter name: main_dwh_sqlcmd_variable sqlcmd variable using to adress the main dwh database. will be used in case of multi-db dwh function main dwh sqlcmd variable is a parameter in analyticscreator. default value $ custom value not set. parameter groups sql templates sql variables sql"}
,{"id":389870784725,"name":"Source Import","type":"subsection","path":"/docs/reference/parameters/parameters-source-import","breadcrumb":"Reference › Parameters › Source Import","description":"","searchText":"reference parameters source import import sql server use no lock"}
,{"id":389870937320,"name":"Import SQL Server Use No Lock","type":"topic","path":"/docs/reference/parameters/parameters-source-import/parameters-source-import-import-sql-server-use-no-lock","breadcrumb":"Reference › Parameters › Source Import › Import SQL Server Use No Lock","description":"","searchText":"reference parameters source import import sql server use no lock overview technical parameter name: import_sqlserver_use_nolock use nolock hint in import packages for sql server. 0 - no, 1 - yes function import sql server use nolock is a parameter in analyticscreator. default value 0 custom value not set. parameter groups source import profiling import"}
,{"id":389870784726,"name":"Project Limits","type":"subsection","path":"/docs/reference/parameters/parameters-project-limits","breadcrumb":"Reference › Parameters › Project Limits","description":"","searchText":"reference parameters project limits project restrict file path length project restrict file name length"}
,{"id":388515715287,"name":"Project Restrict File Path Length","type":"topic","path":"/docs/reference/parameters/parameters-project-limits/parameters-project-limits-project-restrict-file-path-length","breadcrumb":"Reference › Parameters › Project Limits › Project Restrict File Path Length","description":"","searchText":"reference parameters project limits project restrict file path length overview technical parameter name: project_restrict_filepath_length if set, limits the maximum length of the full file name to a specified number of characters function project restrict file path length is a parameter in analyticscreator. default value not set. custom value not set. parameter groups project limits file limits limits"}
,{"id":389870937321,"name":"Project Restrict File Name Length","type":"topic","path":"/docs/reference/parameters/parameters-project-limits/parameters-project-limits-project-restrict-file-name-length","breadcrumb":"Reference › Parameters › Project Limits › Project Restrict File Name Length","description":"","searchText":"reference parameters project limits project restrict file name length overview technical parameter name: project_restrict_filename_length if set, limits the maximum length of the file name to a specified number of characters function project restrict file name length is a parameter in analyticscreator. default value not set. custom value not set. parameter groups project limits file limits limits"}
,{"id":387188914419,"name":"Technical configuration parameters","type":"subsection","path":"/docs/reference/parameters/parameters-technical-configuration-parameters","breadcrumb":"Reference › Parameters › Technical configuration parameters","description":"","searchText":"reference parameters technical configuration parameters ac_log deployment_create_subdirectory diagram_name_pattern dwh_metadata_in_extended_properties hist_proc_use_hash_join oledbprovider_sqlserver pers_default_partswitch project_restrict_filepath_length table_compression_type"}
,{"id":383509340376,"name":"Other parameters","type":"subsection","path":"/docs/reference/parameters/parameters-other-parameters","breadcrumb":"Reference › Parameters › Other parameters","description":"","searchText":"reference parameters other parameters other parameters"}
,
{"id":383461199045,"name":"Tutorials","type":"category","path":"/docs/tutorials","breadcrumb":"Tutorials","description":"","searchText":"tutorials this section contains guided walkthroughs based on sample datasets and example scenarios. tutorials are intended to help you become familiar with analyticscreator by following complete modeling, generation, deployment, and execution flows in a controlled environment. use these tutorials to understand how metadata is translated into warehouse structures, pipelines, and analytical models across different platforms and source scenarios. available tutorials northwind data warehouse guided walkthrough based on the northwind dataset. source import and modeling transformations and data marts end-to-end warehouse flow open tutorial coming soon sql server data warehouse walkthrough end-to-end tutorial for building a sql server-based warehouse. repository and connector setup wizard-generated model execution with sql server and ssis coming soon microsoft fabric walkthrough tutorial for generating and deploying a warehouse model to microsoft fabric. fabric target setup pipeline generation semantic model integration coming soon sap to data warehouse walkthrough tutorial for importing sap metadata and generating a layered warehouse model. sap metadata import persistent staging dimensional or hybrid modeling how to use this section tutorials are intended as practical implementation guides. they are most useful when followed in a test environment together with the quick start guide and the related reference pages. start with northwind if you are new to analyticscreator use platform-specific tutorials to understand deployment patterns use source-specific tutorials to understand metadata import and modeling behavior common principles across tutorials practical walkthroughs each tutorial focuses on a complete implementation flow rather than isolated features. sample datasets tutorials use controlled example data so that modeling and generation steps can be reproduced. end-to-end flow tutorials typically cover metadata import, model generation, deployment, and execution. reference alignment tutorial steps should be used together with technical reference pages for deeper detail. key takeaway tutorials provide guided, reproducible examples that show how analyticscreator is used in practice across datasets, platforms, and source scenarios."}
,{"id":383225948382,"name":"Northwind DWH Walkthrough","type":"section","path":"/docs/tutorials/northwind-dwh-walkthrough","breadcrumb":"Tutorials › Northwind DWH Walkthrough","description":"","searchText":"tutorials northwind dwh walkthrough step-by-step: sql server northwind project create your first data warehouse with analyticscreator analyticscreator offers pre-configured demos for testing within your environment. this guide outlines the steps to transition from the northwind oltp database to the northwind data warehouse model. once completed, you will have a fully generated dwh project ready to run locally. load the demo project from the file menu, select load from cloud. choose nw_demo enter a name for your new repository (default: nw_demo) note: this repository contains metadata onlyâno data is moved. analyticscreator will automatically generate all required project parameters. project structure: the 5-layer model analyticscreator will generate a data warehouse project with five layers: sources â raw data from the source system (northwind oltp). staging layer â temporary storage for data cleansing and preparation. persisted staging layer â permanent storage of cleaned data for historization. core layer â integrated business modelâstructured and optimized for querying. datamart layer â optimized for reportingâorganized by business topic (e.g., sales, inventory). northwind setup (if not already installed) step 1: check if the northwind database exists open sql server management studio (ssms) and verify that the northwind database is present. if yes, skip to the next section. if not, proceed to step 2. step 2: create the northwind database run the setup script from microsoft: đľ download script or copy-paste it into ssms and execute. step 3: verify database use northwind; go select * from information_schema.tables where table_schema = 'dbo' and table_type = 'base table'; once confirmed, you can proceed with the next steps to configure the analyticscreator connector with your northwind database. note: analyticscreator uses only native microsoft connectors, and we do not store any personal information. step 4: change database connector navigate to sources > connectors. you will notice that a connector is already configured. for educational purposes, the connection string is not encrypted yet. to edit or add a new connection string, go to options > encrypted strings > add. paste your connection string as demonstrated in the video below. after adding the new connection string, it's time to test your connection. go to sources â connectors and press the test button to verify your connection. step 5: create a new deployment in this step, you'll configure and deploy your project to the desired destination. please note that only the metadata will be deployed; there will be no data movement or copy during this process. navigate to deployments in the menu and create a new deployment. assign a name to your deployment. configure the connection for the destination set the project path where the deployment will be saved. select the packages you want to generate. review the connection variables and click deploy to initiate the process. finally, click deploy to complete the deployment. in this step, your initial data warehouse project is created. note that only the metadataâthe structure of your projectâis generated at this stage. you can choose between two options for package generation: ssis (sql server integration services) adf (azure data factory) ssis follows a traditional etl tool architecture, making it a suitable choice for on-premises data warehouse architectures. in contrast, adf is designed with a modern cloud-native architecture, enabling seamless integration with various cloud services and big data systems. this architectural distinction makes adf a better fit for evolving data integration needs in cloud-based environments. to execute your package and move your data, you will still need an integration runtime (ir). keep in mind that analyticscreator only generates the project at the metadata level and does not access your data outside the analyticscreator interface. it does not link your data to us, ensuring that your data remains secure in its original location. for testing purposes, you can run your package in microsoft visual studio 2022, on your local sql server, or even in azure data factory."}
,
{"id":383461199046,"name":"Platform Support","type":"category","path":"/docs/platform-support","breadcrumb":"Platform Support","description":"","searchText":"platform support this section describes how analyticscreator integrates with supported target platforms and what it generates for each environment. analyticscreator is a metadata-driven design application that generates sql-based data warehouse structures, orchestration artifacts, and semantic models. the generated assets are then deployed and executed on the selected target platform. supported platforms microsoft fabric support for fabric data warehouse, lakehouse sql endpoints, onelake, pipelines, and integrated semantic models. warehouse and lakehouse targets pipeline generation semantic model integration view platform details microsoft azure / data factory support for azure data factory orchestration together with azure sql and synapse-based warehouse execution. adf pipeline generation azure sql and synapse targets cloud orchestration view platform details sql server support for sql server-based repositories, warehouse generation, and ssis-based execution. on-premise warehouse targets sql and stored procedure generation ssis orchestration view platform details power bi support for semantic model generation including measures, relationships, and analytical structures. tabular models measures and relationships reporting layer view platform details how to use this section each platform page explains how analyticscreator maps metadata definitions to platform-specific implementations. supported services and runtimes generated sql, pipelines, and semantic models deployment and execution behavior platform-specific constraints and design considerations common principles across platforms metadata-driven generation all structures and logic are generated from metadata definitions. platform-side execution processing and orchestration run on the target platform. consistent modeling approach dimensional, data vault, and hybrid models are supported across platforms. generated deployment assets sql objects, pipelines, and semantic models are generated automatically. key differences between platforms orchestration: ssis vs data factory vs fabric pipelines execution environment: on-premise vs cloud vs unified platform storage model: database vs lakehouse vs onelake integration with semantic layers key takeaway analyticscreator generates platform-specific warehouse, pipeline, and analytical artifacts from metadata, while execution and runtime behavior are handled by the selected platform."}
,{"id":383225948376,"name":"Microsoft Fabric","type":"section","path":"/docs/platform-support/microsoft-fabric","breadcrumb":"Platform Support › Microsoft Fabric","description":"","searchText":"platform support microsoft fabric this page describes how analyticscreator generates and integrates data warehouse and analytical solutions for microsoft fabric environments. overview analyticscreator supports microsoft fabric as a target platform for data warehouse generation, orchestration, and analytical modeling. it generates sql-based structures, pipelines, and semantic models that run within fabric services. analyticscreator itself does not execute workloads inside fabric. it generates artifacts that are deployed and executed within fabric components such as sql endpoints, pipelines, and semantic models. supported services and components fabric data warehouse (sql endpoint) fabric lakehouse (sql analytics endpoint) onelake storage fabric data pipelines power bi semantic models (fabric-integrated) what analyticscreator generates for microsoft fabric, analyticscreator generates: sql objects: stg tables (import layer) persistent staging and historization tables core transformations (views or tables) dm layer (facts and dimensions) stored procedures for: data loading historization persisting logic fabric pipelines: orchestration of load and transformation steps dependency-based execution semantic models: dimensions and measures relationships between entities supported modeling approaches dimensional modeling (facts and dimensions) data vault modeling (hubs, links, satellites) hybrid approaches (data vault foundation with dimensional output) historized models (scd2 with valid-from and valid-to) both warehouse and lakehouse-style architectures can be implemented depending on the selected fabric components. deployment and execution model analyticscreator separates generation, deployment, and execution: analyticscreator generates sql objects, pipelines, and semantic models deployment publishes these artifacts into microsoft fabric execution is performed by fabric services (pipelines and sql engine) data processing runs inside fabric: sql transformations run on fabric sql endpoints pipelines orchestrate execution using fabric pipeline services data is stored in onelake ci/cd and version control metadata is stored in the analyticscreator repository projects can be versioned via json export (acrepo) deployment artifacts can be integrated into ci/cd pipelines fabric environments can be targeted via deployment configurations connectors, sources, and exports supported sources sap systems sql server and relational databases other supported connectors exports and targets fabric sql endpoints lakehouse tables semantic models for power bi prerequisites, limitations, and notes fabric workspace and permissions must be configured linked services or connections must be defined for pipelines sql compatibility depends on fabric sql endpoint capabilities performance depends on data volume, partitioning, and load strategy design considerations: choose between data warehouse and lakehouse based on workload use persistent staging to avoid repeated source reads validate generated joins and transformations for performance example use cases building a fabric-native data warehouse with automated sql generation implementing data vault models on top of onelake storage generating power bi-ready semantic models from warehouse structures replacing manual pipeline development with generated fabric pipelines platform-specific notes fabric unifies storage and compute, which simplifies deployment compared to separate azure services lakehouse and warehouse approaches can coexist in the same environment semantic models are tightly integrated with power bi related content quick start guide understanding analyticscreator fabric tutorials and examples key takeaway analyticscreator generates sql structures, pipelines, and semantic models for microsoft fabric, while execution and storage are handled by fabric services such as sql endpoints, pipelines, and onelake."}
,{"id":383225948377,"name":"Azure","type":"section","path":"/docs/platform-support/azure","breadcrumb":"Platform Support › Azure","description":"","searchText":"platform support azure this page describes how analyticscreator generates and integrates data warehouse solutions in microsoft azure environments, with a focus on azure data factory for orchestration and sql-based engines for processing. overview analyticscreator supports microsoft azure as a target environment by generating sql-based data warehouse structures, orchestration pipelines, and analytical models. azure data factory is used for workflow orchestration, while sql-based engines handle data processing and storage. analyticscreator generates all required artifacts, but execution is performed by azure services such as data factory and sql engines. supported services and components azure data factory (orchestration) azure sql database azure sql managed instance azure synapse analytics (sql pools) azure storage (as data source or staging area) power bi (analytical layer) what analyticscreator generates for azure environments, analyticscreator generates: sql objects: stg tables (import layer) persistent staging and historization tables core transformations (views or persisted tables) dm layer (facts and dimensions) stored procedures for: data loading historization persisting logic azure data factory pipelines: execution orchestration dependency handling integration with linked services semantic models for reporting tools such as power bi supported modeling approaches dimensional modeling (facts and dimensions) data vault modeling (hubs, links, satellites) hybrid approaches historized models (scd2 with valid-from and valid-to) modeling behavior is independent of azure and is defined in metadata. azure determines where and how generated logic is executed. deployment and execution model analyticscreator separates generation, deployment, and execution: analyticscreator generates sql objects and pipeline definitions deployment publishes these artifacts to azure services execution is handled by azure data factory and sql engines typical execution flow: azure data factory triggers pipelines data is extracted from sources data is written to stg tables stored procedures execute transformations and historization core and dm layers are updated ci/cd and version control metadata is stored in the analyticscreator repository projects can be versioned via json export (acrepo) generated artifacts can be integrated into azure devops pipelines deployment configurations support multiple environments connectors, sources, and exports supported sources sap systems sql server and azure sql flat files and external storage via data factory exports and targets azure sql database azure synapse sql pools power bi semantic models prerequisites, limitations, and notes azure subscription and resource group required data factory instance must be configured linked services must be defined for source systems sql compatibility depends on target engine (azure sql vs synapse) design considerations: azure environments are modular and require explicit configuration orchestration and storage are separated services performance depends on selected sql engine and scaling configuration example use cases building a cloud-based data warehouse using azure sql database using azure data factory to orchestrate etl pipelines implementing data vault models in azure synapse automating pipeline generation instead of manual adf development platform-specific notes azure separates orchestration (data factory) from compute (sql engines) pipeline configuration requires linked services and integration runtimes multiple sql engines can be used depending on workload requirements related content quick start guide understanding analyticscreator azure tutorials and examples key takeaway analyticscreator generates sql structures and azure data factory pipelines, while execution is handled by azure services such as data factory and sql-based compute engines."}
,{"id":383225948378,"name":"SQL Server","type":"section","path":"/docs/platform-support/sql-server","breadcrumb":"Platform Support › SQL Server","description":"","searchText":"platform support sql server this page describes how analyticscreator generates and integrates data warehouse solutions for microsoft sql server environments. overview analyticscreator supports sql server as both the metadata repository platform and a primary target platform for generated data warehouse structures. in a typical sql server-based setup, analyticscreator generates database objects, loading procedures, ssis packages, and analytical structures that run on sql server and related microsoft services. analyticscreator itself is a design-time application. it generates sql-based artifacts, but execution takes place in sql server, sql server integration services, and downstream analytical services. supported services and components sql server database engine sql server integration services (ssis) sql server analysis services, where used for tabular or analytical models power bi as a downstream semantic and reporting target sql server-based repository for metadata storage what analyticscreator generates for sql server environments, analyticscreator generates: sql objects: stg tables for source import persistent staging and historization tables core transformations as views or persisted tables dm layer structures with facts and dimensions stored procedures for: data loading historization persisting logic customizable processing steps ssis packages for: source import workflow execution etl orchestration analytical outputs: data marts tabular or semantic model structures where configured power bi-ready dimensional outputs deployment assets: deployment packages visual studio solution content generated sql deployment artifacts supported modeling approaches dimensional modeling with facts and dimensions data vault modeling with hubs, links, and satellites hybrid approaches combining data vault foundations with dimensional output historized models using valid-from and valid-to logic snapshot-based historization patterns in sql server-based models, analyticscreator can generate a layered flow from source to staging, persistent staging, core, data mart, and presentation-oriented outputs. deployment and execution model analyticscreator separates structure generation, deployment, and execution: analyticscreator stores metadata in the repository and generates sql server artifacts from that metadata synchronization materializes the modeled structure in a sql server database deployment creates the required database assets and related execution packages execution is performed by sql server and ssis, not by analyticscreator itself typical sql server execution flow: metadata is stored in the sql server repository the wizard generates a draft model synchronization materializes the model as sql server objects deployment creates sql server database content and ssis packages ssis packages are executed to load and process data ci/cd and version control repository metadata is stored in sql server projects can be exported for versioning and deployment control generated deployment packages can be used in development, test, and production processes visual studio-based deployment assets support controlled release workflows connectors, sources, and exports relevant source types sql server source systems sap sources with sql server as target platform files and other supported source connectors relevant exports and downstream targets sql server data warehouse databases ssis execution packages analysis services or power bi-oriented semantic outputs prerequisites, limitations, and notes a sql server instance is required for the repository a target sql server database is required for generated warehouse objects ssis is required when package-based orchestration is used performance depends on indexing, load strategy, and transformation complexity generated sql should still be reviewed where platform-specific tuning is required design considerations: persistent staging should be used deliberately to support reprocessing and historization persisting can improve performance for complex transformations by materializing view output into tables historization strategy affects both storage volume and processing behavior example use cases building an on-premise sql server data warehouse with ssis-based loading modernizing an existing sql server warehouse into a metadata-driven model generating dimensional marts and semantic outputs for power bi implementing data vault or hybrid architectures on sql server platform-specific faq does analyticscreator execute etl inside sql server? analyticscreator generates sql objects and procedures for sql server, but workflow execution is typically handled through generated ssis packages or other generated orchestration assets. does synchronization load business data? no. synchronization materializes the structure in sql server. data loading happens later during execution. can sql server be both source and target? yes. sql server can be used as a source system, as the repository platform, and as the target warehouse platform. can i use power bi with a sql server-based model? yes. analyticscreator can generate dimensional and semantic outputs that are intended for downstream use in power bi. proof assets demo transcripts show the repository stored in sql server, synchronization creating a new sql server database, and deployment producing ssis packages and sql-based structures demo transcripts also show generated historization procedures, view-based transformations, persisting procedures, and data mart outputs for analytical consumption related content quick start guide understanding analyticscreator sql server tutorials and examples historization reference persisting reference commercial solution page for product-level positioning and commercial overview, see the analyticscreator sql server solution page. key takeaway in sql server environments, analyticscreator generates the warehouse schema, loading procedures, ssis assets, and analytical structures, while sql server and related microsoft services execute and host the resulting solution."}
,{"id":383225948379,"name":"Power BI","type":"section","path":"/docs/platform-support/power-bi","breadcrumb":"Platform Support › Power BI","description":"","searchText":"platform support power bi this page describes how analyticscreator generates and integrates analytical models for power bi. overview analyticscreator supports power bi as a target for analytical consumption by generating semantic models based on the data warehouse structure. these models define dimensions, measures, and relationships that can be used directly in reporting. analyticscreator does not execute data processing inside power bi. instead, it generates semantic structures that are consumed by power bi after data has been processed in the underlying data warehouse platform. supported services and components power bi semantic models (tabular models) power bi datasets power bi desktop and power bi service directquery and import modes what analyticscreator generates for power bi, analyticscreator generates: semantic models: dimensions and facts mapped from dm layer relationships between entities measures and calculated fields model structure: hierarchies (e.g. date hierarchies) attribute groupings metadata descriptions deployment-ready artifacts: tabular model definitions integration with deployment workflows supported modeling approaches dimensional modeling (star schema) measures derived from fact tables hierarchical dimensions (e.g. time, geography) data vault models are not directly exposed to power bi. instead, dimensional structures are generated from core layers and used as the basis for semantic models. deployment and execution model analyticscreator separates semantic model generation from data processing: analyticscreator generates the semantic model definition the model is deployed to power bi or an analytical engine data processing happens in the underlying data warehouse power bi consumes the processed data through the semantic model execution flow: data is processed in stg, core, and dm layers semantic model references dm structures power bi queries the model or underlying data source ci/cd and version control semantic models are generated from metadata definitions model definitions can be included in deployment pipelines integration with version-controlled analyticscreator projects connectors, sources, and exports data sources for power bi sql server azure sql microsoft fabric other supported warehouse targets export targets power bi semantic models tabular model deployments prerequisites, limitations, and notes power bi requires access to the deployed data warehouse model performance depends on underlying data model design directquery performance depends on source system performance design considerations: use dm layer as the source for semantic models avoid exposing stg or core layers directly ensure measures are defined consistently example use cases generating a power bi-ready star schema from a data warehouse automating creation of measures and relationships standardizing reporting models across projects reducing manual modeling effort in power bi platform-specific faq does analyticscreator replace power bi modeling? analyticscreator generates the base semantic model, including dimensions, relationships, and measures. additional report-specific logic can still be implemented in power bi if required. where are measures defined? measures can be generated as part of the semantic model based on metadata definitions and can be extended in power bi. can power bi connect directly to core or stg? this is technically possible but not recommended. the dm layer should be used as the primary source for reporting. proof assets generated semantic models include dimensions, measures, and relationships based on metadata demo scenarios show end-to-end flow from source to power bi-ready model related content quick start guide understanding analyticscreator data mart modeling semantic model reference commercial solution page for product-level positioning and overview, see the analyticscreator power bi solution page. key takeaway analyticscreator generates semantic models for power bi based on data warehouse structures, while data processing remains in the underlying platform."}
]
