3

I run into a problem after deploying a package with a namespace. Found an error in a decision within a record-triggered flow.

enter image description here

The field "BC_Poder__c" should have received the namespace prefix in the destination org, but it didn't. I found it happens in every decision component around every flow in the package.

Yes I can fix the flow by changing the field in the resource to:

{!$Record.R2C2_002__BC_Poder__c}

Where the namespace prefix is "R2C2_002__", but I wouldn't expect this to be an error to be manually fixed for all flows (and who knows what else) every time I install the package in a brand new org.

Am I doing something wrong here? Any help would be greatly appreciated.

Thanks!

Improve this question
8
  • Is it a 1GP or 2GP?
    – Renato Oliveira
    Commented Aug 27 at 14:00
  • 1
    Flows have very brittle and non-standard namespace handling; the packaged flow must reference the (objects, settings and) fields (etc.) with the namespace prefix, otherwise stuff gets broken (like you found). Even then, we have an open support case around packaging translations where we have reference to a namespaced custom setting that goes wrong when we try to package the flow.
    – Phil W
    Commented Aug 27 at 14:09
  • It's a Managed 1GP package I'm trying to build.
    – Bernardo Lira
    Commented Aug 27 at 16:05
  • To Phil: the flow is not going to work in the source org. Should I consider editing each individual flow XML file?
    – Bernardo Lira
    Commented Aug 27 at 16:06
  • 1
    Make sure that the "source org" is a namespaced scratch org - make sure you adopt SFDX working practices with version control and scratch orgs.
    – Phil W
    Commented Aug 27 at 19:15

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .