#CRM Configuration52 diskutieren mit

Hi Lisa, 

The short version: this is a limitation of standard quote templates rather than something misconfigured on your end, and the reason it looks arbitrary is that the character count isn't counting what you see. 

Rich text area fields store HTML behind the scenes — paragraph tags, line breaks, bold, font styling, all of it. Character limits in quote templates count those hidden formatting characters along with the visible text. So your 195 visible characters plus the markup wrapping them is hitting the renderer's internal ceiling. That's also why the cut-off point moves around between records: content with more formatting truncates sooner, plain content goes further. Your field's 3,000 character limit governs what Salesforce will store, not what the PDF engine will render. 

A quick way to confirm it: take the same content, strip all formatting so it's plain unformatted text, paste it back in and regenerate the PDF. If it runs noticeably further before cutting, markup overhead is your culprit. 

On what to do about it: 

If you can live without formatting, switching to a plain Long Text Area removes the markup overhead entirely and gets you meaningfully more usable characters, with a predictable cut-off instead of a moving one. 

If you need the full 3,000 characters per line item, standard quote templates aren't going to get you there. The usual routes are a Visualforce quote PDF template, where you control the rendering, or a document generation tool — S-Docs, Conga, Nintex DocGen and similar all handle long per-line-item text properly. More work up front, but it's the only way to stop fighting the limit. 

One thing worth ruling out first: check field-level security on that field for the profile generating the PDF. If a field isn't fully visible to the user, it can render oddly or not at all on template PDFs. Less likely given you're seeing partial text, but cheap to verify. 

Hope that helps. 

Lisa — also worth saying: if the extended line item info is genuinely long, it may be worth asking whether it belongs on the PDF as a line item column at all, versus a terms or details section further down. Line item columns are narrow by design and long text tends to look cramped even when it does render. 

This really resonates.

One thing I've noticed is that most benchmarks focus on whether an AI agent can produce the right answer.

In production, that's only one piece of the puzzle.

The bigger questions become: 

• Can it follow business policies? 

• Can it recover from failures? 

• Can it handle long-running workflows? 

• Can you explain every decision it made?

Curious to see how the industry evolves over the next few years.

Hi, 

It sounds like you're encountering two separate issues. 

1. Marketing Performance Intelligence installation (template_requirement_sdm error)

This step is part of the automated provisioning process, and there isn't any public documentation that explains how to resolve the template_requirement_sdm error specifically. In most cases, this indicates a backend provisioning or installation issue rather than a configuration problem in your org. 

I recommend:

• Verifying that your Marketing setup and Data Cloud provisioning have completed successfully.
• Reviewing the official Salesforce Foundations Marketing setup guide to ensure all prerequisite steps have been completed.
• If the error persists, open a Salesforce Support case, as they can review the installation logs for your org.

Resources:

• Salesforce Foundations Marketing Setup: https://help.salesforce.com/s/articleView?id=base_setup_marketing.htm&type=5 (Salesforce)

2. Email Builder Lite access for users

The error about needing a CMS Workspace and Email Builder Lite access is usually caused by missing permissions or workspace contributor assignments.

A few things to verify:

• The users have been added as Workspace Contributors to the Marketing Workspace (not just granted access to the CMS Workspace).
• The appropriate Marketing permission set (or Permission Set Group) has been assigned. Depending on your org and release, Salesforce may use Permission Set Groups instead of individual permission sets.
• Confirm that the Marketing Workspace has been created and shared correctly.

Helpful documentation:

• Marketing Workspaces and Workspace Contributors: https://help.salesforce.com/s/articleView?id=mktg_content_workspaces.htm&type=5 (Salesforce)
• Salesforce Foundations Marketing Setup Guide: https://help.salesforce.com/s/articleView?id=base_setup_marketing.htm&type=5 (Salesforce)

If both of these checks look correct and you're still seeing the same behavior, I'd recommend opening a Salesforce Support case. Since the template_requirement_sdm installation error and missing permission sets can both be related to org provisioning, Support can verify whether everything has been provisioned correctly in the backend. 

Hope this helps.