* Salesforce Essentials *

Based on your situation, I can provide guidance on setting up a custom domain for your Experience Site. However, I should clarify that the documentation you're referencing ("Options to Serve a Custom Domain" and "Determine How to Serve Your Custom Domain") appears to be Salesforce-specific documentation rather than Copado documentation.

Your Situation Analysis

Based on what you've shared:

14 existing CNAME records for various integrations (Shopify, SendGrid, DigiCert, etc.)

No CDN currently in use for

WordPress hosting your main website

Enterprise Edition nonprofit org

Recommended Approach

Yes, your interpretation sounds correct. For your scenario, serving the domain with your HTTPS certificate on Salesforce servers is likely the best option. Here's why:

Why This Option Makes Sense for You:

CNAME Compatibility: Since you already have 14 CNAME records, adding one more for your Experience Site won't conflict with your existing DNS configuration. Each CNAME can point to different services.

No CDN Required: The Salesforce-hosted certificate option doesn't require you to set up or manage a CDN, which aligns with your current infrastructure.

Simplicity: This is the most straightforward approach for nonprofit organizations without dedicated DevOps resources.

High-Level Setup Process:

Create a subdomain for your surveys (e.g.,

)

Set up the temporary non-HTTPS domain in Salesforce:

Go to Setup → Digital Experiences → Settings

Configure your Experience Site with a temporary Salesforce domain first

This allows you to test functionality before DNS changes

Request the certificate from Salesforce:

Navigate to Setup → Digital Experiences → Domains

Add your custom domain (e.g.,

)

Salesforce will provide you with DNS verification requirements

Update DNS records:

Add the CNAME record pointing to Salesforce's servers

Add any TXT records for domain verification

These won't conflict with your existing 14 CNAMEs

Activate HTTPS:

Once verified, Salesforce will provision an SSL/TLS certificate

Your site will be accessible via

Important Considerations:

License Check: With your current licenses (Salesforce Integration, Analytics Cloud Integration User, Chatter Free, Identity, Chatter External, Sales Insights Integration User), verify that you have Experience Cloud licenses or Community licenses available. Experience Sites require specific licensing beyond what you've listed.

Subdomain vs. Root Domain: You'll likely need to use a subdomain (like

) since your WordPress site is already using the root domain.

Regarding Setup Guides:

While I don't have access to Copado-specific guides for setting up temporary non-HTTPS domains for Experience Sites (as this is primarily a Salesforce configuration task), Salesforce provides comprehensive documentation:

Salesforce Help: "Set Up a Custom Domain for Your Experience Cloud Site"

Salesforce Help: "Add a Custom Domain to Your Experience Cloud Site"

Trailhead: "Experience Cloud Basics" module

Next Steps:

Verify your Experience Cloud licensing with your Salesforce account team

Choose your subdomain (e.g.,

)

Follow Salesforce's domain setup wizard in Setup → Digital Experiences → Domains

Coordinate with your DNS administrator to add the required CNAME and verification records

Test thoroughly before directing users to the new domain

The temporary non-HTTPS domain is just an intermediate step during setup—once complete, your users will access your surveys via a fully secure HTTPS URL at your custom domain.

Would you like more specific guidance on any particular step in this process, or do you have questions about the DNS configuration with your existing CNAME records?

In this case, this is the unsupported but managed app MC4SF (Mailchimp for Salesforce). I would like to hang on to it as long as possible because it gives real-time info on contact subscription status that the replacement apps don't provide.   

I suspect I would not be able to modify a flow created as part of a managed package, and so far I have not found anything in the Apex triggers or classes that can be configured. Are there any workarounds, or are my only options to live with the alerts or uninstall it?

Solved. 

Tooling API vs Metadata API (Simple Explanation) 

Tooling API 

• Designed for developer tools (VSCode, Developer Console, etc.)
• Can access runtime information (e.g., ApexClass, LightningComponentBundle)
• Faster and easier for use in Apex
• Commonly used to query: Apex classes, LWC, Triggers, etc.

Metadata API

• Used for deployment and configuration.
• Accesses complete metadata (e.g., Object schema, Layouts, Flows)
• Needs Session ID with OAuth, not always available inside Flows or Agents.
• Cannot be queried easily using Apex in real-time – usually used via external tools or HTTP callouts.

Why You’re Getting Zero in Flow/Agent 

• When using Metadata API in Apex, it usually requires callouts with valid Session ID.
• In Flow/Agent, that Session ID is often null or restricted due to platform security.
• Tooling API inside Apex may not return results when invoked from Flow or Bot Agent due to permission scoping.
• Anonymous Apex (Dev Console) runs with full user-level permissions, which is why it works there.

Recommended: Use Tooling API with Apex (Simple Count Logic) 

Here’s working Apex code to count: 

• Lightning Web Components
• Flows
• Process Builders
• Custom Objects (Excluding Managed Packages)

 public class OrgMetadataCounter {    public class MetadataCountResult {        public Integer lwcCount;        public Integer flowCount;        public Integer pbCount;        public Integer customObjectCount;    }    public static MetadataCountResult getComponentCounts() {        MetadataCountResult result = new MetadataCountResult();        // LWC Count (Tooling API)        result.lwcCount = [SELECT COUNT() FROM LightningComponentBundle WHERE NamespacePrefix = null AND DeveloperName != null];        // Flow Count (Metadata API via Tooling)        result.flowCount = [SELECT COUNT() FROM FlowDefinitionView WHERE ProcessType = 'Flow'];        // Process Builder Count        result.pbCount = [SELECT COUNT() FROM FlowDefinitionView WHERE ProcessType = 'Workflow'];        // Custom Object Count (Standard + Custom, Excluding Managed Packages)        result.customObjectCount = [SELECT COUNT() FROM CustomObject WHERE NamespacePrefix = null];        return result;    }}

Hi @Mahogany Lore, MLIS ,

I managed to remove it a week ago in a Sandbox environment playing with the up/down left/right arrows. For some reason, I need to reproduce it right now and It seems not to work. Maybe I bugged it last time. 

https://www.reddit.com/r/salesforce/comments/xcycvx/set_another_field_as_name_field/