#Experiencebundle0 discutindo

What is the best practice to deploy Communities with DX and experienceBundle when the community uses CMS Topics ?

We have a component on the home page which displays the Top 5 trending articles for a given Topic.  The experienceBundle for the community holds a hard-coded topicId pointing this component to the tracked topic.

How should we deploy from sandbox to sandbox, since the Topic Id in the new sandbox will be different ?  Copying topics from source to destination will not help. Even if we create Topics manually, we can no longer use experienceBundle to deploy this community after a change request, because the source topicId does not match in the destination sandbox.

#experienceBundle #topic #DX

cc @Wade Wegner @Fabien Taillon @Salesforce DX 

@David Green FYI about to raise a new case for a new error

experiences/myCOMM1:sites.core.actions.UndoRedoException: Passed in position is out of range of the list its being inserted into. Property: sites.core.routes.Route.RenderList, position: 0, value: ViewId: null; TargetId: null; TargetSelector: null

Yesterday we added the ExperienceBundle to our Git repo so it is deployed each time we build the env or the overnight job runs its the test classes.

After it was added the deployment succeeded no errors, but then when the test run attempted to run it hit the above error with no further changes to the ExperienceBundle in GIT.  Note no publish has been conducted on the Experience either, not sure if that matters

So going to have to pull it out of our repo whilst this is investigated

I'm a beginner with CumulusCI, creating my first package as suggested in https://cumulusci.readthedocs.io/en/latest/unlocked_package.html

cci task run create_package_version --org dev --package_type Unlocked

I get this error message :

package.xml: You cannot install or upgrade a package that has a ExperienceBundle component. Remove components of ExperienceBundle type from the package.package.xml: You cannot install or upgrade a package that has a ExperienceBundle component. Remove components of ExperienceBundle type from the package.

Does this mean that CumulusCI does not support packaging #ExperienceBundle ? These are available in packages, according to the Metadata Coverage Report, I have already packaged them.

Are there other metadata which CCI cannot package ?

Is there a CCI-specific Metadata Coverage Report ?

So it seems that Summer 21 has created a new issue with using ExperienceBundle.

When trying to retrieve the ExperienceBundle from a Summer 21 (preview) instance sandbox, we get this error

problem: org.auraframework.throwable.quickfix.DefinitionNotFoundException: No COMPONENT named markup://c:suburbSearch found : [markup://c:xxxx_HelpAssistanceRegister, markup://c:xxxx_HelpAssistanceRegistration]

FYI - The component does exist (but is LWC vs the other 2 which are AURA) and does function as expected.

Salesforce Support has indicated that it is under investigation, but on a case for another issue.  I am wondering if anyone knows if there is a known issue for this?

Thanks

Tony

cc:@David Green @Geno Mathew 

When will ExperienceBundle metadata be good to use?

Seem to be having no end of issues trying to use it for deployment with errors like

ERROR deploying ExperienceBundle experiences/xxxxx: An unexpected error occurred. Please include this ErrorId if you contact support: 685582182-194080 (-1752371813)

Getting strange error trying retrieve 'Experience Bundle'

"messages": [

    {

      "fileName": "unpackaged/ExperienceBundle",

      "problem": " Something is wrong with the viewType in mySite1/views/test1.json. Check the value and try again."

    }

I have even deleted the page, but it still gives the same error.  Any idea's?

Is there an ETA possible on bugfix for deploying experienceBundle + Lightning components together? https://success.salesforce.com/issues_view?id=a1p3A0000003vc8QAA

Extremely painful right now to deploy and reverting to a blob site metadata would be really disappointing..

@Salesforce DX

So starting to look at moving to the ExperienceBundle for our community

Firstly we got this error

ExperienceBundle Metadata API doesn't support the template of myCommunity

That I believe this was due to not updating the community, after updating the community we got a new error that I have no idea about.

Entity type 'ExperienceBundle' is not available in this organization

We have the community enabled for ExperienceBundle and am using a package version of 48 with a Spring 20 org

Any ideas?

@Geno Mathew  @David Green