I have a query that gets data from a DB view that gets dumped into a CSV file periodically, my query source inside PBI is this CSV file, let's call that query view "UsedCars", and inside this I will have the following columns: ID, Name, ReleaseYear, Maker, this view/table may (and will) have dupped cars (same name, year and maker) but different ID, because the ID is unique.
I then procceded to dump UsedCars into a CSV file, I then openned it on Excel and saved it as XSLX so I could add two more columns that I needed: Status and Description. Those are the ones I need to populate manually, because I have to assess each and every car condition and give them a status and possibiby a description. After that I created a new query view using this XSLX file as source, let's call this new query view "UsedCarsStatus". Now I have it inside PBI with the data I want and I can easily correlate it with other tables using the unique ID.
The issue is that "UsedCars" is dynamic, it may grow or shrink on a daily basis and having to export it into a CSV each time is troublesome, even more when I have to use Excel functions to populate the cars I already assessed in past waves (yesterday, the day before, last Monday, etc), because when I export the CSV it's raw and don't even contain the two columns I create inside Excel (Status, Description).
This feels like the wrong way to do things. What would be the best approach in this case?
