So I have a use case where I will have many custom settings and each custom setting has many fields so easily getting in several MB of custom settings data.
If I put this into a managed package where all the custom settings will be public how does this effect the following -
a) The total amount of cached data allowed for your organization is the lesser of these two values:
- 10 MB
- 1 MB multiplied by the number of full-featured user licenses in your organization
b) Custom settings are a type of custom object. Each custom setting counts against the total number of custom objects available for your organisation.
For b) my guess would be there is no impact on custom object count as its a managed package.
For a) I'm not so sure, is 10MB a hard limit for the org and is set 'high' as it is expected this limit will not be hit across all managed packages and customers customer settings combined.
What happens if there is 3MB of custom settings data and only 1 user in the org (so only 1MB of custom settings data is allowed)?
Does public custom settings size within a managed package count towards the custom settings size limits within the org?