When attempting to save field mapping for an object, an error dialog pops up with the message -
The following fields are required for:
Object X: (Created by ID)
Object X: (Last Modified by ID)
The missing Field could be unavailable if there are no Question that matches its type.
This prevents any mapping to be saved for all forms.
TaroWorks will prevent user from saving field mapping if there are issues that would violate salesforce rules. One of those rules is that required fields must be mapped when a record is created or saved.
Created by ID and Last Modified by ID are required fields, but usually they are exempt because these fields are "Non-createable", meaning that users cannot edit these fields because they are used for audit (to see who and when the record was created or modified). TaroWorks ignores these fields normally these are set as "Non-createable". (This setting is normally invisible, even to system administrators.)
However in your instance they are set as "Createable" because someone made a request to Salesforce support to do so - the usual reason is to import old records from another system while keeping the old audit information. Regardless of the history, TaroWorks expects all Createable required fields to be mapped and that is why the error message appears.
You will need to open a case with Salesforce Support to reset it back to "Non-createable". It is highly recommended to check with your users (and solution vendors) if they need it to be createable to avoid interrupting their work.
Please open a case with salesforce by doing the following:
- Log in to your production instance
- Click Help & Training at the top right
- Click Contact Support
- Click Open a Case, and select the following:
Problem Type: CRM
Product Topics: Configuration
Case Subject: Please set the Created By and Last Modified By fields in our instance as NOT createable.
Severity Level: Level 2 - Urgent
- Copy and paste the following:
We have installed a managed package (TaroWorks) that allows us to create records via mobile devices, however we ran into an issue using a critical feature of that app because the Created By and Last Modified fields on all objects are seemingly set by salesforce to be Createable (not the usual default settings because it works in other instances). We have the following requests:
1) Please let us know if there was a previous request made to salesforce to make those fields Createable - and give details if there was one.
2) May you set it back to NOT createable when we give the signal?
Please contact me (name) at (email) and (phone #)
Please continue to cooperate with Salesforce support until the issue is resolved, then the field mapping will work as documented.