Anyone know what happens if you include a OneWorld...
# general
s
Anyone know what happens if you include a OneWorld field in a bundle and attempt to deploy it to a non-OneWorld account? (e.g. Custom record type with a subsidiary list/record field)? I only have access to OneWorld accounts, so I can't easily test to see what happens.
Found out the answer: In my example, NS will deploy the custom record type and subsidiary field. However, the subsidiary field will always show "Parent Company" in the dropdown in a non-one world account.
If a user attempts to view "Parent Company", it will tell them the "Subsidiaries" feature is not enabled.
@KevinJ of Kansas FYI, see above. Thanks for your response.