I'm guessing the answer is no, but is there a way around the Netsuite2.com ODBC connector using script ID names for field names versus field Display Names? Long before my time, people did not follow best practice and so we have a bunch of fields named custentity1, custentity2, etc. In the netsuite.com data source, it took the display name of those and pushed that to the data warehouse, but netsuite2.com is pulling custentity1, which obviously isn't helpful. I know I could change those, but they're tied to other stuff that might break, so I'd prefer not to.

You can alias them in your query (

SELECT custentity1 AS xyz

)

That's a good idea, though I'd have to check if Fivetran let's you use your own query. I'm not sure they do

This may sound like unhelpful advice, but the best time to make the change is now. If you replicate the fields as is, you are building potentially more dependence on the current script ids, making it even harder to change them in the future. I know the reality is we don’t always have the luxury of doing that, but this could definitely add more technical debt. Something worth considering.

That's a fair point @scottvonduhn. As I'm sure you run into also, the issue is always timeframe and prioritization. I'll keep it in the back of my head though.

of course, we live in a world with constant deadlines and priorities. but yes, i’d at least consider that the moment before switching to NetSuite2.com would be a good time and motivation to consider at least trying to rename some of the fields, particularly the most used or most meaningful ones