When you enable data sync for a record type, the record type caches your source data in Appian. This gives you faster queries and better performance wherever you are working with that data in Appian.
Sometimes record types fail to sync to the source. When this happens, you can use the information in this article and in the error messages found in the monitoring view to resolve issues with sync.
This article provides troubleshooting steps for sync failures due to:
When you enable data sync for your record type and configure your record fields, Appian automatically creates a mapping between the source schema and record type schema. The source schema includes the names, types, and uniqueness constraints of all the fields in your source. This schema must match the record type's schema in order for Appian to sync the source data.
If a change is made to the source schema without making a corresponding change to the record type, the record type will fail to sync. There are three common causes for a mismatch between the two schemas.
To update the mappings for any of these scenarios, follow these steps:
You can also use this mapping tool if you need to change the database table or Salesforce object that backs your record.
When you set up your Salesforce object as a source for your record type, you have to provide login credentials in order to access Salesforce. If the Salesforce object's credentials are determined to be invalid at the time of the sync, your sync will fail. It could simply be that the password has expired or that the credentials have changed. In order to successfully sync, you need to verify the credentials and re-sync the record type.
To check the credentials and re-sync:
For more information on authentication, credentials, and configuring a Salesforce object, see Connected Systems.
With data sync, your record type can sync to a source with up to 100,000 rows. This includes writing updates to synced records that use a database table or Salesforce connected system as the data source. If your source exceeds 100,000 rows, syncing to the source will fail. Sources with 90,000 to 100,000 rows will sync successfully, but a warning will let you know that the source is approaching or has reached the row limit.
To keep your source from exceeding the row limit, reduce the number of rows added to the source or remove rows wherever reasonable. If the source is expected to regularly exceed 100,000 rows, see Data Sync to determine if the source is still a good fit for data sync.
If you choose to disable data sync, you will need to find and update all references to the original record fields throughout your application.
To find all references to these fields in your environment:
Every object that references the string will appear in your search results. Once you have located all the references in your objects, update the field references. For updating field references in interfaces, we recommend updating the references in Expression Mode.
Sometimes record types fail to sync to the source because of issues that require troubleshooting outside of Appian. When this happens, check the error message for information to help you troubleshoot the issue or contact your system administrator for further assistance. Here are a few brief explanations of these issues and their possible causes:
|Issue||Error Message||Possible Cause|
|Problem connecting to the source.||
||The source didn't respond, VPN failed, or the API limit has been reached.|
|Problem with the sync server.||
||The disk is full or the sync server is down.|
|Problem with row size.||
||A source row exceeds 1 MB.|
|Problem with resource use.||Generic error:
||Too much competition for resources between syncs and other processes.|
On This Page