My Salesforce notes

*PRODUCT: *PRODUCT RULE: ->Error Condition -->Action (on Prod or Bundle) -->Lookup queries ->Config Rule Configuration Attributes:  Create Product Option picklist field Create Config attributes Create Quoteline picklist field *PRICING: Block: lower bound is included (1), upper bound is excluded (11) for a block 1-10 products Overage rate List price:  Salesforce CPQ uses the Special Price field to hold the result of cost plus markup, allowing comparisons between it and the list price Contracted price: Do not create two contracted prices on the same account that act on a single product The Price Waterfall: Pricing Field What It Represents Original Price Price book price List Price Price book price, percent of total price, block price, or option price override Special Price Cost plus markup price, contracted price, or option discount Regular Price Result of volume-based discounts Customer Price Result of manually editable discounts Partner Price Result of partner discount, set

  Salesforce Anti-Patterns: A Cautionary Tale Designing the data model for performance Loading data into a lean configuration Suspending events that fire on insert Sequencing load operations Loading and extracting data Salesforce record locking cheat sheet Bulk API is by far the quickest way to insert, query, and delete records. The Bulk API should be used for tens of millions or hundreds of millions of records to load or extract. By chunking your queries into batches, tuning your batch sizes for optimum throughput, and avoiding locking errors, you can achieve very high performance for your data movement tasks. Taking advantage of deferred sharing calculations Pre-Data Loading Configuration Steps Create the role hierarchy. Assign users to roles. Set organization-wide defaults to Public Read/Write. Post-Data Loading Configuration Steps Set organization-wide defaults to Public Read Only or Private. Create public groups and queues. Create sharing rules.

 Applied for exporting more than 1 million records. Create or use an existing auto-number field. Alternatively, you can use any number fields that can make up a unique value, as long as they are sequential.  Note : If you are adding a new auto-number field, make sure to enable the “Generate Auto Number for existing records…” option. Create a formula field that converts the auto-number field text value into a numeric value—you cannot use an index with comparison operators such as “<=” (less than or equal to) or “>” (greater than) for the text-based auto-number field. In this example, we’ll name this field “ExportID.” Place a custom index on the formula field by contacting salesforce.com Customer.  Source: https://developer.salesforce.com/blogs/engineering/2013/06/extracting-large-data-volume-ldv-in-force-com