When the connection to the CRM organization is established and you run your first initial Replication job from CRM. The ScribeChangeHistory Plugins, ScribeChangeHistory entity and entity fields are created. The ScribeChangeHistory Custom Entity is used to track deletes in CRM when a record is deleted. At the start of the initial CRM Replication job TIBCO Scribe attempts to create custom fields in the ScribeChangeHistory entity with a prefix of 'New' that are needed for the Replication. This only occurs when connecting to a new CRM instance and running your first Replication job from the new CRM instance. Once this process is completed and the entity and fields exists it will not be required to create again. The fields attempting to be created are 'new_entityid', 'new_changedon', 'new_entityname', 'new_operation', 'new_scribechangehistoryid', and 'new_scribechangehistoryname'.

To review existing fields, In the Microsoft Dynamics CRM UI go to Settings -> Customizations -> Customize the system -> Entities -> Scribechangehistory Entity -> fields as seen in image below.

There may be times during the field creation process where the TIBCO Scribe® Online Replication Services encounters an error similar to Error: "'new_scribechangehistory' entity doesn't contain an attribute with Name = 'new_entityid' and NameMapping = 'Logical'. MetadataCacheDetails" .

This issue is caused by some kind of timeout on the CRM side when attempting to create the custom CRM fields needed by the replication. When reviewing the entity fields you will see the CRM related default fields are created successfully, but the Custom TIBCO Replication related fields were not. CRM normally has a 5-minute timeout for most processes and if the creation of the custom fields takes longer than 5-minutes, you may encounter the issue described in this article.

If a similar error to the one above is encountered review the fields under the ScribeChangeHistory entity to ensure all 6 of the TIBCO Scribe Replication fields exist and if not follow the suggested resolutions below.

1. In the Microsoft Dynamics CRM UI go to Settings -> Customizations -> Customize the system -> entities -> Check the box next to the Scribechangehistory Entity -> Select delete at the top to remove the component from the system -> Save and close.
2. Run the replication job to allow the automatic creation process to occur again. If the replication runs without errors the ScribeChangeHistory entity and fields should have been created successfully. If the same errors occur use option 2.

1. Review the default CRM publisher of the organization to ensure the prefix is set to new.  The prefix must be set to new when manually creating the fields for the ScribeChangeHistory entity. Once the fields are created you can change the prefix of the default CRM publish back to what was previously set.
2. In the Microsoft Dynamics CRM UI go to Settings -> Customizations -> Customize the system -> entities -> Scribechangehistory Entity -> fields -> create a new field -> create the missing field ->Save -> Published the customizations.
3. Review the ScribeChangeHistory entity fields in the CRM UI to ensure the missing fields are not present. If so you can now change the prefix back in the default CRM publisher.
4. Once the entities have been added, please log in to Tibco Cloud Integration - Connect(Scribe) UI, reset the metadata of the CRM Connection, and run the Replication app/solution to see and verify the issue is now resolved.