Power BI (or possibly another source) creating new rows with text in my Queries, ruins formulae.

[Anonymous]

In some of my Queries I am cleaning data by removing blank rows amongst other things. However, every so often (feels like every new time I open my computer) I notice that Power BI, presumably, is inserting two rows into one of my Queries. One of which is a blank row and the other, above this blank row, is blank also except for two cells:

- "Check Point Threat Extraction Secured This Document", and

- "Get Original".

While mildly irritating, the true frustration lies where the insertion of these rows changes from query to query, removing it from the previous one while moving it to another one. 

This messes up my Remove Rows step in my queries as I must change how many rows I remove from the query. This of course means that when I sent or publish the document, it may not run if these rows have been inserted in a new query since the last time I fixed the problem.

Above are screenshots of the problem. Hopefully this is helpful.

Thank you very much for you time in advance 🙂

[Anonymous]

Hi Pete

Thank you so much for taking your time to look at and help me with this here. Your idea did indeed seem to work and I no longer have problems with it.

Do you by any chance know why this message occurs in the first place? My colleagues and I are completely stumped on how, even after some extensive Googling (no problem if not, we're all just super curious).

Thank you again and take care 🙂

Toby 

[BA_Pete]

I've no idea I'm afraid. I can only assume that your company uses the following software and it's adding these tags to writeable documents (XLXS, CSV etc.) within your document storage area (network, SharePoint etc.) once it has scanned them and marked them as safe.

https://blog.checkpoint.com/security/threat-extraction-a-preventive-method-for-document-based-malwar... 

Pete

[BA_Pete]

Hi @Anonymous ,

I may be oversimplifying this but, as your [Column2] contains your data's ID column ([App ID]) which presumably never contains null values in the actual data body, couldn't you just remove redundant rows by filtering on [Column2] <> null, instead of trying to remove a specific number of Top Rows?

Pete