• Craig Woodman
  • NEWBIE
  • 15 Points
  • Member since 2018

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 7
    Questions
  • 16
    Replies
Very similar here to another post that I made about web to lead on before save flow triggers. I was wondering if a before save flow would trigger on an Opportunity record created by lead conversion. I did not see any information, so I figured I would do my own test, by updating the description field on an Opportunity with a before save flow.

Then, I converted a test lead, and sure enough, the description was updated.

This can be a great behavior, but one that everyone needs to be aware of, as it works the opposite of process builder, which will NOT trigger when an Opportunity is created by lead conversion.

Just something to be aware of.
I had a question, but answered it on my own. So since my search didn't reveal anything, I figured I would post it here in case anyone else is looking.

Does a Before Update flow (or one that is triggered by record create or change, that saves before the record is updated) work with lead creation by web-to-lead?

I had not seen this in any documentation. And searches didn't show anything. So I figured I would do some tests on my own.

I set up a test flow to write text to the Lead Description field on creation, that says "The before update flow worked!!!" I then went to the website, downloaded a catalog, and checked the description field. The text was written, with no delay to the web to lead record.

My use case for this is changing the record type automatically on a web to lead record, which passes in certain values. It works perfectly!

I hope that this helps anyone who is looking for this information!
I have run into some situations where a flow screen component will not display with the conditional visibility.  I have found this with using the toggle component (to make a display text component visible) and also with the lowly checkbox.  The components set to conditional visiblity just do not show.  With the checkbox, I had it the affected component show on the first time through the flow, and then didn't on the second.

Any thoughts?
I am working with an Org, and I have used the LeadOrContactID standard field on Campaign Member as a convinient lookup to a campaign member without having to have a decision element to determine which type of ID is being used, and to do a seperate lookup.

I have this on one flow that is around 10 months old, and has been working perfectly.  I needed another flow on Campaign Member yesterday, so I used it again.  I completely tested and it was working fine as of yesterday end of day.

At about 10:30 this morning, I began getting users emailing about errors with records that involved both of these flows that could not save because of an error.  When digging in to it, I found that the Lookup portions of the flow were failing, becasue the flow could not find a Campaign Member record when using the LeadOrContactID as one of the criteria.

So I figured I would create a custom LeadOrContactId field, using a formula field. I verified on the page layout that the field is returning the correct lead or contact ID.  But the flow still fails, for the same reason - It looks like it cannot be used as the criteria for lookup.

I re-crafted both flows with decision elements to take care of this.

Any idea why both flows would quit so suddenly?
Hello,

I ran into an error with a lead converting - just the generic "Salesforce Error" message.  It was not any of my automations failing as I was receiving no application error.  

I tried a few different things, but then I opened a developer console to capture a debug log.  After digging through, I found this error message:

09:04:41:114 EXCEPTION_THROWN [1579]|System.DmlException: Update failed. First exception on row 1 with id 00T2M00003e5MzGUAU; first error: FIELD_INTEGRITY_EXCEPTION, Assigned To ID: id value of incorrect type: 00G2M000003OvngUAC: [OwnerId]

When I went into the task with the ID listed, I noticed that it was owned by a Queue.  Upon changing the two tasks owned by Queues on the lead to a user, the lead was able to convert.

Apparently, we can't convert a lead that has tasks owned by a queue?

Has anyone else run into this?

Craig
I have run into a problem with component visibility using the toggle button feature in flow screen components.  When using the native Salesforce toggle button, I cannot set the visibility components based on the value of the toggle button.

I have established a toggle button titled togShowHide.  I have set a component visibility based on the following:

User-added imageThe problem is, the toggle does not do anything when activated or deactivated to change this component visability - and the visibility is always OFF.

When I reversed everything, making the toggle button active (true) by default, and setting components to display when the value was true, the components will display.  

What it looks like to me, is that the flow components will only allow you to filter the visibility by a variable or other resource that is TRUE.  It just doesn't work with a false value.  In fact, the component won't display at all.

HOWEVER, when I do the same actions using a checkbox, I can filter a flow screen component to display either on a TRUE value or a FALSE value.

Is this a bug, or normal behavior for the toggle component?
Hi everyone,

I opened a case with Salesforce, and they suggested I post it here.  I have a flow that I developed that is used for a visitor log in on an iPad at a kiosk.  The flow asks for name, phone, nature of business, etc, and writes these to a "Visitor Log" object.  My plan is to incorporate with other elements as we go.

I run this flow with an iPad, running the Salesforce 1 mobile app.  I utilize Apple's guided functions, not allowing a click in areas that they don't need to be clicking in the Salesforce 1 app.  All was working well at first, but the flow will stop working after a time period.  Specifically, the flows navigation buttons stop working.  You can still click in the screen and edit, but the navigation buttons stop advancing or going back.

After trying all of the standard things (restart iPad, hard reset, etc.), as
I was using a custom flow screen component for navigation buttons, so I figured maybe that was the issue.  I removed the FSC, and went back to standard navigation buttons.  The issue persists.  It is usually after several hours, and makes it unusable for the purpose.

I solved the problem by removing all lightning components from the flow (ugh... visually bad!) and distributed the flow inside of a visual force page, and through a salesforce site.  No problems at all.  The flow continues to function even after several weeks.  I am still using the Guided functions on the ipad to prevent navigation off of the page.

If I could use the lightnging screen components and deliver the flow in lightning run time doing this, I consider the problem solved!  But I can't.  I opened a case with Salesforce, and they said that the issue was with flows, so I needed to post here.  I don't think that it is, because the flow is functioning perfectly inside of the VF page on a Salesforce Site.

Anybody have any ideas on why this could be?
Very similar here to another post that I made about web to lead on before save flow triggers. I was wondering if a before save flow would trigger on an Opportunity record created by lead conversion. I did not see any information, so I figured I would do my own test, by updating the description field on an Opportunity with a before save flow.

Then, I converted a test lead, and sure enough, the description was updated.

This can be a great behavior, but one that everyone needs to be aware of, as it works the opposite of process builder, which will NOT trigger when an Opportunity is created by lead conversion.

Just something to be aware of.
I had a question, but answered it on my own. So since my search didn't reveal anything, I figured I would post it here in case anyone else is looking.

Does a Before Update flow (or one that is triggered by record create or change, that saves before the record is updated) work with lead creation by web-to-lead?

I had not seen this in any documentation. And searches didn't show anything. So I figured I would do some tests on my own.

I set up a test flow to write text to the Lead Description field on creation, that says "The before update flow worked!!!" I then went to the website, downloaded a catalog, and checked the description field. The text was written, with no delay to the web to lead record.

My use case for this is changing the record type automatically on a web to lead record, which passes in certain values. It works perfectly!

I hope that this helps anyone who is looking for this information!
I have run into some situations where a flow screen component will not display with the conditional visibility.  I have found this with using the toggle component (to make a display text component visible) and also with the lowly checkbox.  The components set to conditional visiblity just do not show.  With the checkbox, I had it the affected component show on the first time through the flow, and then didn't on the second.

Any thoughts?
I am working with an Org, and I have used the LeadOrContactID standard field on Campaign Member as a convinient lookup to a campaign member without having to have a decision element to determine which type of ID is being used, and to do a seperate lookup.

I have this on one flow that is around 10 months old, and has been working perfectly.  I needed another flow on Campaign Member yesterday, so I used it again.  I completely tested and it was working fine as of yesterday end of day.

At about 10:30 this morning, I began getting users emailing about errors with records that involved both of these flows that could not save because of an error.  When digging in to it, I found that the Lookup portions of the flow were failing, becasue the flow could not find a Campaign Member record when using the LeadOrContactID as one of the criteria.

So I figured I would create a custom LeadOrContactId field, using a formula field. I verified on the page layout that the field is returning the correct lead or contact ID.  But the flow still fails, for the same reason - It looks like it cannot be used as the criteria for lookup.

I re-crafted both flows with decision elements to take care of this.

Any idea why both flows would quit so suddenly?
Hello,

I ran into an error with a lead converting - just the generic "Salesforce Error" message.  It was not any of my automations failing as I was receiving no application error.  

I tried a few different things, but then I opened a developer console to capture a debug log.  After digging through, I found this error message:

09:04:41:114 EXCEPTION_THROWN [1579]|System.DmlException: Update failed. First exception on row 1 with id 00T2M00003e5MzGUAU; first error: FIELD_INTEGRITY_EXCEPTION, Assigned To ID: id value of incorrect type: 00G2M000003OvngUAC: [OwnerId]

When I went into the task with the ID listed, I noticed that it was owned by a Queue.  Upon changing the two tasks owned by Queues on the lead to a user, the lead was able to convert.

Apparently, we can't convert a lead that has tasks owned by a queue?

Has anyone else run into this?

Craig
I have run into a problem with component visibility using the toggle button feature in flow screen components.  When using the native Salesforce toggle button, I cannot set the visibility components based on the value of the toggle button.

I have established a toggle button titled togShowHide.  I have set a component visibility based on the following:

User-added imageThe problem is, the toggle does not do anything when activated or deactivated to change this component visability - and the visibility is always OFF.

When I reversed everything, making the toggle button active (true) by default, and setting components to display when the value was true, the components will display.  

What it looks like to me, is that the flow components will only allow you to filter the visibility by a variable or other resource that is TRUE.  It just doesn't work with a false value.  In fact, the component won't display at all.

HOWEVER, when I do the same actions using a checkbox, I can filter a flow screen component to display either on a TRUE value or a FALSE value.

Is this a bug, or normal behavior for the toggle component?
Hi everyone,

I opened a case with Salesforce, and they suggested I post it here.  I have a flow that I developed that is used for a visitor log in on an iPad at a kiosk.  The flow asks for name, phone, nature of business, etc, and writes these to a "Visitor Log" object.  My plan is to incorporate with other elements as we go.

I run this flow with an iPad, running the Salesforce 1 mobile app.  I utilize Apple's guided functions, not allowing a click in areas that they don't need to be clicking in the Salesforce 1 app.  All was working well at first, but the flow will stop working after a time period.  Specifically, the flows navigation buttons stop working.  You can still click in the screen and edit, but the navigation buttons stop advancing or going back.

After trying all of the standard things (restart iPad, hard reset, etc.), as
I was using a custom flow screen component for navigation buttons, so I figured maybe that was the issue.  I removed the FSC, and went back to standard navigation buttons.  The issue persists.  It is usually after several hours, and makes it unusable for the purpose.

I solved the problem by removing all lightning components from the flow (ugh... visually bad!) and distributed the flow inside of a visual force page, and through a salesforce site.  No problems at all.  The flow continues to function even after several weeks.  I am still using the Guided functions on the ipad to prevent navigation off of the page.

If I could use the lightnging screen components and deliver the flow in lightning run time doing this, I consider the problem solved!  But I can't.  I opened a case with Salesforce, and they said that the issue was with flows, so I needed to post here.  I don't think that it is, because the flow is functioning perfectly inside of the VF page on a Salesforce Site.

Anybody have any ideas on why this could be?
Our company currently has Riptide Popup Alerts in our Salesforce Classic org. We are in the process of re-platforming and are being advised that this functionality is not available in Lightning. Is this true, and if it is, is there a solution in place at all for a Lightning org without manually coding the pop-ups?
  • April 05, 2019
  • Like
  • 0