Inforiver
EDITable
EDITable
  • Introduction to EDITable
    • Why EDITable?
    • Supported Database Connections
  • Get Started
    • EDITable Pre-requisites
      • Admin consent for EDITable's Entra ID
        • Basic consent
        • Full admin consent
    • Install EDITable
    • Add EDITable visual
  • Getting Data into EDITable
    • Connect to Data
      • Get data
      • Assign fields
      • Configuration Steps
        • Configure source
        • Configure Columns
        • Configure Type 2 SCDs (Optional)
    • Create a Table
      • Create From Scratch
      • Use Existing Table
      • Import Data
  • Working with EDITable
    • EDITable interface
    • Manage Columns
      • General
      • Constraints
      • Lookup and Relation
      • Display
      • Import/Export Configuration
      • Add Database Column
      • Insert Column
    • Column Access Control
    • Row Identification
    • Table Operations (Insert/Update/Delete)
      • Edit data
      • Bulk Edit
      • Find and Replace
      • Insert rows
      • Insert Column
      • Import rows
      • Delete rows
      • Duplicate rows
      • Copy rows
      • Preview Changes
      • Reset Changes
    • Explore data
      • Search and filter
      • Sort and reorder
      • Show/Hide columns
      • Pin columns
      • Group Rows By
      • Summarize Column
    • Basic formatting
    • Conditional Formatting
  • Row Access Control
  • Approval Workflow
    • Review Changes - Workflow process
  • Type 2 SCDs
    • Configuring Type 2 SCDs in EDITable
  • Audit logs
  • Webhook
  • Display Settings
  • Commenting and Collaboration
    • Assign users & task status
    • View all comments & track changes
    • Comment Settings
  • Admin Portal & EDITable Console
    • Tables
    • Transaction Logs
    • Insights (Metrics)
    • Utility
      • Download Report
      • Pipeline
        • Power BI & EDITable deployment pipelines
        • Deployment in different destinations
        • Trigger deployment pipeline from external applications
        • Logs & other pipeline options
    • Manage Profile
    • Admin Portal
      • User Management
      • Settings
        • General Settings
        • Writeback Settings
          • Settings
          • EDITable managed DB
        • API token
    • Onboarding Actions
  • Formula and Functions
    • Conditional statements
      • IF
      • IFNA
      • SWITCH
    • Logical functions
      • AND
      • IN
      • ISBLANK
      • ISEMPTY
      • ISNUMBER
      • NOT
      • OR
      • XOR
    • Math functions
      • ABS
      • AVERAGE
      • AVERAGEIF
      • AVERAGEEXNEG
      • AVERAGEEXZERO
      • AVERAGEEXZERONEG
      • CEILING
      • COUNT
      • COUNTIF
      • DIVIDE
      • EVEN
      • EXP
      • FLOOR
      • LOG
      • MAX
      • MIN
      • PCT
      • POWER
    • Text formatting functions
    • Date functions
      • DATE
      • DATE.FORMAT
    • Other operators
  • Keyboard Shortcuts
  • Release Notes
    • EDITable - v1.7.5
    • EDITable - v1.7
    • EDITable - v1.6.5
    • EDITable - v1.6
Powered by GitBook
On this page
  • 1. Power BI Deployment Pipelines
  • 2. EDITable Deployment Pipelines
  • 3. Pipeline FAQs
  1. Admin Portal & EDITable Console
  2. Utility

Pipeline

PreviousDownload ReportNextPower BI & EDITable deployment pipelines

Last updated 3 months ago

Let's explore how EDITable reports can be deployed using PowerBI and EDITable deployment pipelines. Pipelines are useful when you need to deploy EDITable visuals in stages across different environments, such as development, testing, and production.

1. Power BI Deployment Pipelines

PowerBI deployment pipelines enable creators to develop and test Power BI content in the Power BI service before the content is shared with end users. The tool is designed as a pipeline with multiple stages, for example, development, test, QA, and production.

2. EDITable Deployment Pipelines

EDITable's deployment pipelines work alongside Power BI pipelines, allowing you to deploy EDITable reports in stages.

With EDITable's deployment pipelines, you can:

  • Maintain streamlined version control for EDITable reports.

  • Ensure the report's column configurations, SCDs, and row identification are preserved across different environments.

  • Deploy your EDITable reports (and thus the tables) from one data destination to another while retaining their configurations.

  • Avoid duplicate visuals that often occur when manually deploying a visual from one workspace to another.

  • Trigger report deployments from external applications using an API endpoint.

We will now look at the steps to deploy an EDITable visual across different environments and demonstrate the capabilities in the following sections.

3. Pipeline FAQs

  1. Why do I need to deploy an editable pipeline? Aren't Power BI deployment pipelines sufficient?

Power BI pipelines ensure that your deployed reports carry all formatting additions and visual updates to the next stages. Using EDITable pipelines guarantees that your EDITable visuals are deployed along with any column configuration updates, SCDs, and row identifications.

  1. What are duplicate visuals? How does deploying an EDITable pipeline avoid them?

Duplicate visuals share the same visual IDs. The visual ID of an EDITable visual can be obtained by clicking on the EDITable logo as shown below:

  • When you manually copy the report from one workspace to another, say from 'Dev' to 'Test', the visuals are duplicated.

  • Duplicate visuals use the same backend cache. Changes made to one visual will have an effect on both. To achieve optimal version control and production deployment, it is necessary to detach the visuals and remove their dependencies.

  • When you use pipelines to deploy the visuals, they are detached from one another.

  • The deployed visual in the new environment gets a new and unique visual ID, and all other formatting, configurations, etc. are carried forward.

  1. Can I deploy the visual to a different data destination during the testing, QA, or production stages?

EDITable pipeline allows you to select your preferred data destination to deploy your visual at any stage. Initially, create EDITable visuals in the required destinations under the same schema with the same table and column names, and then use deployment pipelines to move the updates and additions across stages.

Read more on PowerBI Deployment Pipelines.
Visual ID