I have a workbook with a query that hooks up to my data in DevOps for Work Items (approximately 10,000 records). The query brings back about 20 columns from the table (and expanded tables - e.g. projects), and has another dozen or so Custom Fields - e.g. the age of the item worked out in days, and others - if value = this then custom = 1, else = 0 type custom columns.
It does take quite a while to refresh, so am trying to find ways to shave seconds or minutes off the refresh time. One thing I wondered, and was hoping someone could confirm, is whether the query may run better if I replaced all of the null values with zero (or some other value) for the fields that I'm bringing through. Or does Power Query not mind there being NULLs?
Another thing I wanted to try and establish was whether I'm right in creating these 12 columns, re-ordering all of the standard and custom columns, renaming the fields, filtering out some records depending on the project site they relate to, within the one query. I've tried to keep everything together, so I'm not surprised it does take a few minutes to refresh, but just wondered if that was good practice with Power Query or whether I should split down into smaller chunks?
Appreciate that speeding up a query is the holy grail of Power Query, and there may not be anything that can be done, I'm just hoping that there may be options besides using 'Fast Load' (which I've already got turned on).
