If Fiscal Year settings are configured in the Developer Console, they are available for new subscriber signups in the published application version.
The following table explains the upgrade behavior of an existing packaged Fiscal Year settings that are already deployed in the subscriber's organization.
Consider the following scenario to understand the packaging behavior better:
Version 1: Fiscal Year not configured in Developer Console
Assume that there are two subscriber organizations before upgrade:
- Subscriber1: Fiscal Year already set by the subscriber.
- Subscriber2: Fiscal Year not set.
Version 2: Fiscal Year configured in Developer Console
After publishing Version 2 and upgrading existing subscribers:
- Subscriber1: No change. Fiscal Year remains as set by the subscriber.
- Subscriber2: Fiscal Year remains not set. The newly configured developer values are not made available to existing subscribers through upgrade.
For a new subscriber signup on Version 2, Fiscal Year is set from the developer-configured defaults. The subscriber can update the Fiscal Year values in their subscriber org, and it will not be affected by any future upgrades.