Account Engagement Automates... Record Creation

Thanks, Rene! Following up here from our exchange in the event someone sees the review or the issue listed here and what your resolution was. Rene found the solution to this error in his org where some unorchestrated record triggered flows that were also triggered at the same time as the Create Account Contact flow along side some validation rules.

Thank you Amanda.

Thanks amanda!. we can locate errors now.

Hi Nitisha, you have a couple options. In Account Engagement Settings you should have a sub menu item for 'External Action Errors' that you can review for any errors arising at the external action step. Otherwise, if no external action errors, then the external action ran and instead you can run debug logs in SF for the flow itself that you are triggering.

Hi Amanda, Just wondering how we debug on the issues with app, when the record is not created from MCAE to salesforce.

Thanks Amanda. that works for all data types.

Hi Nithisha, the string is just the way the value is consumed for the schema even if the value was inputted as a picklist, for example. Can you email me our team with more detail and perhaps some screen shots of where you are referencing in the process to for us to better assist? jfassett@salesforce.com, amanda.benjamin@salesforce.com, and cbayerle@salesforce.com

Thanks so much for taking the time to not only play with the app but leave us a review. We appreciate the feedback and hope the app continues to help with your project needs!

Circling back to Livia's comment/question with the response our team had for future reference and for others' as well. Boolean is not a valid type in the External Action schema because boolean isn't a valid data type for the Account Engagement (Pardot) database. When you map a checkbox (boolean) field on the Salesforce Lead or Contact object to Account Engagement, you usually create a radio button prospect field in Account Engagement with 'true' and 'false' as the available values. So the Account Engagement database is technically holding a string of 'true' or 'false' in that field for each prospect. If you change the data type for the input variable ActiveCheckbox in your Flow to Text (a string), you'll be able to pass 'true' or 'false' as text through the merge field to the Flow. In your Flow, the variable will technically hold text (a string), but you should only ever receive a 'true' or 'false' text value from Account Engagement so you should be able to handle it like a boolean in your Flow. (You might create a path in your Flow just in case you ever receive something other than 'true' or 'false' just to be safe.)

Hi Livia, would you mind sending an email to us instead? It'll make for an easier way to collaborate and hopefully help solve any issue you have. Feel free to email jfassett@salesforce.com, amanda.benjamin@salesforce.com, and cbayerle@salesforce.com with the question and perhaps any additional screenshots or info you can provide on what you are seeing that would be helpful. Thanks!

Yeah, Bevy may not. We were just troubleshooting what you both would have in common that may somehow confuse Quip that you may have a Salesforce login to use and prompt you for it. I'm glad you were able to get into it. We do appreciate the feedback on your troubleshooting results, and we will go back to the Labs team and see if they have run into this and any recommended next steps. Thanks again! If you run into any questions or issues, please reach out to us. We have a contact email on the listing.

I don't believe Bevy has anything to do with it as I haven't been logged in there for several weeks. I tried Edge browser (which I never use) and had same issue. Tried link with Firefox next and was able to open it successfully so will use that as my workaround for now. I believe you that the Quip document is set to public, but since this same issue happened on your demo last week (great demo by the way!) and on multiple browsers and incognito for me today it leads me to believe there is still some issue with the link. Just an FYI so that doesn't become a barrier for people checking this out. Speaking of - since I have the user guide open in Firefox now I'm going to start checking out the app, thanks for your work in making it.

If you are logged into Bevy, suggest being logged out so that your email to log into it isn't confusing Quip into thinking you do have a Salesforce login. We attempted to put it into a google doc, but settings don't allow us to share out of Salesforce. We'll look further into this and get back to you again. In the meantime, perhaps clear cookies or try other browsers? It is confirmed publicly accessible to people without a Salesforce email, so we just need to figure out why you are getting the prompt.

Thanks for checking on this. I just tried the incognito window as well as logging into Bevy as you recommended, still got same result of being prompted for @salesforce.com email required for login.

Confirmed the link shared is the right one with the sharing settings open to the public. We had another User Group leader who experienced what you are. Is it possible you are opening it while logged into Bevy that's suggesting you need to log in with a salesforce address? Perhaps try in an incognito window or log out if you are logged into Bevy?

Hi Jim, thanks for the note. The Quip is set to be shared externally to users outside of Salesforce, and we know others have had success reviewing it. We'll take a look at the Quip link and follow up.