> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/administration/install-configure/standard-objects-that-behave-oddly.md). # Standard Objects That Behave Oddly This article offers valuable information on standard objects in Salesforce that have unique characteristics, which are important to consider before configuring S-Docs on these objects. *** ## Campaign * By default, "Campaign Member Statuses" are not added to the Campaign object related list. Please make sure to add the "Campaign Member Statuses" into the Campaign Page Layout related list. ## Campaign Member * You cannot add any buttons. * You cannot create an S-Docs record on it. * There is no list view associated with it; therefore MassMerge will not work. * You can only run Campaign Member on Campaign. * Campaign Member doesn't allow you to attach files (No Notes & Attachments), and has no related lists. You need to create an AdditionalRelationship to Campaign and store documents there. ## Quote * This object must be enabled by a User. * Standard object but is not "hooked up" in S-Docs out of the box. You will need to add it to SDoc Relationship and the Related to Type picklist just like a custom object. * API name for Quote is without a space — it should be `Quote`. ## Work Order * Standard object but is not "hooked up" in S-Docs out of the box. You will need to add it to SDoc Relationship and the Related to Type picklist just like a custom object. * API name for Work Order is without a space — it should be `WorkOrder`. ## Event * S-Docs related list cannot be added to the Events object. * `WhoId` and `WhatId` are polymorphic (reference multiple objects). Use of these fields within a WHERE clause requires special formatting and handling. ## Task * Activity history is a "Task" object under the covers, but its visibility is controlled by the visibility to the parent. * `WhoId` and `WhatId` are polymorphic (reference multiple objects). Use of these fields within a WHERE clause requires special formatting and handling. ## Person Account * Person Accounts introduce complexities in understanding relationship differences, specifically when trying to query this object. ## GiftTransaction * Is a standard object provided within the Nonprofit Success Pack (NPSP) for Salesforce. {% hint style="info" %} The article '' provides an in-depth exploration of dynamic SOQL querying specifically tailored for Person Accounts. It dives into various aspects of querying Person Accounts, highlighting nuances and considerations for handling relationship differences. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.sdocs.com/sdocs/administration/install-configure/standard-objects-that-behave-oddly.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.