PowerTable

Manage master data and build table apps with PowerTable

PowerTable is a no-code product for building writeback-enabled table apps on Microsoft Fabric and other modern data platforms. It allows users to view, edit, and update data directly in a table interface and write the changes back to the underlying data source. You can use PowerTable to build secure, governed table apps that write directly to your operational and analytical data, without creating new data silos. Use PowerTable to create operational apps for planning, data collection, and workflow scenarios without writing code.

What is PowerTable?

PowerTable lets business users build no-code, writeback-enabled table apps on top of modern OLTP and OLAP platforms, such as Microsoft Fabric. A PowerTable app connects live to your underlying tables or semantic models, so you can read and write data without copying it into a separate store.

Key capabilities:

• Build table apps that connect live to your data platform.

• Consume semantic models and capture writeback data.

• Configure layouts and views for different personas.

• Apply row- and column-level access control.

• Track changes through audit logs.

• Route changes through approval flows.

• Automate recurring actions by using schedules.

• Model SCD type 2 and type 3 changes.

• Design master–detail experiences and forms.

Why use PowerTable?

Use PowerTable when you want business users to manage structured data directly in your data platform while IT retains control of security and governance.

Benefits:

• Eliminate spreadsheet apps. Replace ad‑hoc lists and trackers with governed, multiuser table apps.

• Avoid data silos. Keep data in your existing platform; PowerTable reads and writes to the same tables.

• Accelerate change. Business teams can change layouts, rules, and workflows without code.

• Improve auditability. Every change is tracked and can be reviewed or rolled back.

• Standardize processes. Approval flows and automations make processes repeatable and compliant.

---

---

Create a table app

Overview

A table app is the core building block in PowerTable. It provides a grid‑like interface that reads and writes data to a backing table or semantic model. For an MVP, you typically start with a single table app that captures one business entity, such as Products or Projects.

How to create a table app

1. Create a new app

2. In the PowerTable portal, go to your workspace.

3. Select New app.

4. Enter a name and optional description for the app.

5. Select Create.

6. Connect to a data source

7. In the app designer, select Data source.

8. Choose your platform (for example, Microsoft Fabric).

9. Select the workspace, database, and table or semantic model you want to use.

10. Confirm the connection.

11. Map columns

12. PowerTable reads the schema from the source.

13. Review the detected columns.

14. For each column, configure: - Display name. - Data type (text, number, date, Boolean, lookup, and so on). - Required or optional. - Default values.

15. Save your changes.

16. Publish the app

17. Select Save.

18. Select Publish to make the app available to users.

---

Configure layout views

Overview

Layout views define how users see and interact with the data. PowerTable supports different view types so that you can tailor the experience to each persona or task.

Common view types include:

• Grid view. A spreadsheet-like table for bulk review and inline editing.

• Form view. A record‑centric layout optimized for data entry.

• Detail view. A read‑only layout for drilling into a single record.

• Master–detail view. A composite layout that shows a parent record and related child records.

How to create and configure views

1. Open the app designer

2. From your app, select Edit.

3. Add a grid view

4. In the Views pane, select Add view > Grid.

5. Choose the columns to show.

6. Drag columns to reorder them.

7. Configure sorting, filtering, and grouping as needed.

8. Save the grid view.

9. Add a form view

10. Select Add view > Form.

11. Choose whether the form is used for Create, Edit, or View operations.

12. Arrange fields into sections and columns.

13. Configure field‑level properties: - Required - Read‑only - Default values - Help text

14. Save the form.

15. Add other views as needed

    • For detail-only pages, select Add view > Detail and configure display‑only fields.

    • For dashboards or composite experiences, combine views in a master–detail layout (see the “Master–detail view” section).

---

Configure access control

Overview

Access control determines who can see and update data in your app. In an MVP, you typically configure:

• App‑level access: who can open the app.

• Role‑based permissions: who can view, edit, approve, or administer.

• Data‑level rules: optional filters that restrict which records a role can access.

PowerTable integrates with your existing identity provider so that you can assign permissions to users and groups.

How to configure access control

1. Define roles

2. In the app designer, go to Security or Access control.

3. Create roles such as: - App admin - Contributor - Viewer - Approver

4. For each role, define allowed actions (view, create, edit, delete, approve).

5. Assign users and groups

6. For each role, select Add user or group.

7. Search for the account or group from your identity provider.

8. Assign the role.

9. Configure data‑level rules (optional)

10. In the Row‑level security section, define filters per role.

11. For example, restrict Contributors to records where Region = user.Region.

12. Save your rules.

13. Test access

14. Use the Preview as role option to test each role.

15. Verify that users can only see and perform the actions you intend.

---

Track changes with audit logs

Overview

Audit logs record who changed what and when. They help you answer questions such as:

• Who created or updated a record?

• What was the previous value?

• When did a change occur?

For an MVP, enable audit logging on key tables so that you have traceability from day one.

How to enable and use audit logs

1. Enable auditing

2. In the app designer, go to Audit and compliance.

3. Turn on Audit changes for the app or specific tables.

4. Choose the events to record: - Create - Update - Delete

5. Review audit entries

6. From a record, select View history or Audit log.

7. Review changes by user, timestamp, and field.

8. Use filters to narrow the list to a date range or user.

9. Export or report on audit data

10. If supported, export audit logs to your data platform.

11. Use your analytics tools to build reports or dashboards on changes.

---

Build an approval flow

Overview

Approval flows route changes to designated approvers before they are committed or become effective in downstream processes. In PowerTable, you can define approval rules at the app or table level.

An MVP approval flow typically:

• Triggers when a record is created or edited.

• Routes the change to one or more approvers.

• Updates the record’s status based on the outcome.

How to build an approval flow

1. Define approval stages

2. In the app designer, go to Workflow > Approvals.

3. Add stages such as: - Submitted - Reviewed - Approved - Rejected

4. Configure entry conditions

5. For each stage, define when a record enters the stage, for example: - When Status = "Submitted". - When a particular field is changed.

6. Assign approvers

7. For each stage, assign: - A specific user. - A role (for example, Approver). - A dynamic value, such as a manager field.

8. Configure outcomes

9. Set outcomes such as Approve and Reject.

10. Map each outcome to: - A new status value. - Optional follow‑up actions (for example, updating fields or triggering an automation).

11. Test the flow

12. Create a test record and submit it for approval.

13. Confirm that approvers receive the request and that the record status changes as expected.

[!TIP] Keep the first version of your approval flow simple. You can add conditional routing and additional stages after you validate the basic process.

---

Automate processes with scheduling

Overview

Automations let you run repeatable actions on a schedule so that users don’t need to perform them manually. For an MVP, common automations include:

• Refreshing or recalculating derived fields.

• Closing or archiving old records.

• Sending reminders based on due dates.

How to create a scheduled automation

1. Create an automation

2. In the app designer, go to Automation.

3. Select New automation.

4. Choose Scheduled as the trigger type.

5. Configure the schedule

6. Choose the frequency: - Hourly - Daily - Weekly - Monthly

7. Set the start date and time.

8. Define the time zone.

9. Define the action

10. Choose an action type, such as: - Update records. - Insert records. - Run a stored procedure or SQL script (if available).

11. Define the filter for records to process.

12. Configure field updates or parameters.

13. Enable and monitor

14. Turn on the automation.

15. Monitor run history to confirm that jobs complete successfully and process the expected records.

---

Model SCD type 2 and type 3 changes

Overview

Many business entities are slowly changing dimensions (SCDs). PowerTable helps you manage historical and current values directly in your data platform.

• SCD type 2 keeps full history by creating a new row for each change and marking previous rows as inactive.

• SCD type 3 stores the current and previous value in the same row.

You can use PowerTable forms, validations, and automations to enforce these patterns.

How to implement SCD type 2

1. Design the table schema

   • Add keys and metadata columns, such as:

     • BusinessKey

     • SurrogateKey

     • EffectiveFrom

     • EffectiveTo

     • IsCurrent

2. Configure the app

3. In the app designer, map these columns to fields.

4. Make BusinessKey and IsCurrent visible to admins and optional or hidden for business users as needed.

5. Create a form for changes

6. Use a form view for edits.

7. Instead of updating the current row in place, configure an automation or workflow step that: - Sets IsCurrent = 0 and EffectiveTo to the change timestamp for the existing row. - Inserts a new row with updated attributes, IsCurrent = 1, and EffectiveFrom set to the change timestamp.

8. Use views for current vs history

   • Create a grid view filtered to IsCurrent = 1 for everyday use.

   • Create a history view that shows all records, grouped by BusinessKey.

How to implement SCD type 3

1. Design the table schema

   • Add columns such as:

     • CurrentValue

     • PreviousValue

     • LastUpdatedOn

2. Configure update behavior

3. In the app, use validation rules or automation so that when CurrentValue changes: - The existing CurrentValue is copied to PreviousValue. - LastUpdatedOn is set to the current timestamp.

4. Create views

   • Use a grid or detail view that shows both current and previous values so that business users can see recent changes at a glance.

---

Build master–detail views

Overview

A master–detail view combines a primary (master) entity with one or more related (detail) entities. For example:

• Product (master) and price list entries (detail).

• Project (master) and tasks (detail).

PowerTable lets you display and edit master and detail records in a single experience.

How to build a master–detail view

1. Identify master and detail tables

   • Ensure that the detail table contains a foreign key to the master table.

2. Create apps for each table

3. Create a table app for the master table.

4. Create a table app or embedded grid for the detail table.

5. Configure relationships

6. In the master app, go to Relationships.

7. Add a relationship that maps the master key to the detail foreign key.

8. Design the master–detail layout

9. Create a new view and choose Master–detail (or equivalent layout type).

10. Place: - A form or detail view of the master record at the top or left. - A grid view of the related detail records at the bottom or right.

11. Configure actions so that users can: - Add, edit, or delete detail records. - Navigate between master records.

12. Test the experience

13. Open a master record and verify that related detail records appear.

14. Add or update detail records and confirm that the changes write back to the underlying tables.

---

Design forms for data entry

Overview

Forms provide a guided data entry experience. They improve data quality by making required fields, validation rules, and help text explicit.

Typical MVP forms include:

• Create form. Capture all required data to create a record.

• Edit form. Allow updates to selected fields only.

• Read‑only detail form. Present a record without allowing changes.

How to design forms

1. Create a form view

2. In the app designer, select Add view > Form.

3. Choose the mode: Create, Edit, or View.

4. Organize fields

5. Drag fields into logical sections, such as: - General information - Status and ownership - Financials

6. Arrange fields into one or more columns.

7. Apply validation and help

8. Mark required fields.

9. Set input constraints (for example, value ranges, formats, or picklists).

10. Add help text for fields that need clarification.

11. Connect forms to actions

12. For create and edit operations, configure buttons such as Save, Submit for approval, or Cancel.

13. Link the form to your approval flow so that submission changes the record status or triggers workflow.

14. Preview and iterate

15. Use Preview to test the form with sample data.

16. Adjust layout and rules based on user feedback.

---

Next steps

• Identify a single, high‑value business scenario (for example, a product master or project tracker).

• Use this MVP guide to:

  • Create a table app on top of your existing tables or semantic models.

  • Configure layouts, access control, audit logs, approvals, automations, SCD behavior, and forms.

• Roll out the app to a small pilot group.

• Capture feedback and extend the app with additional workflows, integrations, and governance controls.

⁂