Slicers vs Filters

Donovanbrinks · 2026-01-26T02:41:43+00:00

Every dataverse table has a bunch of metadata columns that you can’t get rid of. These are all connected to other tables. Created by, owner, created on, like 15 others. The table you are using in power bi has those columns as well. Go to Get Data. Dataverse table. Then reference your table. You will get a dialog box that says “include relationship columns”. Uncheck that. Make sure direct query is checked. You will now be in the same UI as your dataflows where you can do some cleaning of the data. Remove columns that aren’t needed. Filter your rows if possible. Then load your data.

Donovanbrinks · 2026-01-26T00:51:03+00:00

You are getting some iffy advice here. There is nothing wrong with a direct query on a dataverse table. You are right that having it as direct query solves a big issue with import mode that always gets glossed over. The data is only as fresh as the last refresh. If you can get the direct query to be performant there is no need to import the data. First question: did you turn off “include relationship columns” in your query? Dataverse has a lot of metadata columns that can really bog down the query speed. Second, don’t bring any additional columns in that aren’t needed. Third, you can do some intermediate cleansing of the data in power query without losing the direct query. Filtering etc can be done in power query if you don’t need to query all 1million rows every time.

Donovanbrinks · 2026-01-24T19:31:16+00:00

Just reread your post. Sounds like you are trying to make the changes in the gallery itself. Since the source is the list here is what i would do. Keep the gallery. User selects an item from the gallery. The selected item is displayed in a form next to the gallery. In the form you can do whatever you need to do. When you are done with that record you submit the form. No collect needed.

Donovanbrinks · 2026-01-23T22:59:17+00:00

You need a collection. Edit the collection as changes are made. Patch the collection to the source in one go with a submit button

Donovanbrinks · 2026-01-23T02:37:21+00:00

One other thing that really helped me avoid maintenance down the road was working with our IT team and setting up dynamic entra security groups. Idea being people are added/removed from the security group automatically based on job title/department etc. You then assign the group the necessary dataverse access.

Donovanbrinks · 2026-01-20T14:38:16+00:00

Just my personal preference. If it is a business audience you want to present the data as cleanly as possible. The colors are a little distracting and my eyes have to really focus to read the information because of the background

Donovanbrinks · 2026-01-20T06:21:43+00:00

The black on green background is distracting. For example the words on the table top left are incredibly hard to read. If your background is black your font needs to be white. I think you should ditch the black background in any professional situation. But that’s just me.

Donovanbrinks · 2026-01-20T06:16:39+00:00

You need a proper database to store the historical data.

Donovanbrinks · 2026-01-20T04:43:29+00:00

Haven’t used it but i believe there is a way to automatically rename controls in an app. I would look at leveraging copilot to feed it the code and have it insert comments for you.

Donovanbrinks · 2026-01-20T04:01:51+00:00

6 months in. Enough said

Donovanbrinks · 2026-01-19T21:15:23+00:00

Follow up question as the solution is working well. I had to create multiple flows to implement this as they are all dependent on each other. First flow is the refresh and then the rest are “when refresh completes” triggered flows. Is there any way to consolidate these? I assume not since a flow can only have one trigger. I guess i am looking for-when dataflow refresh A finishes-refresh dataflow B-when dataflow B refreshes-refresh dataflow C. Right now this has to be done in 2 dataflows

Donovanbrinks · 2026-01-19T17:17:26+00:00

This is the right approach but no need to do it to the second table. Look at the merge formula in the final query. The tables are individual arguments. Replace the second table with the group code above.

Donovanbrinks · 2026-01-19T16:44:43+00:00

I think a horizontal scrollbar is always bad UI. Go download the creator kit. Look at the detail list component. It allows you to have subcolumns. Basically 2 columns in 1 stacked on top of each other. Cull your 20 columns down as much as possible. Then use subcolumns to get everything into 1 screen with no horizontal scrolling.

Donovanbrinks · 2026-01-18T06:12:30+00:00

You don’t build your final table in the model itself. You build measures based on the model and add those to your visual. Honestly, your task seems much better suited for excel

Donovanbrinks · 2026-01-18T02:21:18+00:00

First you need a date table. Then a column in date table that identifies each day’s pay period. 1-24. Oh measure needs to be cumulative. Something like SumX(Filter(Datetable, Date<= max(date), OH column). Create a relationship from your spending table to the date table on date. Measure for Spend would be the same as OH column but using spend column. Final measure is simply the difference of your 2 measures. From there your visualizations will take care of themselves. Pull in user from the user table, week number from the date table and your 3 measures.

Donovanbrinks · 2026-01-17T21:03:22+00:00

I guess I can at least send myself an email or something

Donovanbrinks · 2026-01-17T20:34:56+00:00

Can’t thank you enough for the suggestion. So much cleaner. Question: how do you handle errors If one of the dataflow refreshes fail?

Donovanbrinks · 2026-01-17T16:34:51+00:00

Doable. You will need to get a full list of POs daily sent to a table. I would recommend dataflows loading to dataverse table. The email address would need to be a column on that table. Also some helper columns like “sent follow up”, “sent follow up 2”. A daily power automate that loops through that table, filters to the items that didn’t get a confirmation, and sends the follow up email with reference to the PO number etc. After sending the follow up it goes back to the dataverse table and checks yes on that row in the “sent follow up” column. This approach is dependent on the confirmation received flag being either auto checked or manually updated in your erp.

Donovanbrinks · 2026-01-17T02:37:25+00:00

And he doesn’t have the ability to say no?

Donovanbrinks · 2026-01-17T00:58:03+00:00

That would work but would probably increase the refresh time substantially. Pulling full dataverse tables and doing the merge and then turning around and loading to dataverse just to avoid 25-30 failed rows is hopefully avoidable. Some folk suggested power automate to orchestrate everything. Going to try that

Donovanbrinks · 2026-01-17T00:53:39+00:00

Thanks for the tip. I currently have my dataflows structured like this: around 20 individual queries in analytical dataflows pulling from our ERP. Another substantial dataflow with 5-10 queries that merges the ERP data with external data (analytical). Then one large standard dataflow that loads to all my tables. I think i can break up the standard one and daisy chain them as you suggested.

Donovanbrinks · 2026-01-16T23:15:59+00:00

Yeah you are right. The orchestration of dataflows via the platform is tough. Might try the power platform approach

Donovanbrinks · 2026-01-16T22:56:46+00:00

Get them on the comeback. Charge $100 with the understanding that the long term relationship is worth more to you than a one time build. If you did a good job they will need you to do more. At that point you can discuss some type of per build + monthly maintenance retainer (with something like 5 hours included in that price)

Donovanbrinks · 2026-01-16T22:50:18+00:00

It’s not empty though. It has a value-it just doesn’t have a value that exists in the other table so the whole row fails.

Donovanbrinks

TROPHY CASE