Skip to main content
Topics#ExperienceBundles

#ExperienceBundles0 discussing

Ask a question...
Tobias Thiel (Lead Architect Salesforce at KUKA AG) posted in * Experience Cloud *
Mar 30, 2021, 9:56 AM

Hello all,

what are your best practice recommendations for #Continuous Deployment with #ExperienceBundles enabled? The experience bundle tree with all the details like views shows up in the dev tools but in our deployment tool Copado I only get the experience bundle as a whole. Is this a limit of the tool or the API?

Deploying the whole community each time in one piece although only a specific page update is needed seems like a high risk for a larger community. I have hoped that the switch to ExperienceBundles would give admins the chance to deploy on a more granular level like one single page including translations and component settings.

Thanks

Tobias

#deployment

2 comments
Write a comment...
0/9000
Reinier van den Assum (Senior Technical Consultant / Developer at Deloitte) posted in CMTD
May 18, 2020, 1:04 PM

Hi @Denny Chandra , are you familiar with the issue when deploying a Community Page which contains one or multiple CMTD Enhanced Related Lists using ExperienceBundles?

 

I'm trying to migrate deployments from SiteDotComSites to ExperienceBundles, but face the following error:

Error: attribute [layoutType]: Attribute value is not valid 1. Check your file and try again.

 

Salesforce Support acknowledges the issue (they can reproduce), but mention the CMTD package is not an official Salesforce Product and therefore not supported by Salesforce Support.

 

In my perspective the issue lays in the deployment tool which is a product of Salesforce, but I'd like to align whether you share that thought.

 

How to reproduce:

1) Add a CMTD Enhanced Related List to a Community Page & Publish

2) Via Workbench fetch the ExperienceBundle (retrieve)

3) Download the package and Deploy it using Workbench to the same environment (deploy)

 

Then the above error is shown.

My own thought: layoutType is stored in the .json as Integer, but should represent a Picklist value, wouldn't it make sense to store this as a String (if modifiable). When manually changing 1 > "1", the same issue remains.

 

ExperienceBundle component (so in the experienceBundle/[community]/views/[page].json:

{

    "defaultNumberofRecordsToDisplay": 10,

    "defaultRecordType": "",

    "displayType": "List",

    "filter": "Type__c = 'Dealer' AND Available__c = TRUE",

    "iconName": "standard:person_account",

    "layoutType": 1,

    "maxNumberofRecordsToDisplay": 250,

    "newRecord": "",

    "objectAPIName": "Dealer_Contract_Allocation__c",

    "parentField": "Dealer_Contract__c",

    "relatedListName": "Dealer_Contract_Allocations",

    "showHeader": true,

    "showMenuAction": false,

    "showRefreshButton": true,

    "sort": "Available__c DESC, Position__c ASC",

    "title": "Available slots"

}

 

Hope you would be able to help me out here, or make sure we can make the case at Salesforce this is due to their implementation of ExperienceBundles and therefore a fix should be deployed.

 

Looking forward to your response and thanks in advance!

Kind regards, Reinier

N.B. I'm currently running at the latest package version.

5 comments
  1. Reinier van den Assum (Deloitte)
    May 25, 2020, 10:24 AM
    @Denny Chandra

    In my perspective this is indeed a bug caused by a conflict on the ExperienceBundle export-engine of Salesforce having the layoutType always return as 1. This is independently of whether or not the component itself (your Managed package) might have provided any other value.

    I've asked Salesforce to keep me posted on the progress and will let you know when I have any update. For now maybe good to share somewhere for all who would like to migrate to ExperienceBundles, but face this challenge.

Write a comment...
0/9000