Cannot save SFMs anymore when formula field is used on SFM
E.g "Edit timesheet" SFM has automatically created Title "Timesheet for xxx (2018-12-24 to 2018-12-30) and when trying to save it, we get "Exceeds maximun length Title" error message.
Only difference compared to last Friday (4th Jan, SFM worked) is that Salesforce Spring 19 version was upgraded to our environment.
We will be upgrading our Salesforce to '19 in a few weeks. Elina Ristila, Alex De Sousa, have you opened up SMax support cases for this issue? If so, has Support indicated if this is Timesheet-specific or more general to field length across SFMs?
From what we can tell the issue is impacting formula fields found in SFMs. In our org it's impacting multiple SFMs. We do not use any Time-sheet functionality.
We opened a case a received the following from ServiceMax support:
This issue is currently being reviewed by our CCS/Tier 3 team. We have reached out to Salesforce to determine if this issue is related to Spring '19 patch 3.4. I will keep you posted with any updates received.
We have also created a case for this
Case 00075110:"Exceeds maximum length of formula field error"
ServiceMax is aware of this issue and is working with Salesforce to resolve. The issue is related to the displaying formula fields on the SFM page layout. A temporary workaround is to remove the formula from the page layout.
Please note that this issue is only affecting sandboxes that have been upgraded to Salesforce Spring19, and is not impacting any production environments. Please monitor this post as we will post updates here.
Hello GEORGE PIPER. We tested today in a Sandbox which was updated to Spring '19 over the weekend. We are encountering the same issue reported related to formula fields on the SFM page layouts. We also tested in the same environment late last week before the SFDC upgrade and there were no issues, so from a timing/testing perspective, it seems that this is Spring '19 related.
Please note though that customers are using non-production environments for production issues (i.e., change requests) or for us training since we are going live. At this point we are shut out of training until this issue is resolved in non-production. it should be considered a high priority or other customers not just myself will be impacted.Brian Waiser Dana Soza This is impactful and should be treated as such.
Totally agree with you AJ. We are in a similar position trying to conduct a UAT in a sandbox that is affected and have flown testers in who now cannot test.