I am in the situation where a client is demanding that I redo some reports so they are organized by one table id (ID_A) instead of another table id (ID_B) that exist in separate databases. All the reports are running from ID_B and they were seeing some data issues. The client feels this was because the data was being pulled by ID_B and should be pulled by ID_A.
I have explained that ID_A does not even exist in the database that I am looking at in this situation and I need to use ID_B to navigate to another database that contains the table with ID_A. I can display both/neither/either ids in the report. In the end the data issue was simply a data mapping bug completely elsewhere.
Now the client is not seeing the bad data, but still wants me to rework with ID_A, because that is the "correct" way to do this. From my perspective, as long as the data displayed is what they want, it is the "correct" way, so I feel like it is extra coding time to redo this work.
I can directly lie to them and say, yep, its done and go about my way. I am worried that they will look at the code in the end (they have rights to it). Does anyone have any experience convincing a client that data can be retrieved in more than one way, or whatever I need help with here. Extremely tight deadlines prevent me from just saying F IT and redoing the code.