sync account to salesforce value not updated but opportunity sync works
ART-2047_KNOWLEDGE_NODE-31
prompted to manually map certain fields if needed. You can track the migration and perform any required mapping under **Settings** > **Integrations** > **AirSyncs**.\n\nThe duration of the import depends on the size of the Salesforce account and the data being imported. It can take seconds for an account with only a few dozen cases to a few hours for an account with tens of thousands of cases with many attachments. DevRev honors the Salesforce API rate limits and back-off and resumes
Salesforce AirSync | AirSync | Snap-ins | DevRev
ART-2911_KNOWLEDGE_NODE-27
![]()\n\n   Providing incorrect information in the configuration may lead to the merging of incorrect accounts, an irreversible action. The primary account continues syncing after the merge, while the secondary account no longer syncs with the external source. Field updates to the secondary account are ignored. When accounts are merged, the values of single-value stock fields from the secondary account, as well as any **common** custom field values of the secondary account, are lost.\n3. Click
Account deduplication | Automate | Snap-ins | DevRev
ART-2045_KNOWLEDGE_NODE-58
synced items is not propagated. This includes works (issues or tickets), accounts, users, links, and other types. When an item is deleted (either in DevRev or at the source) and that item exists at the other end, it will not be deleted but no further updates to it will be made.\n\n### References\n\n* In-text references (such as @mentions) will not be remapped.\n\n### Schema changes\n\n* If a new type is added to the external source after the initial sync, it will not be automatically picked up
AirSync | Snap-ins | DevRev
ART-13117_KNOWLEDGE_NODE-0
b"Will Airdrop recreate/duplicate merged accounts or contacts?\n\nNo, Airdrop can recognize that you merged an account or contact, so it will not create them again and will keep updating any linked tickets or other linked objects.Updates from an account in the external system are not synced to DevRev, why not? I merged the account with another in DevRev.\n\nOnce you merge an account or contact, Airdrop stops syncing updates to it (just to the account or contact, not to the linked items, linked
Airdrop duplicates merging
ART-2047_KNOWLEDGE_NODE-44
limitations](/docs/import).\n\n### Comments\n\n* Threaded case comments are not synced back to Salesforce.\n\n### Updates\n\n* Updates to Picklist\\_MultiSelect fields from DevRev are not loaded/synced back to Salesforce.\n\n### Knowledge articles\n\n* Only published articles in the master language are imported from Salesforce to DevRev.\n* If the article has multiple rich text content fields, the article will be split into multiple DevRev articles, one for each rich text content
Salesforce AirSync | AirSync | Snap-ins | DevRev
ART-2047_KNOWLEDGE_NODE-27
\xe2\x9c\x85 | \xe2\x9c\x85 |\n| Comment on Case/Task/Problem/Incident | Comment on Ticket | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Attachment on Case/Task/Problem/Incident | Attachment on Ticket | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Product | Product | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Account | Account | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Contact | Contact | \xe2\x9c\x85 | \xe2\x9d\x8c |\n| Opportunity | Opportunity | \xe2\x9c\x85 | \xe2\x9c\x85 |\n| Lead | Contact | \xe2\x9d\x8c | \xe2\x9d\x8c |\n|
Salesforce AirSync | AirSync | Snap-ins | DevRev