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.
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.
We are continuing to work with Salesforce on this issue. Salesforce has reproduced the issue successfully and escalated this to their Teir 3 team. Please note that this is only occurring in sandboxes that have been upgraded to Salesforce's Spring19 preview. A work around to this issue is to remove formula fields from the SFM page layout using the SFM Transaction Designer. We will continue to post updates as we have have them. Currently there is no ETA on resolution.
Thanks for the update but know that the workaround doesn't work if you are using the field as part of the filter or process in the SFM so we are on a holding pattern until a solution can be found. Joe Borgstrom Charles Miller
We're are also having issues in our Dev sandbox showing "Exceeds maximum length..." when attempting to save the SFM transaction, but works fine in our Full Sandbox. Both are on SMAX v17.3 and SFDC Spring '19.
We have received the following update from Salesforce. The expect to have this resolved by Wednesday evening. We will continue to post hear as we get more updates.
"The behavior with the "Zero Length Formula Fields" in the Spring 19 release Orgs has been confirmed as a Known Issue by our R&D team. Please find the below Known Issue Link an dclick on the button "This issue affects me" for further notification on the Bug Fix.
Starting in Spring \'19, doing a describeSobject() on an object that has a Formula Text data type yields a length of 0 for that field.
Before Spring \'19, Formula Text data types had a length of 1300.
Our R&D team is working on high priority to fix the bug and tentative fix for the patch release is expected to be tomorrow evening most probably."
Salesforce has informed us that a fix for this issue will be rolled out on 1/10/2019 5:00 PM PST(Safe Harbor). Once the fix is rolled out we will test and update here. We will continue to monitor this issue and provide updates when available.
Just an FYI that it doesn't appear to be in all Orgs yet. I still have one sandbox that is on the original 4.0 patch and not the most recently applied 4.1 which resolves this.