3

ApiV47 (Winter'20) does not support BusinessProcess metadata anymore. In order to have RecordTypes on Lead you need to have BusinessProcess. So we do have a few. So far we deployed the code using SFDX unlocked packages. However this doesn't work any more as we get "Unsupported metadata type: [BusinessProcess]" error. If the BusinessProcess is removed from the repo then the Lead recordtypes have missing dependencies. If the Lead recordtypes are removed too then the Apex Classes have missing dependencies. So this isn't a viable solution.

Any known workaround/solution?

(Yes, the classes can be rewritten as to have the SOQL queries in strings with "RecordTypeId" clauses added dynamically so the code can be deployed to empty scratch orgs without test failures. However this is more like dailywtf's turf. I'd avoid this at all costs.)

Any comments are welcome.

3
  • We are also hit hard by this. I don't remember where this was documented in release notes. Did you create a ticket to SF asking about reasons for this?
    – akarnid
    Commented Oct 9, 2019 at 14:04
  • @akarnid: Yes, we created a ticket to SF. So far we only got a pointer to developer.salesforce.com/docs/metadata-coverage/47 which shows this is a feature, not a bug... Still waiting for a real explanation/workaround from them. In the meantime I thought maybe someone has a solution already here.
    – RetekBacsi
    Commented Oct 9, 2019 at 14:32
  • Yeah we are getting that WorkflowRule, PathAssistant and BusinessProcess are also not supported any more.
    – akarnid
    Commented Oct 9, 2019 at 16:35

2 Answers 2

2

It's a known issue that will be corrected. See https://success.salesforce.com/issues_view?Id=a1p3A000001Sa3n

1
  • Great news, thank you!
    – RetekBacsi
    Commented Oct 14, 2019 at 4:30
1

you can try to build your package with the flag --apiversion and use previous api version

https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_reference.meta/sfdx_cli_reference/cli_reference_force_package.htm

2
  • we have tried that and it is also not working, we have tried various combinations and still getting errors when trying to create package version...
    – L.Skuba
    Commented Oct 10, 2019 at 11:19
  • Unfortunately this doesn't work for us either. We have already tried this, just forgot to mention in the original post.
    – RetekBacsi
    Commented Oct 10, 2019 at 12:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .