Deployment issue about sfdc-lead-conversion-record-types HOT 4 CLOSED

Hi @trilame, thanks for reporting the issue. When I get a chance to dig into this I'll follow up.

from sfdc-lead-conversion-record-types.

Hi @trilame, I've updated the code so the tests pass. You may want to check out my latest blog post on using Process Builder for a non-code solution: https://douglascayers.wordpress.com/2016/06/26/advanced-lead-conversion-with-process-builder/

from sfdc-lead-conversion-record-types.

Hello,

It works very well now! Thanks a lot for all of this.

I also checked the solution through the process builder, which looks great: maybe I'll try this one on another instance.

from sfdc-lead-conversion-record-types.

Hi @trilame, I think I see the issue. The test code is looking for specific record type names which likely don't ever exist in other people's orgs. I believe this can be improved by just dynamically grabbing a record type from each of the objects so that existing record types in a customer's org are used and the test should pass. But... an even better solution is to use Process Builder!

Before Process Builder was released my only option was to go this route with apex code. I will write up a blog post how to do it with Process Builder so you don't have to wrangle with all this code =)

Thanks,

Doug

from sfdc-lead-conversion-record-types.