You’re offline. This is a read only version of the page.
8
You've pinpointed a very interesting and likely accurate root cause: a residual validation check within the Customer Insights - Journeys (Real-time Marketing) app context that was relevant for Outbound Marketing's lead scoring but shouldn't be active now that Outbound is uninstalled.
This kind of context-specific, internal validation can be tricky to troubleshoot because it's not tied to visible customizations like plugins, JavaScript, or business rules.
Here's a breakdown of why this might be happening and how you might address it:
Likely Cause:
As you suspect, the Customer Insights - Journeys app likely still has some internal logic or components related to the legacy Outbound Marketing lead scoring features. This logic might be triggered when the Lead form is used within its context, even though Outbound is uninstalled. The check for an associated Contact or Account was crucial for Outbound lead scoring to function correctly.
Since Real-time Marketing has its own, different mechanisms for lead qualification and scoring, this validation is now irrelevant and unexpected.
Why it Doesn't Appear in Sales Hub:
The Sales Hub app likely doesn't carry the same legacy context or triggers related to Outbound Marketing lead scoring, hence the consistent behavior you observe there.
How to Address This (Since You've Ruled Out Customizations):
Given that you've confirmed no custom logic is at play, the solution likely involves influencing the behavior of the Customer Insights - Journeys app itself. Here are your primary options:
Why Direct Configuration Might Be Limited:
Because this seems to be internal validation logic tied to the app context, you're unlikely to find a specific setting within the standard customization interface to disable it. These kinds of checks are often embedded within the application's code.
In summary, your diagnosis of a leftover check from Outbound Marketing within the Customer Insights - Journeys app context is very plausible. The best course of action is to open a support ticket with Microsoft to report this unexpected behavior. They will be best positioned to investigate and provide a resolution.
Would you like me to help you frame the information for your support ticket?
Share
Report
All responses (
Answers (
