Hi,
We have a question about permissions for the “subsidiaries feature not enabled” case in non-One World accounts.
The subsidiaries table still exists and it is populated in the background with 1 subsidiary, even though the feature isn’t enabled.
We query the subsidiary table in quite a few of our suiteql transfers and the permission to the table is normally given by "subsidiaries" permission on the lists tab in our Role.
However, when the "subsidiaries feature" is not enabled, the "List - subsidiaries" permission isn't available in the tenant. Only way in our tests we’ve been able to get permissions to read from the table is to assign the admin role to our integration.
Question is - what gives the admin role permission to read from the table when the "List- subsidiaries" permission doesn't exist? Is there a way to pin down which permission gives it access? And to be clear, only thing we’re trying to do is reading from the subsidiary table in our SuiteApp.
We also had an issue when istalling the SuteApp to a non-One World account, like Thomas here: https://community.oracle.com/netsuite/english/discussion/4483249/why-sdf-suiteapp-fails-to-install-on-a-non-oneworld-account-with-subsidiaries-requirement-disabled#latest
Many thanks in advance for your help!