Hi,
I have two questions related to PowerTable (PT)
Question 1
I wonder if it is possible to refresh the data inside a PT, after loading data (populating it) from a Semantic Model (SM).
I've created a new PT, connected it to an existing SM, from which I retrieve multiple fields from different dimension tables.

If one of the underlying dimension tables gets updated (i.e. new rows) in Fabric, the PT does not appear to show these rows. Does it only use the SM to populate the PT initially and then the connection to the SM is lost? I Could not find this in the documentation. However, the next screen writes ' .... and schedule refresh':

Question 2.
What I'm trying to create is a PT which Planners can use to specify new combinations on which they can plan. Since our Fact table contains only dimensions that have been 'hit' (i.e. have actual sales), there might be combinations with no hits / sales but on which we would like to plan anyway. Those new combinations I would like to add to our Planning Sheet (PS).
I'm using the Lookup function to create dropdown menu's (inside the PT) for users:

The values are being retrieved from the relevant PT. These PTs were populated by connecting to a SM (hence it is important for me that the PTs are being refreshed). Is it possible to use the lookup functions directly on the SM or does this have to go via the SQL database (DB)? Alternatively, I suppose I would have to add the dimension tables to the SQL DB (might be wiser right).
Thanks in advance!
3 Replies
Hi Aparna,
Thanks for answering the questions.
With regard to Question 2, that would mean that we have to duplicate our dimension tables into the Fabric Planning SQL database purely to support PT lookups.
With the FabCon 2026 announcements around tighter OneLake integration and the Native Planning Engine, I am wondering:
- Is it possible for PowerTables to use data from OneLake shortcuts as lookup sources?
- If this is not supported today, is this the architectural direction Lumel is moving toward? Ideally we'd like to maintain dimensions once in Fabric and consume them in Planning without duplicating data into the Planning SQL database.
Thanks again.
Hi Frans,
Support for using OneLake shortcuts as Lookup sources has been added to our roadmap and we expect to share more updates soon.
Stay tuned!
Viewing 3 replies - 1 through 3 (of 3 total)
