1

Today what we do is delete the LWC from Flexipage with a predeployment manual step and then it gets deployed through the package with update designer attributes.

Is there a way to skip that?

3
  • 1
    In theory, if the name in the flexipage and LWC are in the same deployment, it should work. If not, I don't think there's a way to fix this (but you could automate the first deployment, too).
    – sfdcfox
    Sep 29 '21 at 16:36
  • curious on the automation?
    – jini
    Sep 29 '21 at 16:39
  • 1
    You can deploy the flexipage without the designer attribute set in one deployment, then a second deployment with the flexipage using the new attribute with the LWC code that exposes it.
    – sfdcfox
    Sep 29 '21 at 17:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.