The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Solved! Go to Solution.
First step is to bring your data into usable format
and then you can add the column in the Faults table.
Note that I modified your sample data as it was missing the "before 7am" scenario.
Why would you need this in Power Query? Seems to be much simpler and more flexible to implement that in the UI.
.
UI = User Interface. What your report users interact with.
.
Please provide sample data that covers your issue or question completely, in a usable format (not as a screenshot).
Do not include sensitive information or anything not related to the issue or question.
If you are unsure how to upload data please refer to https://community.fabric.microsoft.com/t5/Community-Blog/How-to-provide-sample-data-in-the-Power-BI-...
.
.
Power Query doesn't really like nested "each" statements, it is hard to keep track of the scope. So it is simpler to use explicit functions instead. "k" is a random name for "current row of the outer scope" and you can reference it inside the function.
{0} is just saying "give me the first row of the Table.SelectRows". You could have used Table.First or other methods too.