You are here:
Considerations and Limitations
Review these considerations and system behaviors before implementing or using Sample Management.
Required Editions
Available in: Lightning Experience Available in: Enterprise, Unlimited, and Developer Editions |
General Limitations and Setup
- Address Field Limitations: Due to a platform limitation regarding complex address fields, the Shipping Address and Customer Address on a Sample Request do not automatically populate from the associated Account. Users must manually enter data into both fields.
- Experience Cloud Visibility: For Partner Experience, the Sample Request object is not displayed by default. Admins must manually customize the Experience site to include the Record List for the Sample Request object.
Sample Request Items and Products
- Product Selection is Final: Once a Sample Request Item is saved, the referenced product or custom specification (SampleItemReference) cannot be changed.
- Strict Product Filtering: Users can only add standard products to a request if the product is active and its Specification Type is set to Sample.
- Pricebook Display Behavior: When adding products, the user experience changes based on the Pricebook. If a Pricebook is linked to the Sample Request, the selection window shows only sample products from that Pricebook, including their List Price. If no Pricebook is linked, the window shows all sample products in the org, but the List Price is left blank.
- Price and Cost Book Validations: If a Pricebook Entry or Costbook Entry is specified, the system validates that the product matches the one selected for the request. Additionally, the Sample Request's Requested Date must fall within the Costbook Entry's effective date range.
- Automatic Scaling and Population: The system automatically scales product quantities based on the configured Unit of Measure (UOM) rounding methods (Up/Down/Nearest). It also automatically populates the Product Category, Sales Price, and Cost Price in the background based on related standard and cost books.
Product Requirement Specifications (PRS)
- Category Configuration Prerequisite: Admins must configure the Category picklist values on the PRS entity (e.g., Functional, Performance, Packaging, Compliance) before users can create custom requirement specifications.
- Hidden System Fields During Creation: When users create a new PRS or PRS Version, the Latest Version and Version fields are hidden from the UI. These are non-editable system fields that become visible on the record's Details tab only after it is saved.
- Automated Version Tracking: The system manages version numbering automatically. The first version defaults to 1, and subsequent versions increment by 1 automatically.
- Effective and Expiry Date Logic: When a new PRS Version is created, its Effective Date defaults to the current date, and its Expiry Date is null. The system simultaneously updates the previous version's Expiry Date to match the new version's Effective Date.
Flows and APIs
- Parsing Custom Attributes: The Get Connect API returns all custom attributes as a JSON map. To utilize these custom fields within a Salesforce Flow, admins must configure the flow to parse this JSON string into a usable object.
- Prompt Templates: When using prompt templates, custom fields can be generated as a JSON map in the output, which can then be processed and utilized downstream in flows.
Did this article solve your issue?
Let us know so we can improve!
