Row headers are not always in the first row

[StuBee]

Hello,

Been using this forum for a while and never yet needed to askd a question (they've normally been asked)

I have headers that are usually in the first row of the file, but there are some where there is a random date in the first one or two lines.

Would any of you be bale to help with, where it says "PSID=" in the first or second row that this is not used as the header, or where it says "product" this is used as the header?

Thank you

[v-shex-msft · Accepted solution]

Hi @StuBee,

Is your row header start on a specific row or randomly index? If you mean it stored on a fixed row number, your can direct extract specific row value and use it with rename functions.

If you mean stored randomly, I'd like to suggest you store these column names in other tables and direct invoke in rename functions to write custom function to analysis and external column name row values.

Regards,

Xiaoxin Sheng

[StuBee]

Thanks for this, it is that a random 1 or 2 rows may appear (not always) before the headers.

Great idea, just rename them. Thank you so much (feeling a little stupid for not thinking of that)

🙂

[kentyler]

You can fix this in Power Query, either during the process of loading the data or afterwards. There is an option in the ribbon for removing rows

I'm a personal Power Bi Trainer I learn something every time I answer a question

The Golden Rules for Power BI

1. Use a Calendar table. A custom Date tables is preferable to using the automatic date/time handling capabilities of Power BI. https://www.youtube.com/watch?v=FxiAYGbCfAQ
2. Build your data model as a Star Schema. Creating a star schema in Power BI is the best practice to improve performance and more importantly, to ensure accurate results! https://www.youtube.com/watch?v=1Kilya6aUQw
3. Use a small set up sample data when developing. When building your measures and calculated columns always use a small amount of sample data so that it will be easier to confirm that you are getting the right numbers.
4. Store all your intermediate calculations in VARs when you’re writing measures. You can return these intermediate VARs instead of your final result  to check on your steps along the way.