1. Before you set up the writeback table, we recommend setting up the accoPLANNING visual in Power BI with the different measures and dimensions you’ll need. This will prevent you from having to go back to SQL Management Studio multiple times to change or add more columns.

2. Always include columns for User and UpdateDate as they are used to localize who created the data entries and when.

3. To distinguish writeback tables from the rest of the data warehouse setup, create a new schema with a prefix of your choosing to store your writeback tables.

4. Don’t import your writeback tables into your Power BI reports. You only want to visualize data from your facts or dim tables. Therefore, it is not necessary to import writeback tables. Their only purpose is to store your inserted data and merge it into your fact or dim tables.

5. In order to see your registrations live in Power BI, it is necessary to run Direct Query. Only the tables that receive your data need to be in Direct Query. The remaining tables can be in import mode.

Example: we have a table in Power BI named "dim_product" and an accoPLANNING visual that writes to a writeback table named "dim_product_MDM". A trigger merges data inserted into dim_product_MDM over to the dim table "dim_product". In order to see the data we enter into our accoPLANNING visual, dim_product needs to be in Direct Query in Power BI.

Master Data Management

Master Data Management - Prerequisite