search

SalesforceCommerceCloud / b2c-crm-sync

... a contemporary perspective on how to integrate B2C Commerce and the Salesforce Customer 360 Platform to power frictionless customer experiences in the B2C domain.
https://salesforcecommercecloud.github.io/b2c-crm-sync/
BSD 3-Clause "New" or "Revised" License
64 stars 47 forks source link

Problem with manual Deployment of Metadata since Spring '22 Update #121

Open freytagt opened 2 years ago

freytagt commented 2 years ago

Starting from this week (first time noticed in 8th of February) we are encountering problems deploying metadata in sandboxes where Spring 22' release was applied. The very same package containing same metadata did not have any issues the week before (6th of February) in sandboxes where Winter 21' was the current release.

The problem occurs upon deploying UI components, like Record Pages, List Views, Layouts and Tabs. Also, Picklists that use Global Value Sets and Static resources. While issues with Global Value sets and Static resources was resolved by deploying separately Global Value Set before Picklist field that references its values and adding missing tags to Static Resource .xml files the rest of the components still are failing for unknown reasons which cannot be identified. I want to imply again that week before there were no issues with the very same components in the same sandboxes.

According to Salesforce Status page the Sandboxes received Spring 22' release on January 8th. Before this we successfully managed to deploy the same metadata in other Sandboxes which are bound to receive Spring 22' release on February 12th, but already this week seems to have some parts of it (can be noticed by the spring loading icon) and now after re-validating the same metadata there it has same issues.

Common errors that we face:

All of the errors displayed have similar message that component (either record page, custom field or layout) was not found even though all the components actually are part of the package file and had no issues before.

Did anybody encounter the same problem or has an idea how to solve it?

jbachelet commented 2 years ago

Hello, Thank you for posting this issue. Can you please provide the error shown by SFDX when trying to deploy?

Thanks!

freytagt commented 2 years ago

Hey @jbachelet, thanks for reaching out.

Actually we don't use the SFDX commands.

We can't due to a deployment process which needs to be as packages and go over Bitbucket repositories etc.

We are deploying the Metadata in a package and need to do the post deployment manually.

Can you say if this is possible and/or how to do it?

jbachelet commented 2 years ago

Okay. My goal was to be able to get the full error behind your failed deployment. Without this, it is hard to help you more here.

freytagt commented 2 years ago

Hey @jbachelet,

I know but thanks anyway. Actually it seems that this belongs to a problem when you want to zip a package on mac.

But can I ask you anyway: are there any steps to deploy it to production environment? What is the "normal" process and what do I need to consider when I am deploying it manually?

jbachelet commented 2 years ago

Hello,

There is nothing in the CLI commands within this repository that is intended to deploy to production. The CLI comands could help you to generate the connected-app, named credentials, csp ... and B2C services XML files, but then I do recommend you to use your actual way of deploying metadata to the Core org to also deploy b2c-crm-sync.

avarma4213 commented 1 year ago

Hey @jbachelet,

I know but thanks anyway. Actually it seems that this belongs to a problem when you want to zip a package on mac.

But can I ask you anyway: are there any steps to deploy it to production environment? What is the "normal" process and what do I need to consider when I am deploying it manually?

Hi, we are also facing the same issue. Did you find any resolution for this?

thanks