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.