[Datamart-News] Datamart: New safeguard (update)

[Datamart Support * DAS]

We’ve had a few users ask what a statewide Agency filter would look like in Power BI. There are several ways to approach it, but here’s the method we recommend.

When running a statewide query in Power BI Desktop, start by creating an Advanced Filter using the “is equal to” option. After Power BI generates the filter code, you can manually adjust it to use greater than ( > ) and less than ( < ) operators to capture the full range of agency values.

Since the Agency field is stored as text, Power BI doesn’t offer a built‑in between option for filtering, which is a bit limiting. The workaround is to create the initial filter and then modify the logic, so it behaves like a numeric range.

Filter example within the Power Query Editor section:
[cid:image001.jpg at 01DCBD24.A8E9A8F0]

Adding greater than and less than functionality to the code line:
[cid:image002.jpg at 01DCBD24.A8E9A8F0]

This runs fairly quickly and produces the results you’re looking for. Naturally, you’ll still need to apply additional filters to refine the dataset further.

If you have questions, feel free to reach out to Datamart Support.

[Text  AI-generated content may be incorrect.]
From: Datamart-News datamart-news-bounces at omls.oregon.gov<mailto:datamart-news-bounces at omls.oregon.gov> On Behalf Of Datamart Support * DAS via Datamart-News
Sent: Wednesday, March 25, 2026 2:21 PM
To: WALLACE Aaron * DAS via Datamart-News datamart-news at omls.oregon.gov<mailto:datamart-news at omls.oregon.gov>
Subject: [Datamart-News] Important update: New safeguard for accounting event table queries

Datamart users,

We want to make you aware of a new safeguard we will be putting in place to help maintain the stability and performance of the DAS Financial Datamart environment.

Beginning April 6, we will implement a script that automatically stops any queries running against the accounting event tables (All, Active, Archive) if they do not include an agency filter. These tables are extremely large and resource-intensive, and unfiltered queries have been causing performance issues for users on a statewide level.

What this means for you:

  *   If you run a query against the accounting event tables without specifying an agency, your query will be stopped automatically.
  *   To avoid interruptions, please ensure that all queries against these tables include an appropriate agency filter. (Statewide query filter example: Agency between 000 to 999)

If you have questions or need help adjusting your queries, feel free to reach out.

Thank you for your cooperation,

[Text  AI-generated content may be incorrect.]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://omls.oregon.gov/pipermail/datamart-news/attachments/20260326/c50ab711/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 25189 bytes
Desc: image001.jpg
URL: <https://omls.oregon.gov/pipermail/datamart-news/attachments/20260326/c50ab711/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 11721 bytes
Desc: image002.jpg
URL: <https://omls.oregon.gov/pipermail/datamart-news/attachments/20260326/c50ab711/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 57758 bytes
Desc: image003.png
URL: <https://omls.oregon.gov/pipermail/datamart-news/attachments/20260326/c50ab711/attachment.png>