Revenue Arrangement with hundreds of Revenue Elements takes a very long time to save, and throws an unexpected error when you try to save it. How do we fix this? There are practically no User Event Scripts or Workflows deployed to Revenue Arrangements in our account. What could be causing the problem, and how do we fix it?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems like the issue with saving Revenue Arrangements with hundreds of Revenue Elements could be due to a few reasons: 1. Permissions Error: This could be due to the role that is trying to save the Revenue Arrangement not having the necessary permissions. Make sure the role has the necessary permissions to create and edit Revenue Arrangements and Revenue Elements. 2. Mandatory Fields: The error message suggests that there might be mandatory fields in the Revenue Elements that are not being populated. Make sure all mandatory fields are populated before trying to save the Revenue Arrangement. 3. Custom Fields: If you have any custom fields applied to Revenue Arrangements, they could be causing issues. One user reported a similar issue where they were unable to edit any Revenue Element fields after creating a list/record transaction column field and applying it to Revenue Arrangements. The workaround was to convert the field from a list/record field to a free-text field. 4. Scripts or Workflows: Even though you mentioned that there are practically no User Event Scripts or Workflows deployed to Revenue Arrangements in your account, it's worth double-checking. A script or workflow could be interfering with the saving process. To fix the issue, you could try the following: 1. Check the role permissions and ensure all mandatory fields are populated before saving the Revenue Arrangement. 2. If you have any custom fields applied to Revenue Arrangements, try converting them from a list/record field to a free-text field. 3. Double-check for any scripts or workflows that could be interfering with the saving process and disable them if necessary. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******