Skip to main content

#CMS Workspace0 人がディスカッション中

It has just come to my attention that Account Engagement users are unable to utilize existing CMS files with the new Email Builder Experience. I have been working with Salesforce Support to resolve an initial issue accessing the new email experience but once that was resolved, it was obvious all of the files (years of uploads) in our CMS are not compatible with the new email experience. Below is the response from Support:

 

Thanks for reaching out to the Account Engagement (FKA Pardot) Support Team.

 

I am Vinay from the Salesforce Account Engagement support team. I have taken ownership of your case and happy to look into this case further for you.

 

From the old comments and issue, I understand that you are looking to utilize old already existing CMS channel file with newly launched New content builder option experience.

 

I double checked for you with advanced team including product engineering team, As per current product design, New builder is compatible with '(Content Workspace for Marketing Cloud Account Engagement)' connected workspaces. which are 'ENHANCED' in nature.

 

So, As of today, You would potentially have to upload all those images used in previous CMS Workspace in order to use in NEW experience.

 

I know this is not super helpful, But this new option gives option to users to familiarize themselves with the new builder and its capabilities while being able to use it for MCAE list email sending through Salesforce.

 

But in Future, This would of course be made more compatible for seamless CMS content experience!

 

This is an acceptable answer but what I find unacceptable is the fact that the Email Experience is not compatible with existing CMS files. This will take countless hours to re-upload and re-categorize our files, as I imagine I am not alone in this frustration. This alone will keep me from using the new email builder experieince.

 

If you happen to come across this, I wanted you to be aware, there seems to be no workaround other than taking the time, you've already spent, to re-upload your CMS files.

 

#AccountEngagement  #New Email Template Builder  #Lightning Email Builder  #CMS Content  #CMS Workspace

0/9000

Would you like to take a 10-15 minute survey about Salesforce CMS Schedule Publishing and Cross Workspace Sharing? 

 

Your input in this survey is highly appreciated and valuable to us. It's designed to be quick, taking less than 15 minutes. We're focusing on two key areas: understanding how you use the schedule publishing feature in CMS and gathering insights on sharing content across workspaces. Your feedback will help us enhance Salesforce CMS to align better with your needs. 

 

As a thank-you, we're offering a $15 Tango gift card for your participation.  

 

Here's the survey link, and it'll open to 16 participants until 11/14/2023 11:00 PM ET. Thank you in advance for joining us in this effort!

#CMS #User Experience #CMS Workspace

0/9000
Sarath Dodda (Salesforce の tr)Sanjna Patyal のフィードに投稿

Hello Sanjna - Thank you and really appreciated for sharing recording for  ** Experience Cloud Release Management** 

 

 Couple of questions on CMS Workspace and deployment. Right we are blocked with below issues - 

1. Can CMS collections in content management deployable from one org to another org? if yes, please share ref documentation.

2. We have created CMS content in workspace and try to import into another org. But only contents ( flex documents, images) are deployed not the folder structure we created in source org. Is there a way to deploy Content along with folders created in CMS workspace?

3. When deploying community using MAD Api, the referencing Hero images in community builder are linked - We had to link manually from Asset library ( Even though image available in CMS workspace content) ?. 

 

Thank you !! 

2 件のコメント
  1. 2021年5月3日 14:25
    I am not sure about your last question. Could you please post your question to the * Experience Cloud * group and @ mention me. I will get someone from the team to answer your question. Thanks!
0/9000

Hello Pardot Power Users, I need your help!

I'm setting up the new Pardot email builder and am almost at the end, when I ran into an unexpected problem. Where we are so far:

1. CMS workspace and channel is set up.

2. Email Content object is in place

3. Domain is set up as per the instructions I was able to find.

4. The domain was added to the channel, and recognized and added in Pardot Email Setup menu.

The problem:

In the email builder I go to add an image from the cms. I can see the image just fine in the cms window, but when I pull it into the template, I get a broken image icon.

I've been around the moon and back trying to solve this one, so if any Pardot/CMS trailblazers out there might be able to help me out, that'd be incredible!

Thanks in advance

19 件のコメント
0/9000

Anyone has seen this before? Content item disappears from CMS Workspace, but it's still on community page.

 

Steps:

  • New content item was created in CMS Workspace and published to community.
  • In Content Management, the content item is showing and content-slug is used on CMS Single Item component.
  • Content item is not showing on CMS Workspace anymore
  • Community is still showing the content, because it was "saved" under Content Management.

Question: how do I bring the content item back to CMS Workspace?

11 件のコメント
0/9000

Hi everyone!

 

Just A quick question.

One of our client really wants to shut down his current site in favor of a Salesforce Community with CMS content, but he needs to import at least a few hundreds articles and old news.

 

Does the CMS workspace allow massive import of content somehow?

If it doesn't, is this a planned roadmap feature?

It's really important for us to know this.

Thanks

 

#Salesforce CMS #CMS #Community Cloud #CMS Workspace 

2 件のコメント
0/9000

Hi All,

Does anyone know reasons why when creating a CMS workspace, contributor roles is greyed out. Cannot find any setting or answers on this.

18 件のコメント
  1. 2019年10月18日 21:17
    To close the loop on this: there is a setting that needs to be enabled by Salesforce Tier 3 Support in order to configure CMS Workspaces.
0/9000