Solved

WHY SFDC Account ID Mandatory mapping in AO even though if it's intended for internal user

shiv_kumar_katiyar
Rank
Userlevel 4
Badge +1
I have a request wherein customer is trying to send a survey to internal user via Advanced Outreach. But participant list isn't populating because there is no account associated to it.



So we tried to workout this problem by creating a dummy account and adding it in the second step of AO participant config-



https://cl.ly/090L0T1N3r0S



Checked internally and got the same solution, so posting this case here to check if there is any possibilities of removing Account ID mandatory check in AO mapping.
icon

Best answer by ashish_ahuja 24 May 2018, 07:01

View original

3 replies

ashish_ahuja
Rank
Hi Shiv, thanks for coming up with the solution as well for the question. That is the recommended way of doing it.



Adding more clariry to the answer, it's a survey function to be associated with an Account or a Company. A non transactional survey cannot be sent without being associated with either one of those which is why it is kept as a mandatory field and overriden with the feature of a Dummy account in the use cases where no valid account is present but still sending a survey is meaningful to gather responses.



Hope this helps.
shiv_kumar_katiyar
Rank
Userlevel 4
Badge +1
Thanks Ashish! but then what about Email chain model where there is no survey but still ask for dummy account id and same technique I have to apply-



https://cl.ly/3z1g3h2G3f1E
ashish_ahuja
Rank
Email chain gives you the capability to create CTA's based on the conditional criteria builder based on dynamic field evaluations which also has a dependancy on Account Id. A CTA should relate to an account for acting on an event based on data analysis.

But your points are valid in the use cases where email chain model is used for a Program/AO with only email configurations.

We can take it as an enhancement request for future release to detect steps and mandate the fields.

Thanks for the feedback. Highly appreciated!

Reply


Terms & ConditionsCookie settings