If you were building a solution that referenced the SUBSIDIARY record ... how would you build it so it worked on both OneWorld and NonOneWorld accounts. [I have inherited a solution that has a field on a custom record that is of type SUBSIDIARY].

I feel like there is something I am missing here. Just use runtime to check if the account is one world and follow different logic trees?

No @Sandii. So, I have a custom record, that has a field called 'subsidiary' .. it's a List/Record of type SUBSIDIARY (-117). If I deploy this to a NON OneWorld account ... it deploys the custom record, but drops the 'subsidiary' field