Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Data Privacy
  18. Oracle E-Business Suite Retirement Reports
  19. JD Edwards Enterprise Retirement Reports
  20. Oracle PeopleSoft Applications Retirement Reports
  21. Language Settings
  22. Appendix A: Data Vault Datatype Conversion
  23. Appendix B: Special Characters in Data Vault
  24. Appendix C: SAP Application Retirement Supported HR Clusters
  25. Appendix D: Glossary

Salesforce Limitations

Salesforce Limitations

Archiving from Salesforce has the following known limitations:
  1. Salesforce marks the "querybale" attribute to "false" for some of the objects. This means that external applications cannot query the object, so the Enterprise Data Manager cannot import metadata from these objects. For more information about importing metadata from Salesforce, see the chapter "Salesforce Accelerator" in the
    Enterprise Data Manager Guide
    .
  2. Salesforce marks the "deletable" attribute to "false" for some of the objects. This means that external applications cannot delete the records in the object, so Data Archive cannot delete records from these objects.
    The FeedPollChoice and FeedPollVote tables that are a part of the standard accelerator Task and Event entities have this limitation. The Task or Event entity does not delete the records from these tables. However, because of the cascade delete functionality in Salesforce, Salesforce deletes the records in these tables when Data Archive deletes the records in the parent table.
    For more information about the FeedPollChoice and FeedPollVote tables, see the chapter "Salesforce Accelerator" in the
    Enterprise Data Manager Guide
    .
  3. Salesforce does not allow triggers on objects to be updated through an API. Because of this Data Archive cannot deactivate or activate a trigger.
    Workaround: You can use the Force.com Migration Tool, the Salesforce user interface, or the Force.com IDE to activate or deactivate a trigger.
  4. The "Bookmark" information of a Feed Item in Salesforce cannot be archived, because bookmark information is not exposed in any Salesforce object.
  5. Salesforce will not allow you to execute the select query "select * from <object _name>" on some objects, like "CollaborationGroupRecord." Because of this the row count report cannot be generated for the entities with tables that have this limitation. The archive job will throw the following error at steps for which the row count report is enabled: "MALFORMED_QUERY: Implementation restriction: <object_name> requires a filter by a single Id….."
    Workaround: Terminate the job, edit the archive project definition, disable the row count report in the steps, and schedule the job.
    Note: The "ContentDocumentLink" object also has this limitation, but the row count select query is modified, so you can enable the row count report for the Task and Event entities.

0 COMMENTS

We’d like to hear from you!