In general, GRAX supports backup of any Salesforce objects that meet all the following criteria:
- Able to be queried
- Has at least one 'audit date' field (
CreatedDate), and that field is sortable.
- The running user (who is loading the list of objects and selecting which to back up) has at least read access to the object.
This covers most Salesforce objects.
Let's take a look at specific objects or categories of objects that GRAX doesn't currently support. Please note that these lists are not exhaustive and there may be additional objects that are unsupported. Typically, they aren't able to be queried or aren't fully supported by the API in some way. Please reach out to GRAX if you have questions about specific objects.
AIApplication AIDataDefinition AIError AIInsightAction AIInsightFeedback AIInsightReason AIInsightSource AIInsightValue AIMetric AIModel AIModelDefinition AIModelGraph AIPredictionDefinition AIRecordInsight AIState AcceptedEventRelation AccountUserTerritory2View ActivityMetric ActivityMetricRollup Address AggregateResult AppDefinition AppTabMember AssistantRecommendation AssistantRecommendationShare AssociatedLocation AuraDefinitionBundleInfo AuraDefinitionInfo CaseStatus ChatterMessageThread CollaborationGroupRecord ColorDefinition ConfidenceThresholdConfig ConfidenceThresholdCoverage ContentBody ContentDocumentSubscription ContentFolderItem ContentFolderLink ContentFolderMember ContentHubItem ContentTagSubscription ContentUserSubscription ContentWorkspace ContentWorkspaceDoc ContentWorkspaceMember ContentWorkspacePermission ContentWorkspaceSubscription ContractStatus ContractStatusDeclinedEventRelation CronJobDetail DashboardComponent DataStatistics DataType DatacloudAddress DatacloudCompany DatacloudContact DatacloudDandBCompany DecisionTable DecisionTableDatasetLink DeclinedEventRelation DirectMessage EinsteinDiscoveryModel EmbeddedServiceDetail EmbeddedServiceLabel EntityDefinition EntityParticle EventBusSubscriber EventWhoRelation FeedAttachment FeedTrackedChange FieldDefinition FieldSecurityClassification FlexQueueItem FlowDefinitionView FlowVariableView FlowVersionView FormulaFunction FormulaFunctionAllowedType FormulaFunctionCategory GroupSubscription IconDefinition IdeaComment IdpEventLog KnowledgeArticle KnowledgeArticleVersion ListViewChartInstance ListViewChartInstances Location MacroInstruction MetadataPackageVersion Name NetworkUserHistoryRecent NotificationMember OauthToken OrderStatus OutgoingEmail OutgoingEmailRelation OwnerChangeOptionInfo PartnerRole Person PicklistValueInfo PlatformAction PlatformEventUsageMetric PredictionDefinition PredictionDefinitionField Publisher RecentlyViewed RecordRecommendation RelationshipDomain RelationshipInfo S2XEventMap S2XEventMapSelfServiceUser SearchLayout SelfServiceUser ServiceAppointmentStatus ShiftStatus Site SiteDetail SolutionStatus TabDefinition TaskPriority TaskStatus TaskWhoRelation TenantSecret ThirdPartyAccountLink TwoFactorInfo TwoFactorTempCode UndecidedEventRelation UserAppMenuCustomization UserAppMenuItem UserEntityAccess UserFieldAccess UserPermissionAccess UserRecordAccess UserRecordAccessTaskStatus UserSetupEntityAccess VisualizationPlugin VisualizationResource VisualizationType Vote WorkOrderLineItemStatus WorkOrderStatus
AnalyticsBotSession ApiEvent BackgroundOperationResult BotAnalytics BotEventLog FieldHistoryArchive IdentityVerificationEvent LightningUriEvent ListViewEvent LoginAsEvent LoginEvent LogoutEvent RecordActionHistory ReportEvent UriEvent
EventStore Feed History Share __ViewStat __VoteStat __b (big objects) __mdt (custom metadata types) __x (external objects) _hd (historical trending objects)
Let's take a deeper look at considerations and support around specific features.
Some Salesforce objects contain binary fields with base64 encoded data (that is files). GRAX supports Attachments, Content (via the linkages amongst
ContentDocumentLink), and EventLogFiles. For any other objects that may contain these base64 fields, GRAX may support backing up the other data fields besides the binary, per the rules mentioned above.
GRAX doesn't support 'feed' objects within an object backup.
FeedAttachment doesn't have an audit date field and thus isn't supported. This object is a junction between FeedItem and ContentVersion. You are still able to back up the File that is posted in the chatter feed as long as that file is also linked to the record via
ContentDocumentLink, which is supported and available to select in the hierarchy.
Tag objects are supported. For object backups, you can see a backup type category if you have tags enabled in your org.
GRAX supports both the classic and lightning knowledge object model, which revolve around objects ending in either
kav. VoteStat and ViewStat objects aren't supported, as indicated above.
GRAX doesn't support backing up the base64 body (binary) of a Document. However, you can back up the other fields on the
Document object, such as name, description, type etc. Documents are more relevant for Salesforce Classic and the recommendation is to move to Files, which are fully supported by GRAX.
You won't find the
Document object available for archives.
Custom Setting objects should appear in the GRAX backup list, provided they aren't
protected. Please note that some custom setting objects may not be supported for archiving or restoring, even if they are being backed up. Click here for more information on custom settings.
GRAX doesn't support backup of custom metadata types.
Updated about 4 hours ago