SFDC platform supports only 100 custom fields on Activity Object that include Managed package fields. Today, we have reached limit on our org and ServiceBoard Managed package is creating 3 new fields. The total count of ServiceMax Managed package fields is reaching to 14 along with 3 new fields. In our org Activity object is used many streams or porcesses other than Field Services. This is blocking us to upgrade to new version SVMX and Service Board.
The Engineering and Product teams of ServiceMax should understand the limitation on Activity object custom fields and review new fields created on this object. If I can't release 3 fields on this object then we are completely blocked to upgrade newer version of ServiceMax. One manage package consuming 14 fields out 100 is not mature design. There is serious need to review this issue and stop further more field creation in this Object.
Anyone is same situation as us?
1000% Agree and have raised this point in the past as we struggled with the same limit.
Pitney Bowes would welcome some client centric thinking and development in this area.
Two of the 3 new fields ("version number" and "integration source") are required to handle the integration conflicts (e.g. concurrent updates, race conditions) that are inevitable when connecting two systems. The third field ("appointment status") is needed to manage the Appointment lifecycle status, an important new capability introduced by Service Board.
We fully understand the frustration, and we are very well aware of the limitations imposed by SFDC. This was not an easy decision, but in the end all alternative approaches (e.g. adding a supporting object) would have created worse issues around performance and governor limits.