Startup SQL tables not loading in PowerBI

Questions (nl)
, ,
1

I have defined a number of custom tables in the Startup SQL. This started with one table which was successfully loaded into PowerBI. By now, we want to expand this with several filtered tables to limit the daily download. However, I can’t get the new tables to appear in PowerBI. Only the old one remains visible, even if I deliberately remove it. I have already cleared the cache everywhere (both Invantive and PowerBI) and even removed and reinstalled PowerBI on my desktop after being unsuccessful, but the problem persists. Below is the startup SQL:

create or replace force view TimeTrackingAllThisYear
as
select *
from Teamleader.V2Flat.TimeTrackingAll
where YEAR(ended_at) = 2026
;
create or replace force view TimeTrackingThisYear
as
select *
from Teamleader.V2.TimeTracking
where YEAR(ended_at) = 2026
;
create or replace force view InvoicesThisYear
as
select *
from Teamleader.V2.Invoices
where YEAR(updated_at) = 2026
;
create or replace force view InvoiceLinesAllThisYear
as
select *
from Teamleader.V2Flat.InvoiceLinesAll
where YEAR(invoice_updated_at) = 2026
;

Does anyone have any advice?

2

The advice is to check if handling new view versions has already been attempted:

It is also recommended not to use year(datumveld) = 2026, but to change it for maintainability and performance to:

ended_at >= trunc(sysdateutc, -2)
and ended_at < add_months(trunc(sysdateutc, -2), 12)

This makes it possible to apply server-side filtering instead of fetching everything and filtering locally.

3

Thank you for this addition! My goal is to only retrieve the filtered table from Teamleader to limit API calls. Is it correct that with the above addition it works this way?

My solution for the reported issue turned out to be disabling the “use HTTP disk cache” in the database settings. Resetting the cache proved insufficient. After unticking, I see the newly defined tables appear in PowerBI.

4

In response to “Is it true that with the above addition, it works like this?”: is there still an issue, or is the behaviour different than expected?

6

This question has been automatically closed after 1 week of inactivity. The last given answer has been marked as the solution.

Please post a new question in a separate topic if the issue occurs again. In the new question, kindly include a link to this topic by pasting its URL into the text.