A transformation is a metadata object used to define how data is processed in the staging and warehouse layers. Depending on the transformation type, it can be modeled as a automatically-generated view, a manual view, a script-based process, or an external process.
Function
The Transformation feature is used to define and maintain transformation logic in the model.
Transformations are used to process source data and prepare it for downstream warehouse structures. The current documentation confirms regular, manual, script, and external transformation types.
Access
Transformations are available in the dataflow diagram of the main AnalyticsCreator user interface.
How to access
Navigation tree
Not applicable.
Toolbar
ETL → Transformation
Diagram
Dataflow diagram → Right-click context menu → Add → Transformation
Visual element
Transformation
Screen overview
The Transformation feature provides access to transformation definitions in the dataflow diagram.
Add transformation: Creates a new transformation from the diagram context menu.
Regular transformation: Transformation described in tabular form that results in a generated view.
Manual transformation: Hand-created view defined manually by the user.
Script transformation: Transformation based on SQL scripts, often calling stored procedures.
External transformation: Transformation created outside AnalyticsCreator, for example as an SSIS package.
Related topics
Dataflow diagram
Source
Table
Persisting
Macros
Predefined transformations
[
{"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":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 structured reference for the analyticscreator user interface, entities, types, and parameters. this reference guide is organized into sections and subsections to help you quickly find interface elements, object types, dialogs, wizards, and configuration details in analyticscreator. sections [link:365118109942|user interface] toolbar, navigation tree, dataflow diagram, pages, lists, dialogs, and wizards. [link:365178121463|entity types] connector types, source types, table types, transformation types, package types, and more. [link:365178123475|entities] reference pages for main analyticscreator object classes such as layers, sources, tables, and packages. [link:365178123499|parameters] system and project parameters including technical and environment-related settings."}
,{"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 provides access to the main functional areas of analyticscreator. it is organized into logical sections that group related actions and configuration options, supporting a structured and efficient workflow. each section focuses on a specific aspect of the data product lifecycle: file contains general application actions such as creating or opening repositories, saving changes, and managing overall workspace settings. sources used to define and manage source systems. this includes configuring connections, importing metadata, and maintaining source structures. dwh focuses on data warehouse modeling. users define transformations, historization, and core structures required for building integrated data models. data mart supports the creation of data products for analytical consumption. this includes defining business-oriented models and preparing data for reporting tools. etl provides access to generation and configuration of data movement and transformation processes, such as pipelines or integration workflows. deployment controls the generation and deployment of artifacts to target environments. this includes creating deployment packages and executing releases. options contains configuration settings for the application, repositories, and environment-specific behavior. help provides access to documentation, guidance, and additional support resources. the toolbar structure reflects the typical workflow in analyticscreator—from source definition to modeling, transformation, and deployment—ensuring a clear and guided development process"}
,{"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 sources the sources menu is where you configure data connectivity. add new connectors, manage connected systems (databases and files), and maintain reference tables used across models. icon feature description connectors lists and manages available connectors for different data sources. sources displays and manages connected source systems (databases and flat files). references manages reference tables for lookups, hierarchies, or static mappings. new connector adds a new data source connector (select type and authentication). new connector imports connector definitions from a previously exported file. new connector imports connector settings directly from cloud storage or a repository."}
,{"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 dwh the dwh menu focuses on warehouse modeling. define layers and schemas, configure tables and indexes, and manage reusable assets such as references, macros, predefined transformations, and snapshots. icon feature description layers configure warehouse layers and their responsibilities. schemas list and manage schemas within the warehouse model. tables display and configure fact and dimension tables. indexes list and configure indexes to optimize query performance. references manage reference tables for lookups, hierarchies, or static mappings. macros create and manage reusable macro actions. predefined transformations library of ready-to-use transformations for common patterns. snapshots define snapshot structures to capture point-in-time states."}
,{"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 data mart the data products menu models analytical products for bi consumption. organize related stars into galaxies, define star schemas, manage hierarchies and roles, and configure partitions and semantic models. icon feature description galaxies organize related star schemas into a galaxy for analytical grouping. stars define star schemas containing facts and dimensions. hierarchies manage hierarchical structures (e.g., year â quarter â month). roles define user roles and access permissions for data products. partitions configure table partitions for scale and performance. models define semantic models built on top of the warehouse for bi tools."}
,{"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 etl the etl menu contains development assets for extraction, transformation, and loading. group work into packages, write scripts, manage imports, and handle historization scenarios with reusable transformations and generated dimensions. icon feature description packages list etl packages that group transformations and workflows. scripts contain sql or script-based transformations for etl. imports manage import processes from external sources into the warehouse. historizations handle slowly changing dimensions and historical data tracking. transformations define transformation logic for staging and warehouse layers. new transformations launch transformation wizard calendar dimension generates a reusable calendar dimension (year, month, day, etc.). time dimension creates a detailed time dimension (hours, minutes, seconds). snapshot dimension creates snapshot dimensions to capture point-in-time records."}
,{"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 deployment the deployment menu packages your modeled assets for delivery to target environments. use it to build and export deployment artifacts for your warehouse or data products. icon feature description deployment package build and export deployment packages for the warehouse or data products."}
,{"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 options the options menu centralizes application-wide settings. configure user groups, warehouse defaults, interface preferences, global parameters, and encrypted values used throughout projects. icon feature description user groups manage user groups and access levels. dwh settings configure global warehouse settings such as naming and storage rules. interface customize interface preferences and appearance. parameter define global and local parameters for etl and modeling. encrypted strings manage encrypted connection strings and sensitive values."}
,{"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 help the help menu provides export tools and links to external resources. generate documentation, open knowledge resources, and review legal and product information. icon feature description export to visio export diagrams to microsoft visio for documentation. export in word export documentation directly to a microsoft word file. wikipedia open a relevant wikipedia article for reference. videos links to instructional or demo videos. community links to the user community or forums. version history show version history and change logs. eula display the end user license agreement. about show software version, credits, and licensing information."}
,{"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 a structured view of all elements within the current repository. it serves as the primary entry point for accessing and organizing objects in analyticscreator. objects are arranged hierarchically, typically grouped by layers and functional areas such as sources, data warehouse structures, and data products. this structure reflects the logical design of the data solution and supports clear separation of concerns. key capabilities of the navigation tree include: hierarchical organization displays objects in a tree structure, allowing users to expand and collapse nodes to navigate complex models efficiently. object access and selection enables quick access to all objects, including sources, transformations, and data products. selecting an object updates the central workspace and configuration panels. object grouping supports logical grouping of objects (e.g., via object groups), helping teams organize large projects and maintain clarity. context actions right-click options allow users to create, modify, or manage objects directly within the tree. visual indicators icons and markers provide additional information about object types, states, or dependencies. the navigation tree acts as the backbone of the user interface, enabling users to efficiently navigate, manage, and maintain all components of their data solution."}
,{"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 [link:#|source] [link:#|connector types] [link:#|refresh source metadata] [link:#|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 not confirmed. diagram not applicable. visual element not confirmed. screen overview the packages feature contains the following entries: import historization persisting external script export workflow each entry represents a package-related area below the packages feature. related topics import historization persisting external script export workflow"}
,{"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. 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. function 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. its main purpose is to help users find index-related objects in the correct area of the application. access the indexes feature is available in the navigation tree of the main analyticscreator user interface. how to access navigation tree navigation tree → indexes toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the indexes feature acts as an entry point for index-related content in the navigation tree. the exact content available under this feature can depend on the project structure, configuration, and available permissions. related topics navigation tree connectors layers packages roles 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. 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. function roles are maintained with general properties, user assignments, cube-specific settings, and filter settings. the page shown includes fields for the role name and description, a user assignment area, tabs for tabular cube and multidimensional cube, a rights selection, and a dax filter area. access roles are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree roles → role → edit role; roles → add role toolbar data mart -> roles *include link* diagram not applicable visual element not confirmed screen overview the image below shows the role editor for creating or maintaining a role. add role name: name of the role. description: description of the role. users: area for assigned users. login: user login column in the assignment grid. tabular cube: tab for tabular cube settings. multidimensional cube: tab for multidimensional cube settings. rights: selection field for rights. dax filter: area for maintaining dax filters. table: table column in the dax filter grid. disable: option for disabling the filter entry. dax filter: filter expression column."}
,{"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. galaxies are used to organize larger analytical solutions by grouping related stars into a shared business context. access galaxies are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree galaxies → galaxy → right-click → edit toolbar data mart → galaxies diagram not applicable. visual element not confirmed. screen overview the galaxies feature provides access to existing galaxies and their maintenance. the confirmed edit fields are: galaxy name: name of the galaxy. description: description of the galaxy. related topics stars data mart"}
,{"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, a galaxy is a logical container for related stars or star schemas. it is used to group stars into a shared business context and organize larger analytical solutions more clearly. function the galaxies feature is used to group and maintain related stars. each galaxy acts as a container for star schemas. access galaxies are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree galaxies → galaxy → right-click → edit toolbar data mart → galaxies diagram not applicable. visual element not confirmed. screen overview the galaxies feature provides access to existing galaxies and their maintenance. edit galaxy galaxy name: name of the galaxy. description: description of the galaxy. related topics stars data mart"}
,{"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. 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. access partitions are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree partitions → partition → right-click → edit toolbar data mart → partitions diagram not applicable. visual element not confirmed. screen overview the partitions feature provides access to existing partitions and their maintenance. edit partition partition key: key used to define the partition. strategy: partition strategy, for example range or hash. slice definition: definition of the logical slice. related topics data mart facts dimensions"}
,{"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. 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. access macros are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree macros → macro → right-click → edit toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the macros feature provides access to existing macros and their maintenance. edit macro macro name: name of the macro. sql/ssis code: code definition used by the macro. placeholders: parameter placeholders such as :1 and :2. related topics transformations parameters predefined transformations"}
,{"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 *** review to add all scripts and table independent scripts division*** a object script is a script bound to a specific metadata object, such as a table or transformation. it is used to automate repeatable logic and apply object-specific actions in the data warehouse model. function the object scripts feature is used to define and maintain scripts that are attached to individual metadata objects. object scripts support object-specific execution logic and can be used for bulk updates or automated changes based on the scope of the target object. access object scripts are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree object scripts → object script → right-click → edit object scripts → object script → right-click → run toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the object scripts feature provides access to existing object scripts and their maintenance. edit object script target object: defines the metadata object to which the script is attached. execution logic: defines the logic executed by the object script. comments: stores additional information about the object script. sequencing: defines the order or execution sequence of the object script. run object script run: executes the script for the assigned target object. related topics transformations tables macros predefined transformations"}
,{"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 a filter is a reusable view definition that stores diagram filter settings such as object types, layers, schemas, or groups, so users can quickly switch between focused modeling contexts. function the filters feature is used to save, apply, and delete reusable filter views. filters help users work more efficiently in large or complex models by restoring predefined diagram views instead of manually reapplying the same filter settings each time. access filters are available as a feature in the navigation tree and as filter-related actions in the diagram interface. how to access navigation tree navigation tree → filters toolbar diagram toolbar → filter panel → store current filter diagram toolbar → filter panel → apply filter diagram toolbar → filter panel → manage filters → delete diagram available in the diagram view through the filter panel. visual element filter panel screen overview the filters feature is used to manage saved diagram filters. confirmed filter-related actions include: store current filter: saves the currently applied filter settings as a reusable filter view. apply filter: loads a previously saved filter and applies it to the current diagram view. delete filter: removes a saved filter from the repository. confirmed filter criteria include settings such as object types, layers, schemas, or groups. related topics navigation tree diagram toolbar filter panel object groups layers schemas"}
,{"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. these predefined transformations represent ready-to-use logic for recurring conversion, cleanup, formatting, and standardization tasks. access predefined transformations are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree navigation tree → predefined transformations toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the predefined transformations feature contains the following entries: anonymization binarytostr hierarchytostring numbernulltozero stringmaxto8000 stringnulltona timetodatetime trim xmltostring each entry represents a predefined transformation that can be accessed below the predefined transformations feature. 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. snapshots are used for point-in-time tracking and historization scenarios, including scd-related time tracking. access snapshots are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree snapshots → snapshot → right-click → edit toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the snapshots feature provides access to existing snapshots and their maintenance. edit snapshot name: name of the snapshot. date expression: defines the date logic used for the snapshot. calculation logic: defines the calculation logic of the snapshot. 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 a deployment is a metadata object used to define and execute how generated data warehouse artifacts are published to a target environment. function the deployments feature is used to maintain deployment settings and run deployments. deployment settings define where generated artifacts are deployed. confirmed settings include the target database and dacpac-related options. access deployments are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree deployments → deployment → right-click → edit deployments → deployment → right-click → run toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview the deployments feature provides access to existing deployment entries and their maintenance. edit / run deployment deployment settings: settings used to control the deployment. target db: target database for the deployment. dacpac options: options related to dacpac-based deployment. run: executes the deployment. related topics deployment package repository"}
,{"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 a group is a metadata object used to organize sources, tables, transformations, and other objects into reusable sets. it helps filter displayed objects and control workflow execution based on group membership. function the groups feature is used to define and maintain metadata groups. groups can be used to display only the objects belonging to a specific group and to enable or disable objects in the workflow based on their group membership. access groups are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree groups → group → right-click → edit toolbar not confirmed. diagram groups can also be used in the diagram context through object group membership and group-based filtering. visual element group dropdown screen overview the groups feature provides access to existing groups and their maintenance. edit group group name: name of the group. assigned objects: objects that belong to the group. filter settings: settings used to control group-based filtering. defined groups can be used to filter the diagram view and to control workflow behavior through group membership. related topics filters transformations object scripts deployments"}
,{"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. each model represents a logical grouping of tables and serves as a high-level container for a business-specific semantic definition. access models are available in the navigation tree of the main analyticscreator user interface. how to access navigation tree models → model → right-click → edit toolbar data mart -> models diagram not applicable. visual element not confirmed. screen overview the models feature provides access to existing models and their maintenance. list view search by name: filters the list using the model name criteria. search by description: filters models based on description text. edit view name: defines the model name. description: optional metadata describing the purpose or business context of the model. cancel: closes the editor without saving. save: stores the updated model definition in metadata. related topics data mart facts dimensions"}
,{"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 section in analyticscreator 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 rewrite everthing 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} > 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. transformation wizard — screen a (general settings) id property description 1 type specifies the transformation type (e.g., dimension, fact). 2 schema defines the schema where the transformation will be created (e.g., dwh). 3 name specifies the name of the transformation object. 4 historizing type defines the historization logic (none, snapshot, fullhist). 5 main table identifies the main source table used in the transformation. 6 create unknown member automatically creates an unknown/default record. 7 persist transformation determines if the transformation logic should be persisted. 8 persist table persists the output as a physical table. 9 persist package includes the transformation in a package for reuse. transformation wizard — screen b (table join & hist type) id property description 10 table join + hist type defines how related tables are joined and historized. 11 all n:1 direct related adds all directly related n:1 tables automatically. 12 all direct related adds all tables that have a direct relationship. 13 all n:1 related adds all indirectly related n:1 tables. 14 all related adds all related tables, both direct and indirect. 15 delete deletes selected related tables. 16 delete all removes all related tables from the list. 17 use business key references if possible uses business keys for relationships if available. 18 use hash key references if possible uses hash keys for relationships if available. 19 use only hash key references forces the use of hash key references only. 20 use only business key references forces the use of business key references only. transformation wizard — screen c (fields) id property description 21 fields specifies which fields to include (none, key fields, all fields). 22 field names defines the naming format for fields (field[n], table_field). 23 field names appearance controls letter casing (upper, lower, or no change). 24 key field names defines a pattern for key names (e.g., fk_{tablename}). 25 key fields null to zero automatically replaces null key values with zero. 26 use friendly names as column names applies user-friendly labels to column names. 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 provides a visual representation of data movement and transformation within analyticscreator. it allows users to understand how data flows from sources through the data warehouse to data products. objects are displayed as connected elements, showing dependencies and execution order across the data pipeline. this visual approach supports both development and analysis by making relationships between components immediately visible. key capabilities of the dataflow diagram include: end-to-end data flow visibility displays the flow of data from source systems through transformations to final data products. dependency visualization clearly shows upstream and downstream relationships between objects, enabling impact analysis when making changes. interactive navigation users can select elements within the diagram to access detailed configurations and related objects. logical structuring organizes transformations and processing steps in a way that reflects execution logic and data dependencies. visual clarity for complex models helps users understand large and complex data solutions by providing an intuitive graphical overview. the dataflow diagram enhances transparency and control by making data dependencies explicit, supporting both development efficiency and governance."}
,{"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 a dataflow diagram feature used to quickly locate objects by entering keywords or phrases in the search bar. function the search feature is used to find objects in the dataflow diagram more efficiently. it helps users navigate large and complex models by reducing the effort required to manually locate specific objects. access search is available in the dataflow diagram of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar not confirmed. diagram dataflow diagram → search bar visual element search bar screen overview the search feature provides a search bar for entering keywords or phrases. it is used to quickly locate objects in the current dataflow diagram context. related topics dataflow diagram filters source table transformation"}
,{"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 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. function the filters feature is used to save, apply, and delete reusable filter views in the dataflow diagram. filters help users work more efficiently in large or complex models by restoring predefined diagram views instead of manually reapplying the same filter settings each time. access filters are available in the dataflow diagram through the filter panel. how to access navigation tree not applicable. toolbar diagram toolbar → filter panel → store current filter diagram toolbar → filter panel → apply filter diagram toolbar → filter panel → manage filters → delete diagram available in the dataflow diagram through the filter panel. visual element filter panel screen overview the filters feature provides the following functions: store current filter: saves the current filtering criteria as a reusable profile. apply filter: applies a previously saved filter to the current diagram view. delete filter: removes a saved filter. confirmed filter criteria include object types, layers, schemas, and groups. related topics dataflow diagram search groups layers schemas"}
,{"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 are used to organize objects such as sources, tables, and transformations into reusable groups. they help structure the dataflow diagram and support group-based filtering and workflow control. function the object groups feature is used to assign objects to groups and work with group membership in the dataflow diagram. object groups can be used to display only the objects belonging to a specific group and to enable or disable objects in the workflow based on their group membership. access object groups are available in the dataflow diagram through the object context menu and the group dropdown in the menu bar. how to access navigation tree not applicable. toolbar not confirmed. diagram dataflow diagram → object context menu → object groups visual element group dropdown screen overview the object groups feature provides the following functions: object groups: opens the group assignment for the selected object. group dropdown: filters the diagram view to show only the objects that belong to the selected group. group membership: controls whether objects are included or excluded in workflow behavior based on their assigned group. confirmed object types mentioned in the current documentation include sources, tables, and transformations. related topics dataflow diagram filters groups source table transformation"}
,{"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 a layer is a logical architectural slice used to group metadata objects and define their build order and visibility in the model. function the layers feature in the dataflow diagram is used to structure objects according to the architectural flow of the solution. layers represent phases such as source, staging, persisted staging, transformation, data warehouse - core, or datamart. they help organize the diagram and make dependencies between objects easier to understand. access layers are available in the dataflow diagram context of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar not confirmed. diagram dataflow diagram visual element not confirmed. screen overview the layers feature represents the architectural structure shown in the dataflow diagram. confirmed layer examples include: source staging persisted staging transformation data warehouse - core datamart the diagram can show all layers together with the dependencies between the objects assigned to them. related topics dataflow diagram source table transformation filters object groups"}
,{"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 in analyticscreator, a source is a metadata object that describes external data. it defines the structure of the source data and serves as the starting point for downstream modeling in the data warehouse. function the source feature is used to represent and maintain external data structures in the model. each source belongs to a connector. a source contains columns, and references between sources can be defined. access sources are available in the dataflow diagram of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar not confirmed. diagram dataflow diagram → source → right-click → edit source visual element source screen overview the source feature provides access to the source definition. connector assignment: each source belongs to a connector. columns: a source contains column definitions. references: references between sources can be defined. edit source: opens the source definition for maintenance. related topics dataflow diagram connectors tables source references"}
,{"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 a table is a metadata object that represents a database table or view within the data warehouse. it defines the structure used for imported, historicized, persisted, and other modeled table objects. function the table feature is used to define and maintain table structures in the model. each table belongs to a schema. a table can include calculated columns, primary keys, identity columns, and indexes. relationships between tables can also be defined to support downstream transformations. access tables are available in the dataflow diagram of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar dwh → table diagram dataflow diagram → table → right-click → edit visual element table screen overview the table feature provides access to the table definition. table schema: schema where the table resides. table name: name of the table. table type: type of the table object. friendly name: optional label used for easier identification. description: documentation field for the table. calculated columns: additional columns defined by sql expressions. primary keys: key definition for the table. identity columns: identity-based column definitions. indexes: index definitions for the table. references: relationships between tables. related topics dataflow diagram source transformation table references indexes"}
,{"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 a transformation is a metadata object used to define how data is processed in the staging and warehouse layers. depending on the transformation type, it can be modeled as a automatically-generated view, a manual view, a script-based process, or an external process. function the transformation feature is used to define and maintain transformation logic in the model. transformations are used to process source data and prepare it for downstream warehouse structures. the current documentation confirms regular, manual, script, and external transformation types. access transformations are available in the dataflow diagram of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar etl → transformation diagram dataflow diagram → right-click context menu → add → transformation visual element transformation screen overview the transformation feature provides access to transformation definitions in the dataflow diagram. add transformation: creates a new transformation from the diagram context menu. regular transformation: transformation described in tabular form that results in a generated view. manual transformation: hand-created view defined manually by the user. script transformation: transformation based on sql scripts, often calling stored procedures. external transformation: transformation created outside analyticscreator, for example as an ssis package. related topics dataflow diagram source table persisting macros predefined transformations"}
,{"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 in analyticscreator, a fact is a metadata object used to model quantitative business data for analytical processing in the data warehouse and data mart. function the fact feature is used to represent and refine fact structures in the model. access facts are available in the dataflow diagram context of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar dwh → fact diagram dataflow diagram → fact visual element fact screen overview the fact feature provides access to fact objects in the dataflow diagram. fact structure: represents quantitative business data used for analysis. gui-based definition: facts are defined through the analyticscreator user interface. refinement: generated fact tables can be adjusted by removing unnecessary attributes, validating joins, and ensuring the correct grain. calendar handling: date columns can be replaced by references to a calendar dimension where required. related topics dataflow diagram dimension transformation table stars"}
,{"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 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. function the dimension feature is used to represent and refine dimension structures in the model. current analyticscreator documentation confirms that dimensions are generated as part of the warehouse model and can be configured with default predefined transformations and star assignments. access dimensions are available in the dataflow diagram context of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar dwh → dimension diagram dataflow diagram → dimension visual element dimension screen overview the dimension feature provides access to dimension objects in the dataflow diagram. generated model object: dimensions are part of the generated data warehouse model. default transformations: default predefined transformations can be selected for dimensions. stars: generated dimensions can be assigned to data mart stars. refinement: dimension structures can be refined by removing unnecessary attributes, validating joins, defining surrogate keys, and replacing date columns with calendar dimension references where needed. related topics dataflow diagram fact transformation calendar dimension predefined transformations stars"}
,{"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 a export in the dataflow diagram is the feature that allows export the data warehouse project.. function not confirmed. access mouse right-click → add → import/export definition how to access navigation tree not applicable. toolbar file → back-up and restore → load from file diagram dataflow diagram → mouse right-click → add → import/export definition visual element import screen overview add → import/export definition related topics dataflow diagram save to file load from file"}
,{"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 a historization is a metadata object used to track changes of a table or transformation over time in the data warehouse model. function the historization feature is used to historicize a table or transformation. current version analyticscreator support for scd type 1 and scd type 2, as well as ssis-based or stored procedure-based historization. it also supports empty-record handling and optional use of vault id as the primary key. :contentreference[oaicite:1]{index=1} access historization is available in the dataflow diagram context of the main analyticscreator user interface.. how to access navigation tree packages → historization toolbar etl → historizations diagram dataflow diagram → object context menu → add → historization visual element historization screen overview the historization feature is created and maintained through the historization wizard. :contentreference[oaicite:3]{index=3} 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 ssis package where the historization will be done. historizing type: selects between ssis package and stored procedure. scd type: selects between 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: allows use of hash keys instead of business keys in data vault or mixed architecture scenarios. after clicking finish, the historization is generated and the diagram is updated automatically. the generated historization package can then be selected and adjusted further if needed. :contentreference[oaicite:4]{index=4} related topics dataflow diagram transformation table historization wizard packages"}
,{"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 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. function the persisting feature is used to persist the result of a transformation into a table. access persisting is available in the dataflow diagram context of the main analyticscreator user interface. how to access navigation tree not applicable. toolbar packages → historization diagram dataflow diagram → persisted staging layer visual element persisting screen overview the persisting feature is created and maintained through the historization wizard. transformation: the name of the transformation to persist. persist table: the name of the table where the transformation will be persisted. this table is created in the same schema as the transformation. persist package: the name of the ssis package that manages the persistence process. related topics dataflow diagram transformation table packages"}
,{"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 a export in the dataflow diagram is the feature that allows export the data warehouse project.. function not confirmed. access mouse right-click → add → import/export definition how to access navigation tree not applicable. toolbar file → back-up and restore → save to file diagram dataflow diagram → mouse right-click → add → import/export definition visual element export screen overview add → import/export definition related topics dataflow diagram save to file load from file"}
,{"id":383509174509,"name":"Pages","type":"subsection","path":"/docs/reference/user-interface/pages","breadcrumb":"Reference › User Interface › Pages","description":"","searchText":"reference user interface pages pages"}
,{"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 the connector page is used to add and edit source connectors. function this page is used to maintain connector definitions. access the connector page can be opened from the navigation tree and toolbar. how to access navigation tree connectors → connector → edit connector; connectors → add connector toolbar sources → add diagram not confirmed. screen overview ac visual element: detailconnectors this page is used to add or edit a connector. related topics connectors sources"}
,{"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 the export page is used to add and edit data exports. function this page is used to maintain export definitions. access the export page can be opened from the navigation tree and diagram. how to access navigation tree packages → export → package → export → edit export toolbar not confirmed. diagram [ep] → double-click screen overview ac visual element: detailexport this page is used to add or edit an export. related topics packages export"}
,{"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 the olap hierarchy page is used to add and edit olap hierarchies. function this page is used to maintain olap hierarchy definitions. access the olap hierarchy page can be opened from the navigation tree. how to access navigation tree hierarchies → table → hierarchy → edit hierarchy toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailhierarchies this page is used to add or edit an olap hierarchy. related topics hierarchies table"}
,{"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 the historization page is used to add and edit historizations. function this page is used to maintain historization definitions. access the historization page can be opened from the navigation tree and diagram. how to access navigation tree packages → historization → package → historization → edit historization toolbar not confirmed. diagram [hp] → double-click screen overview ac visual element: detailhist this page is used to add or edit a historization. related topics packages historization"}
,{"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 the import page is used to add and edit data imports from a source. function this page is used to maintain import definitions. access the import page can be opened from the navigation tree and diagram. how to access navigation tree packages → import → package → import → edit import toolbar not confirmed. diagram [ip] → double-click screen overview ac visual element: detailimp this page is used to add or edit an import. related topics packages import"}
,{"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 the index page is used to add and edit table indexes. function this page is used to maintain index definitions. access the index page can be opened from the navigation tree. how to access navigation tree indexes → index → edit index toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailindexes this page is used to add or edit a table index. related topics indexes table"}
,{"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 the macro page is used to add and edit macros. function this page is used to maintain macro definitions. access the macro page can be opened from the navigation tree. how to access navigation tree macros → macro → edit macro toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailmacros this page is used to add or edit a macro. related topics macros"}
,{"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 the model dimension page is used to add and edit model dimensions. function this page is used to maintain model dimension definitions. access the model dimension page can be opened from the navigation tree. how to access navigation tree models → model → dimensions → dimension → edit dimension; models → model → dimensions → add dimension toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailmoddimensions this page is used to add or edit a model dimension. related topics models dimensions"}
,{"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 the model fact page is used to add and edit model facts. function this page is used to maintain model fact definitions. access the model fact page can be opened from the navigation tree. how to access navigation tree models → model → facts → fact → edit fact toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailmodfacts this page is used to add or edit a model fact. related topics models facts"}
,{"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 the table page is used to add and edit tables. function this page is used to maintain table definitions. access the table page can be opened from the navigation tree and diagram. how to access navigation tree model → layers → layer → schema → tables → table → edit table toolbar not confirmed. diagram [t] → double-click; table → double-click screen overview ac visual element: detailobjects this page is used to add or edit a table. related topics layers schemas tables"}
,{"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 the object script page is used to add and edit object scripts. function this page is used to maintain object script definitions. access the object script page can be opened from the navigation tree. how to access navigation tree object scripts → [any] → script → edit object script toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailobjectscripts this page is used to add or edit an object script. related topics object scripts scripts"}
,{"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 the package page is used to add and edit packages. function this page is used to maintain package definitions. access the package page can be opened from the navigation tree. how to access navigation tree packages → [any] → package → edit package; packages → workflow → add workflow package; packages → script → add script package; packages → external → add script package toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailpackages this page is used to add or edit a package. related topics packages workflow script external"}
,{"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 the olap partition page is used to add and edit olap partitions. function this page is used to maintain olap partition definitions. access the olap partition page can be opened from the navigation tree. how to access navigation tree partitions → partition → edit partition toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailpartitions this page is used to add or edit an olap partition. related topics partitions"}
,{"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 the persisting page is used to add and edit transformation persistings. function this page is used to maintain persisting definitions. access the persisting page can be opened from the navigation tree and diagram. how to access navigation tree packages → persisting → persisting → edit package toolbar not confirmed. diagram [pp] → double-click screen overview ac visual element: detailpers this page is used to add or edit a transformation persisting. related topics packages persisting"}
,{"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 the predefined transformation page is used to add and edit predefined transformations. function this page is used to maintain predefined transformation definitions. access the predefined transformation page can be opened from the navigation tree. how to access navigation tree predefined transformations → predefined transformation → edit predefined transformation toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailpredefinedtransformations this page is used to add or edit a predefined transformation. related topics predefined transformations"}
,{"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 the table reference page is used to add and edit table references. function this page is used to maintain table reference definitions. access the table reference page can be opened from the navigation tree. how to access navigation tree layers → layer → schema → tables → table → references → reference → edit table reference toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailreferences this page is used to add or edit a table reference. related topics layers tables references"}
,{"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 the olap role page is used to add and edit olap roles. function this page is used to maintain olap role definitions. access the olap role page can be opened from the navigation tree. how to access navigation tree roles → role → edit role toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailroles this page is used to add or edit an olap role. related topics roles"}
,{"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 the sql script page is used to add and edit sql scripts. function this page is used to maintain sql script definitions. access the sql script page can be opened from the navigation tree. how to access navigation tree scripts → [any] → script → edit script toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailscript this page is used to add or edit an sql script. related topics scripts"}
,{"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 the snapshot group page is used to add and edit snapshot groups. function this page is used to maintain snapshot group definitions. access the snapshot group page can be opened from the navigation tree. how to access navigation tree snapshots → snapshot groups → snapshot group → edit snapshot group toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailsnapshotgroup this page is used to add or edit a snapshot group. related topics snapshots snapshot groups"}
,{"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 the snapshot page is used to add and edit snapshots. function this page is used to maintain snapshot definitions. access the snapshot page can be opened from the navigation tree. how to access navigation tree snapshots → snapshot → edit snapshot toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailsnapshots this page is used to add or edit a snapshot. related topics snapshots"}
,{"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 the source page is used to add and edit sources in a connector. function this page is used to maintain source definitions. access the source page can be opened from the navigation tree and diagram. how to access navigation tree connectors → connector → sources → source → edit source toolbar not confirmed. diagram source → double-click screen overview ac visual element: detailsource this page is used to add or edit a source. related topics connectors sources"}
,{"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 the star page is used to add and edit data mart stars. function this page is used to maintain data mart star definitions. access the access path for the star page is not confirmed in the provided structure. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailstars this page is used to add or edit a data mart star. related topics data mart stars"}
,{"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 the deployment page is used to add, edit, and run deployments. function this page is used to maintain deployment definitions and run deployments. access the deployment page can be opened from the navigation tree. how to access navigation tree deployments → deployment → edit/run deployment toolbar not confirmed. diagram not confirmed. screen overview ac visual element: newssis this page is used to add, edit, or run a deployment. related topics deployments"}
,{"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 the source reference page is used to add and edit source references. function this page is used to maintain source reference definitions. access the source reference page can be opened from the navigation tree. how to access navigation tree connectors → connector → sources → source → references → reference → edit source reference toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailsrcreferences this page is used to add or edit a source reference. related topics connectors sources references"}
,{"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 the transformation page is used to add and edit transformations. function this page is used to maintain transformation definitions. access the transformation page can be opened from the navigation tree and diagram. how to access navigation tree model → layers → layer → schema → transformations → transformation → edit transformation toolbar not confirmed. diagram transformation → double-click screen overview ac visual element: detailtransformations this page is used to add or edit a transformation. related topics layers schemas transformations"}
,{"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 the users in user group page is used to add and edit users in a user group. function this page is used to maintain user assignments in a user group. access the access path for the users in user group page is not confirmed in the provided structure. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. screen overview ac visual element: detailuserroles this page is used to add or edit users in a user group. related topics user groups users"}
,{"id":383509396683,"name":"Lists","type":"subsection","path":"/docs/reference/user-interface/lists","breadcrumb":"Reference › User Interface › Lists","description":"","searchText":"reference user interface lists lists"}
,{"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 the connectors page is used to list connectors. function this page is used to list connectors. access the page can be opened from the navigation tree and toolbar. how to access navigation tree connectors->list connectors toolbar sources->connectors diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchconnectors this page is used to list connectors. related topics sources"}
,{"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 the datamart stars page is used to list datamart stars. function this page is used to list datamart stars. access the page can be opened from the toolbar. how to access navigation tree not confirmed. toolbar datamart->stars diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchstars this page is used to list datamart stars. related topics datamart stars"}
,{"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 the deploymens page is used to list deployments. function this page is used to list deployments. access the page can be opened from the navigation tree and toolbar. how to access navigation tree deployments->list deployments toolbar deployment->deployment package diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchdeployments this page is used to list deployments. related topics deployments deployment deployment package"}
,{"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 ac visual element: configencryptedstrings this page is used to list/edit encrypted strings. related topics options"}
,{"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 the exports page is used to list data exports. function this page is used to list data exports. access the page can be opened from the toolbar. how to access navigation tree not confirmed. toolbar etl->exports diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchexports this page is used to list data exports. related topics none confirmed."}
,{"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 the galaxies page is used to list and edit galaxies. function this page is used to list and maintain galaxies. access the page can be opened from the toolbar. how to access navigation tree not confirmed. toolbar data mart->galaxies diagram not confirmed. visual element not confirmed. screen overview ac visual element: configgalaxies this page is used to list/edit galaxies. related topics data mart"}
,{"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 the hierarchies page is used to list hierarchies. function this page is used to list hierarchies. access the page can be opened from the navigation tree and toolbar. how to access navigation tree hierarchies->list hierarchies toolbar data mart->hierarchies diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchhierarchies this page is used to list hierarchies. related topics data mart"}
,{"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 ac visual element: searchhist this page is used to list historizations. related topics none confirmed."}
,{"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 ac visual element: searchimports this page is used to list data imports. related topics none confirmed."}
,{"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 the indexes page is used to list table indexes. function this page is used to list table indexes. access the page can be opened from the navigation tree and toolbar. how to access navigation tree indexes->list indexes toolbar dwh->indexes diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchindexes this page is used to list table indexes. related topics none confirmed."}
,{"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 the layers page is used to list and edit layers. function this page is used to list and maintain layers. access the page can be opened from the navigation tree and toolbar. how to access navigation tree layers->layer->edit layer toolbar dwh->layers diagram not confirmed. visual element not confirmed. screen overview ac visual element: configlayers this page is used to list/edit layers. related topics none confirmed."}
,{"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 the macros page is used to list macros. function this page is used to list macros. access the page can be opened from the navigation tree and toolbar. how to access navigation tree macros->list macros toolbar dwh->macros diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchmacros this page is used to list macros. related topics none confirmed."}
,{"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 the models page is used to list and edit models. function this page is used to list and maintain models. access the page can be opened from the navigation tree and toolbar. how to access navigation tree models->list models toolbar data mart->models diagram not confirmed. visual element not confirmed. screen overview ac visual element: configmodels this page is used to list/edit models. related topics data mart"}
,{"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 the object group content page is used to list and edit obects in object groups. function this page is used to list and maintain obects in object groups. access the page can be opened from the navigation tree. how to access navigation tree groups->group->list objects toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchgroupobjects this page is used to list/edit obects in object groups. related topics groups"}
,{"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 the object scripts page is used to list object scripts. function this page is used to list object scripts. access the page can be opened from the navigation tree. how to access navigation tree object scripts->list object scripts; object scripts->[any]->list object scripts toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchobjectscript this page is used to list object scripts. related topics none confirmed."}
,{"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 the olap roles page is used to list olap roles. function this page is used to list olap roles. access the page can be opened from the navigation tree and toolbar. how to access navigation tree roles->list roles toolbar data mart->roles diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchroles this page is used to list olap roles. related topics roles data mart"}
,{"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 the packages page is used to list packages. function this page is used to list packages. access the page can be opened from the navigation tree and toolbar. how to access navigation tree packages->list packages; packages->[any]->list packages toolbar etl->packages diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchpackages this page is used to list packages. related topics none confirmed."}
,{"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 the partitions page is used to list partitions. function this page is used to list partitions. access the page can be opened from the navigation tree and toolbar. how to access navigation tree partitions->list partitions toolbar data mart->partitions diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchpartitions this page is used to list partitions. related topics data mart"}
,{"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 the predefined transformations page is used to list predefined transformations. function this page is used to list predefined transformations. access the page can be opened from the navigation tree and toolbar. how to access navigation tree predefined transformations->list predefined transformations toolbar dwh->predefined transformations diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchpredefinedtransformations this page is used to list predefined transformations. related topics none confirmed."}
,{"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 ac visual element: configschemas this page is used to list/edit schemas. related topics layers"}
,{"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 the snapshot groups page is used to list snapshot groups. function this page is used to list snapshot groups. access the page can be opened from the navigation tree. how to access navigation tree snapshots->snapshot groups->list snapshot groups toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchsnapshotgroups this page is used to list snapshot groups. related topics snapshots"}
,{"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 the snapshots page is used to list snapshots. function this page is used to list snapshots. access the page can be opened from the navigation tree and toolbar. how to access navigation tree snapshots->list snapshot toolbar etl->snapshots diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchsnapshots this page is used to list snapshots. related topics none confirmed."}
,{"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 the source references page is used to list source references. function this page is used to list source references. access the page can be opened from the navigation tree and toolbar. how to access navigation tree connectors->connector->sources->source->references->list source references toolbar sources->references diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchsrcreferences this page is used to list source references. related topics connectors sources references"}
,{"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 the sources page is used to list sources. function this page is used to list sources. access the page can be opened from the navigation tree and toolbar. how to access navigation tree connectors->connector->sources->list sources toolbar sources->sources diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchsources this page is used to list sources. related topics connectors"}
,{"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 the sql script page is used to list sql script. function this page is used to list sql script. access the page can be opened from the navigation tree and toolbar. how to access navigation tree scripts->[any]->list [type] scripts toolbar etl->scripts diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchscripts this page is used to list sql script. related topics scripts"}
,{"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 the table references page is used to list table references. function this page is used to list table references. access the page can be opened from the navigation tree and toolbar. how to access navigation tree layers->layer->schema->tables->table->references->list references toolbar dwh->references diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchreferences this page is used to list table references. related topics layers tables references"}
,{"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 ac visual element: searchobjects this page is used to list tables. related topics model layers"}
,{"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 the transformations page is used to list transformations. function this page is used to list transformations. access the page can be opened from the navigation tree and toolbar. how to access navigation tree model->layers->layer->schema->transformations->list transformations toolbar etl->transformations diagram not confirmed. visual element not confirmed. screen overview ac visual element: searchtransformations this page is used to list transformations. related topics model layers"}
,{"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 ac visual element: searchusergroups this page is used to list user groups. related topics options"}
,{"id":383509396684,"name":"Dialogs","type":"subsection","path":"/docs/reference/user-interface/dialogs","breadcrumb":"Reference › User Interface › Dialogs","description":"","searchText":"reference user interface dialogs dialogs"}
,{"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 help → about diagram not confirmed. visual element not confirmed. screen overview ac visual element: about this dialog is used for about analyticscreator (version). related topics help"}
,{"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 options → dwh settings diagram not confirmed. visual element not confirmed. screen overview ac visual element: dwhsettings this dialog is used for common dwh settings. related topics options dwh"}
,{"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 the error description dialog is used for common dialog containing errors/warnings/meessages. function this dialog supports common dialog containing errors/warnings/meessages. access the access path for the error description dialog is not confirmed in the provided structure. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: errorwindow this dialog is used for common dialog containing errors/warnings/meessages. related topics messages warnings"}
,{"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 the eula dialog is used for dialog contatinig end user licence agreement. function this dialog supports dialog contatinig end user licence agreement. access the eula dialog can be opened from the toolbar. how to access navigation tree not confirmed. toolbar help → eula diagram not confirmed. visual element not confirmed. screen overview ac visual element: eulawindow this dialog is used for dialog contatinig end user licence agreement. related topics help"}
,{"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 the input dialog dialog is used for common input dialog. function this dialog supports common input dialog. access the access path for the input dialog dialog is not confirmed in the provided structure. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: inputdialog this dialog is used for common input dialog. related topics input"}
,{"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 the input dialog with dropbox dialog is used for common input dialog with dropbox. function this dialog supports common input dialog with dropbox. access the access path for the input dialog with dropbox dialog is not confirmed in the provided structure. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: inputdialogcombo this dialog is used for common input dialog with dropbox. related topics input dialog"}
,{"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 the open/save in cloud dialog is used for dialog to load/store data in cloud. function this dialog supports dialog to load/store data in cloud. access the open/save in cloud dialog can be opened from the toolbar. how to access navigation tree not confirmed. toolbar file → load from cloud; file → save to cloud diagram not confirmed. visual element not confirmed. screen overview ac visual element: listfileswindow this dialog is used for dialog to load/store data in cloud. related topics file"}
,{"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 the preview source data dialog is used for dialog to preview source data. function this dialog supports dialog to preview source data. access the preview source data dialog can be opened from the navigation tree and diagram. how to access navigation tree connectors → connector → sources → source → preview data toolbar not confirmed. diagram source → preview data visual element not confirmed. screen overview ac visual element: preview this dialog is used for dialog to preview source data. related topics connectors sources"}
,{"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 the upgrade repository dialog is used for repository upgrade progress dialog. function this dialog supports repository upgrade progress dialog. access the access path for the upgrade repository dialog is not confirmed in the provided structure. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: publishdatabase this dialog is used for repository upgrade progress dialog. related topics repository"}
,{"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 the refresh source metadata dialog is used for dialog to update source metadata. function this dialog supports dialog to update source metadata. access the refresh source metadata dialog can be opened from the navigation tree and diagram. how to access navigation tree connectors → connector → refresh used sources; connectors → connector → refresh all sources; connectors → connector → sources → source → refresh structure toolbar not confirmed. diagram source → refresh source visual element not confirmed. screen overview ac visual element: refreshsources this dialog is used for dialog to update source metadata. related topics connectors sources"}
,{"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 the search dialog is used for common search dialog. function this dialog supports common search dialog. access the search dialog can be opened from the toolbar and diagram. how to access navigation tree not confirmed. toolbar find on diagram diagram ctrl-f visual element not confirmed. screen overview ac visual element: searchdialog this dialog is used for common search dialog. related topics dataflow diagram"}
,{"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 the tumbnail diagram dialog is used in the analyticscreator user interface. function this dialog supports the related dialog action. access the tumbnail diagram dialog can be opened from the diagram. how to access navigation tree not confirmed. toolbar not confirmed. diagram diagram → show tumbnail visual element not confirmed. screen overview ac visual element: smalldiagram no additional description is confirmed in the provided structure. related topics dataflow diagram"}
,{"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 the source constraints dialog is used for information about source constraints. function this dialog supports information about source constraints. access the source constraints dialog can be opened from the visual element. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element {detailsource} → constraints screen overview ac visual element: sourceconstraint this dialog is used for information about source constraints. related topics sources"}
,{"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 the synchronize dwh dialog is used for dialog to synchronize dwh. function this dialog supports dialog to synchronize dwh. access the synchronize dwh dialog can be opened from the toolbar. how to access navigation tree not confirmed. toolbar file → synchronize dwh diagram not confirmed. visual element not confirmed. screen overview ac visual element: synchronise this dialog is used for dialog to synchronize dwh. related topics file dwh"}
,{"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 the interface settings dialog is used for analyticscreator interface settings. function this dialog supports analyticscreator interface settings. access the interface settings dialog can be opened from the toolbar. how to access navigation tree not confirmed. toolbar options → interface diagram not confirmed. visual element not confirmed. screen overview ac visual element: acsettings this dialog is used for analyticscreator interface settings. related topics options"}
,{"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 the login dialog is used for login dialog on start of analyticscreator. function this dialog supports login dialog on start of analyticscreator. access the access path for the login dialog is not confirmed in the provided structure. how to access navigation tree not confirmed. toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: loginwindow this dialog is used for login dialog on start of analyticscreator. related topics analyticscreator"}
,{"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 the object groups dialog is used for information about the groups of specific object. function this dialog supports information about the groups of specific object. access the object groups dialog can be opened from the diagram. how to access navigation tree not confirmed. toolbar not confirmed. diagram any object → object groups visual element not confirmed. screen overview ac visual element: searchgroups this dialog is used for information about the groups of specific object. related topics groups"}
,{"id":383509340360,"name":"Wizards","type":"subsection","path":"/docs/reference/user-interface/wizards","breadcrumb":"Reference › User Interface › Wizards","description":"","searchText":"reference user interface wizards dwh wizard export wizard export to visio export to word historization wizard import wizard new calendar transformation new snapshot dimension new time transformation persisting wizard run object script source wizard transformation wizard vault wizard"}
,{"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 the create calendar dimension wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the toolbar and diagram. how to access navigation tree not confirmed. toolbar etl → calendar dimension diagram diagram → add → calendar dimension visual element not confirmed. screen overview ac visual element: assistent_newdatetrans this wizard is used for create calendar dimension. related topics etl calendar dimension dataflow diagram"}
,{"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 the create datavault object wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree. how to access navigation tree model → layers → layer → schema → tables → table → add vault toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: assistent_newvault this wizard is used for create datavault object. related topics model layers tables datavault"}
,{"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 the create export wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree and diagram. how to access navigation tree packages → export → add export package toolbar not confirmed. diagram table/transformation → add → export visual element not confirmed. screen overview ac visual element: assistent_newexport this wizard is used for create export. related topics packages export table transformation"}
,{"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 the create historization wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree and diagram. how to access navigation tree packages → historization → add historization package toolbar not confirmed. diagram table/transformation → add → historization visual element not confirmed. screen overview ac visual element: assistent_newhist this wizard is used for create historization. related topics packages historization table transformation"}
,{"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 the create import wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree and diagram. how to access navigation tree packages → import → add import package toolbar not confirmed. diagram source → add → import visual element not confirmed. screen overview ac visual element: assistent_newimp this wizard is used for create import. related topics packages import 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 the create snapshot dimension wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the toolbar and diagram. how to access navigation tree not confirmed. toolbar etl → snapshot dimension diagram diagram → add → snapshot dimension visual element not confirmed. screen overview ac visual element: assistent_newsnapshottrans this wizard is used for create snapshot dimension. related topics etl snapshot dimension dataflow diagram"}
,{"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 the create source wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree. how to access navigation tree connectors → connector → sources → read source from connector toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: assistent_newsource this wizard is used for create source. related topics connectors sources"}
,{"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 the create time dimension wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the toolbar and diagram. how to access navigation tree not confirmed. toolbar etl → time dimension diagram diagram → add → time dimension visual element not confirmed. screen overview ac visual element: assistent_newtimetrans this wizard is used for create time dimension. related topics etl time dimension dataflow diagram"}
,{"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 the create transformation wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree, toolbar, and diagram. how to access navigation tree model → layers → layer → schema → transformations → add transformation toolbar etl → new transformation diagram diagram → add → transformation visual element not confirmed. screen overview ac visual element: assistent_newtransformation this wizard is used for create transformation. related topics model layers transformations etl dataflow diagram"}
,{"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 wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree and toolbar. how to access navigation tree connectors → connector → dwh wizard toolbar file → dwh wizard diagram not confirmed. visual element not confirmed. screen overview ac visual element: assistent_newdwh this wizard is used for dwh wizard. related topics connectors dwh"}
,{"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 the hash keys wizard is used to create/refresh hash keys and hash key relationship. function this wizard is used to create/refresh hash keys and hash key relationship. access this wizard can be opened from the diagram. how to access navigation tree not confirmed. toolbar not confirmed. diagram diagram → add/refresh hash keys visual element not confirmed. screen overview ac visual element: assistent_hash this wizard is used for hash keys. related topics dataflow diagram hash keys"}
,{"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 the persist transformation wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree and diagram. how to access navigation tree packages → pertisting → add pertisting package toolbar not confirmed. diagram transformation → add → persisting visual element not confirmed. screen overview ac visual element: assistent_newpers this wizard is used for persist transformation. related topics packages persisting transformation"}
,{"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 the run object script wizard is used in analyticscreator. function this wizard is used for the action indicated by its topic. access this wizard can be opened from the navigation tree. how to access navigation tree any object → run script → script; object scripts → table-independent scripts → run object script toolbar not confirmed. diagram not confirmed. visual element not confirmed. screen overview ac visual element: assistentrunscript this wizard is used for run object script. related topics object scripts scripts"}
,{"id":383461259455,"name":"Entity types","type":"section","path":"/docs/reference/entity-types","breadcrumb":"Reference › Entity types","description":"","searchText":"reference entity types entity types"}
,{"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"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the mssql connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the oracle connector type. related topics connector types connector"}
,{"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 this page describes the excel connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the csv connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the oledb connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the sap connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the odbc connector type. related topics connector types connector"}
,{"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 this page describes the direct connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the oledb.net connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the azure blob connector type. related topics connector types connector"}
,{"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 not confirmed. toolbar not confirmed. diagram not applicable. visual element not confirmed. screen overview this page describes the odata connector type. related topics connector types connector"}
,{"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"}
,{"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 a source type in analyticscreator. function this source type is used to classify sources of type table. access this source type belongs to the source 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 table source type. related topics source types source"}
,{"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 a source type in analyticscreator. function this source type is used to classify sources of type query. access this source type belongs to the source 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 query source type. related topics source types source"}
,{"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 a source type in analyticscreator. function this source type is used to classify sources of type sap_deltaq. access this source type belongs to the source 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 sap_deltaq source type. related topics source types source"}
,{"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 a source type in analyticscreator. function this source type is used to classify sources of type sap_odp. access this source type belongs to the source 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 sap_odp source type. related topics source types source"}
,{"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 a source type in analyticscreator. function this source type is used to classify sources of type view. access this source type belongs to the source 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 view source type. related topics source types source"}
,{"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"}
,{"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 a table type in analyticscreator. function this table type is used to classify tables of type import table. access this table type belongs to the table 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 import table table type. related topics table types table"}
,{"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 a table type in analyticscreator. function this table type is used to classify tables of type historizised table. access this table type belongs to the table 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 historizised table table type. related topics table types table"}
,{"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 a table type in analyticscreator. function this table type is used to classify tables of type persisting table. access this table type belongs to the table 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 persisting table table type. related topics table types 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 a table type in analyticscreator. function this table type is used to classify tables of type dimension table. access this table type belongs to the table 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 dimension table table type. related topics table types table"}
,{"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 a table type in analyticscreator. function this table type is used to classify tables of type externally filled table. access this table type belongs to the table 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 externally filled table table type. related topics table types table"}
,{"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 a table type in analyticscreator. function this table type is used to classify tables of type fact table. access this table type belongs to the table 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 fact table table type. related topics table types table"}
,{"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 in analyticscreator. function this table type is used to classify tables of type datavault hub. access this table type belongs to the table 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 datavault hub table type. related topics table types 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 in analyticscreator. function this table type is used to classify tables of type datavault link. access this table type belongs to the table 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 datavault link table type. related topics table types 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 in analyticscreator. function this table type is used to classify tables of type datavault satellite. access this table type belongs to the table 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 datavault satellite table type. related topics table types 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"}
,{"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 a transformation type in analyticscreator. function this transformation type is used to classify transformations of type regular transformation. access this transformation type belongs to the transformation 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 regular transformation transformation type. related topics transformation types 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 a transformation type in analyticscreator. function this transformation type is used to classify transformations of type manual transformation. access this transformation type belongs to the transformation 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 manual transformation transformation type. related topics transformation types 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 a transformation type in analyticscreator. function this transformation type is used to classify transformations of type script transformation. access this transformation type belongs to the transformation 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 script transformation transformation type. related topics transformation types 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 a transformation type in analyticscreator. function this transformation type is used to classify transformations of type direct-connector transformation. access this transformation type belongs to the transformation 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 direct-connector transformation transformation type. related topics transformation types 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 a transformation type in analyticscreator. function this transformation type is used to classify transformations of type datamart transformation. access this transformation type belongs to the transformation 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 datamart transformation transformation type. related topics transformation types 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 a transformation type in analyticscreator. function this transformation type is used to classify transformations of type union transformation. access this transformation type belongs to the transformation 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 union transformation transformation type. related topics transformation types 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 a transformation type in analyticscreator. function this transformation type is used to classify transformations of type external transformation. access this transformation type belongs to the transformation 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 external transformation transformation type. related topics transformation types 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"}
,{"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 this transformation historization type is used to classify historization behavior of type fullhist. access this transformation historization type belongs to the transformation historization 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 fullhist transformation historization type. related topics transformation historization types transformation"}
,{"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 this transformation historization type is used to classify historization behavior of type snapshot. access this transformation historization type belongs to the transformation historization 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 snapshot transformation historization type. related topics transformation historization types transformation"}
,{"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 this transformation historization type is used to classify historization behavior of type snapshothist. access this transformation historization type belongs to the transformation historization 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 snapshothist transformation historization type. related topics transformation historization types transformation"}
,{"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 this transformation historization type is used to classify historization behavior of type actualonly. access this transformation historization type belongs to the transformation historization 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 actualonly transformation historization type. related topics transformation historization types transformation"}
,{"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 this transformation historization type is used to classify historization behavior of type none. access this transformation historization type belongs to the transformation historization 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 none transformation historization type. related topics transformation historization types transformation"}
,{"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"}
,{"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 in analyticscreator. function this join historization type is used to classify join historization behavior of type none. access this join historization type belongs to the join historization 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 none join historization type. related topics join historization types transformation"}
,{"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 in analyticscreator. function this join historization type is used to classify join historization behavior of type actual. access this join historization type belongs to the join historization 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 actual join historization type. related topics join historization types transformation"}
,{"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 in analyticscreator. function this join historization type is used to classify join historization behavior of type full. access this join historization type belongs to the join historization 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 full join historization type. related topics join historization types transformation"}
,{"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 in analyticscreator. function this join historization type is used to classify join historization behavior of type historical_from. access this join historization type belongs to the join historization 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 historical_from join historization type. related topics join historization types transformation"}
,{"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 in analyticscreator. function this join historization type is used to classify join historization behavior of type historical_to. access this join historization type belongs to the join historization 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 historical_to join historization type. related topics join historization types transformation"}
,{"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"}
,{"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 in analyticscreator. function this package type is used to classify packages of type import. access this package type belongs to the package 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 import package type. related topics package types package"}
,{"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 in analyticscreator. function this package type is used to classify packages of type historization. access this package type belongs to the package 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 historization package type. related topics package types package"}
,{"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 in analyticscreator. function this package type is used to classify packages of type persisting. access this package type belongs to the package 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 persisting package type. related topics package types package"}
,{"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 in analyticscreator. function this package type is used to classify packages of type workflow. access this package type belongs to the package 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 workflow package type. related topics package types package"}
,{"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 in analyticscreator. function this package type is used to classify packages of type script. access this package type belongs to the package 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 script package type. related topics package types package"}
,{"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 in analyticscreator. function this package type is used to classify packages of type exports. access this package type belongs to the package 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 exports package type. related topics package types package"}
,{"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 in analyticscreator. function this package type is used to classify packages of type external. access this package type belongs to the package 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 external package type. related topics package types package"}
,{"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"}
,{"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. function this sql script type is used to classify sql scripts of type pre-creation. access this sql script type belongs to the sql script 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 pre-creation sql script type. related topics sql script types sql script"}
,{"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. function this sql script type is used to classify sql scripts of type post-creation. access this sql script type belongs to the sql script 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 post-creation sql script type. related topics sql script types sql script"}
,{"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. function this sql script type is used to classify sql scripts of type pre-workflow. access this sql script type belongs to the sql script 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 pre-workflow sql script type. related topics sql script types sql script"}
,{"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. function this sql script type is used to classify sql scripts of type post-workflow. access this sql script type belongs to the sql script 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 post-workflow sql script type. related topics sql script types sql script"}
,{"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. function this sql script type is used to classify sql scripts of type pre-deployment. access this sql script type belongs to the sql script 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 pre-deployment sql script type. related topics sql script types sql script"}
,{"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. function this sql script type is used to classify sql scripts of type post-deployment. access this sql script type belongs to the sql script 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 post-deployment sql script type. related topics sql script types sql script"}
,{"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. function this sql script type is used to classify sql scripts of type repository extension. access this sql script type belongs to the sql script 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 repository extension sql script type. related topics sql script types sql script"}
,{"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"}
,{"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 a schema type in analyticscreator. function this schema type is used to classify schemas of type staging. access this schema type belongs to the schema 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 staging schema type. related topics schema types schema"}
,{"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 a schema type in analyticscreator. function this schema type is used to classify schemas of type persisted staging. access this schema type belongs to the schema 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 persisted staging schema type. related topics schema types schema"}
,{"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 a schema type in analyticscreator. function this schema type is used to classify schemas of type transformation. access this schema type belongs to the schema 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 transformation schema type. related topics schema types schema"}
,{"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 a schema type in analyticscreator. function this schema type is used to classify schemas of type core. access this schema type belongs to the schema 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 core schema type. related topics schema types schema"}
,{"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 a schema type in analyticscreator. function this schema type is used to classify schemas of type datamart. access this schema type belongs to the schema 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 datamart schema type. related topics schema types schema"}
,{"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":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":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 technical configuration parameters"}
,{"id":388515715280,"name":"AC_LOG","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-ac-log","breadcrumb":"Reference › Parameters › Technical configuration parameters › AC_LOG","description":"","searchText":"reference parameters technical configuration parameters ac_log overview ac_log is a parameter used to control logging behavior during deployment and processing. function this parameter controls the logging level of deployment and processing. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the ac_log parameter. documented values: 0 = no log 1 = basic log related topics parameters technical configuration parameters"}
,{"id":388515715281,"name":"DEPLOYMENT_CREATE_SUBDIRECTORY","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-deployment-create-subdirectory","breadcrumb":"Reference › Parameters › Technical configuration parameters › DEPLOYMENT_CREATE_SUBDIRECTORY","description":"","searchText":"reference parameters technical configuration parameters deployment_create_subdirectory overview deployment_create_subdirectory is a parameter used to control whether a subdirectory is created for each generated deployment package. function this parameter controls whether a subdirectory is created for every generated deployment package. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the deployment_create_subdirectory parameter. documented values: 0 = no 1 = yes related topics parameters technical configuration parameters"}
,{"id":388515715282,"name":"DIAGRAM_NAME_PATTERN","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-diagram-name-pattern","breadcrumb":"Reference › Parameters › Technical configuration parameters › DIAGRAM_NAME_PATTERN","description":"","searchText":"reference parameters technical configuration parameters diagram_name_pattern overview diagram_name_pattern is a parameter used to define the object name shown in diagrams. function this parameter controls the naming pattern used for object names in diagrams. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the diagram_name_pattern parameter. supported placeholders include: {name} {friendly name} {fullfriendlyname} {id} {cr} documented default: {fullfriendlyname} related topics parameters technical configuration parameters"}
,{"id":388515715283,"name":"DWH_METADATA_IN_EXTENDED_PROPERTIES","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-dwh-metadata-in-extended-properties","breadcrumb":"Reference › Parameters › Technical configuration parameters › DWH_METADATA_IN_EXTENDED_PROPERTIES","description":"","searchText":"reference parameters technical configuration parameters dwh_metadata_in_extended_properties overview dwh_metadata_in_extended_properties is a parameter in analyticscreator. function detailed behavior is not confirmed in the provided source. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the dwh_metadata_in_extended_properties parameter. the parameter name is confirmed. detailed parameter behavior is not confirmed. related topics parameters technical configuration parameters"}
,{"id":388515715284,"name":"HIST_PROC_USE_HASH_JOIN","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-hist-proc-use-hash-join","breadcrumb":"Reference › Parameters › Technical configuration parameters › HIST_PROC_USE_HASH_JOIN","description":"","searchText":"reference parameters technical configuration parameters hist_proc_use_hash_join overview hist_proc_use_hash_join is a parameter in analyticscreator. function detailed behavior is not confirmed in the provided source. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the hist_proc_use_hash_join parameter. the parameter name is confirmed. detailed parameter behavior is not confirmed. related topics parameters technical configuration parameters"}
,{"id":388515715285,"name":"OLEDBPROVIDER_SQLSERVER","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-oledbprovider-sqlserver","breadcrumb":"Reference › Parameters › Technical configuration parameters › OLEDBPROVIDER_SQLSERVER","description":"","searchText":"reference parameters technical configuration parameters oledbprovider_sqlserver overview oledbprovider_sqlserver is a parameter used to define the oledb provider for sql server. function this parameter defines the oledb provider for sql server. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the oledbprovider_sqlserver parameter. the parameter defines the sql server oledb provider. related topics parameters technical configuration parameters"}
,{"id":388515715286,"name":"PERS_DEFAULT_PARTSWITCH","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-pers-default-partswitch","breadcrumb":"Reference › Parameters › Technical configuration parameters › PERS_DEFAULT_PARTSWITCH","description":"","searchText":"reference parameters technical configuration parameters pers_default_partswitch overview pers_default_partswitch is a parameter in analyticscreator. function detailed behavior is not confirmed in the provided source. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the pers_default_partswitch parameter. the parameter name is confirmed. detailed parameter behavior is not confirmed. related topics parameters technical configuration parameters"}
,{"id":388515715287,"name":"PROJECT_RESTRICT_FILEPATH_LENGTH","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-project-restrict-filepath-length","breadcrumb":"Reference › Parameters › Technical configuration parameters › PROJECT_RESTRICT_FILEPATH_LENGTH","description":"","searchText":"reference parameters technical configuration parameters project_restrict_filepath_length overview project_restrict_filepath_length is a parameter in analyticscreator. function detailed behavior is not confirmed in the provided source. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the project_restrict_filepath_length parameter. the parameter name is confirmed. detailed parameter behavior is not confirmed. related topics parameters technical configuration parameters"}
,{"id":388515715288,"name":"TABLE_COMPRESSION_TYPE","type":"topic","path":"/docs/reference/parameters/parameters-technical-configuration-parameters/parameters-technical-configuration-parameters-table-compression-type","breadcrumb":"Reference › Parameters › Technical configuration parameters › TABLE_COMPRESSION_TYPE","description":"","searchText":"reference parameters technical configuration parameters table_compression_type overview table_compression_type is a parameter used to define the default table compression type. function this parameter defines the default table compression type. access this parameter belongs to the technical configuration parameters section in analyticscreator. how to access navigation tree not applicable. toolbar options → parameter diagram not applicable. visual element not confirmed. screen overview this page describes the table_compression_type parameter. documented values: 1 = none 2 = page 3 = raw related topics parameters technical configuration parameters"}
,{"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."}
]
