FutureProofing for Known Header Changes - Power Query
While I am building a report, I determine that a field name needs to change at the source in a SQL server, but still need to move forward with my current report. I send a note to the dev group to make that change, but still rename it for now in the query. Unfortunately, when the dev team fixes it upstream, my report will then break - at some point in the future.
Ask: If a header name change made in an applied step is then reflected upstream [same name as the query attempts to change it to] then skip the step and notify owner instead of breaking the refresh at that point in the future.
Of course, there are other ways to solve for this, but these are the types of issues Power BI can begin to develop intelligence around where it has not yet existed - modeled query adaptations within Power Query for changing upstream data formatting, naming, and pathing.