Dynamics 365 Customer Insights - Journeys

This is actually a bug, but I was encouraged by support to report it as an idea.

The error applies to real-time marketing segment builder, where the use of several segments with the combination "and also" as criteria elements gives the wrong number of contacts. The same applies if you have a table with a criteria and a related table with a criteria.

E.g. we have a case where we want to find all students who are on a course. In Outbound segment builder the query is as follows and returns 85 students, which is the correct number

PROFILE(opportunity, opportunity_1) .RELATE(opportunity_pp_studyprogramperiod_pp_studyprogram_edition, pp_studyprogramperiod_1) .FILTER(opportunity_1.pp_bcstatus == 292460000 && pp_studyprogramperiod_1.pp_fsclasscode == 'MH23MSRHO1') .TRAVERSE(opportunity_contact_customerid, contact_1)

In real-time the query looks like this and returns 154 students as the pp_bcstatus is not considered.

PROFILE(contact).RELATE(opportunity_customer_contacts, pp_studyprogramperiod_2, RELATE(pp_opportunity_studyprogram_edition_pp_study, pp_studyprogramperiod_2__1)).RELATE(opportunity_customer_contacts, opportunity_1).FILTER(opportunity_1.pp_bcstatus == 292460000 && pp_studyprogramperiod_2__1.pp_fsclasscode == 'MH23MSRHO1')

There are several ways to build this segment, but they all returns the wrong result. For example, if we combine two segments, like this

PROFILE(contact).RELATE(opportunity_customer_contacts, opportunity_1).FILTER(opportunity_1.pp_bcstatus == 292460000) INTERSECT PROFILE(contact).RELATE(opportunity_customer_contacts, pp_studyprogramperiod_1, RELATE(pp_opportunity_studyprogram_edition_pp_study, pp_studyprogramperiod_1__1)).FILTER(pp_studyprogramperiod_1) 1__1.pp_fsclasscode == 'MH23MSRHO1 ')

The result is still wrong, it returns 154 students instead of 85.

I would say this is a critical error!

TrackingID#2309220050002468

Today it is not possible to use TRAVERSE clause in creating a segment in the RTM segment builder. This is something that we can do in the Outbound segement builder.

This means that there is no possibility to segment on child account data where the only connection to contact/lead exists on the parent account..

The parent/child relationships are standard (OOTB) relationships that can be used to create segments in Ooutbound Marketing bu not in RTM. This has to become possible in the new segement bilder in RTM.

Please vote to get this functionality in to RTM ASAP!

We need Dependant Lookup filter (Based on Dataverse relationship).

We use to have this feature in Outbound Marketing but in Real time marketing We don't have this Feature. This is a bare minimum functionality which required.

Ex: State Lookup filtered based on selected Country lookup.

Allow any type of person to create opportunities from the client module without taking into account the default configuration in the parameters

When we create Opportunity from ‘Accounts Receivable > Customers > All customers’ and ‘Prospect’ field value in Global Address book is ‘Organization’, system has to set relations for the new Opportunity.

The first relation is standard for all Opportunities – smmOpportunityTable->DitPartyTable

The second one depends on the type of a party.

If ‘Prospect’ field value in Global Address book is ‘Person’ or we create Opportunity right from the ‘Sales and marketing > Relationships > All prospects’ where the record has party type ‘Person’, system establishes relation ‘DirPartyTable - > DirPerson’. If not – relation ‘DirPartyTable - > DirOrganization’ is created.

In our case, we already have ‘DirPartyTable - > DirPerson’ relation, as it is set by system during creation of a Customer of type ‘Person’, and further, when we try to create opportunity from the customer, we get the second relation ‘DirPartyTable - > DirOrganization’, as ‘Prospect’ field value in Global Address book is ‘Organization’ and we don’t create opportunity from the ‘Prospect’ form. Actually, we are trying to have two different relations ‘DirPartyTable - > DirOrganization’ and ‘DirPartyTable - > DirPerson’ for one party, and the system throws an exception as it is impossible.

Several customers have complained about the way the tool provides a way to manage the supression list. 

Right now, the only way to check if a contact has entered this list is to add the ContactabilytyGrid control to your contact custom form (Communication tab in OOTB form). This tab shows the date of entry and exit from the list and the reason. In addition, there is the possibility to remove the contact from the list if it is not a hardbounce.

It would be a great help to be able to consult this data in bulk, from a section of the insights or from a view, but to be able to exploit a list of all the emails that have entered this list with the information of the reason, date of entry and exit. 

Clearly, if a customer has millions of contacts, they will have thousands of contacts in the suppression list, so checking them one by one does not make much sense.

Thank you very much!

In the segmentation of customer insights journeys, although the columns are dynamically added to the segment member view, when exporting, the system exports some columns by default.

Please, it would be a great help if in the exported excel file the columns of the segment member view that are shown in the segment could be kept. Quite a few customers complain about this, as they include columns with key data in the view and then cannot work with this information in the exported file.

I am seeking a functionality that supports a WEBAPI call, enabling the input of a lead's Guid to reveal the associated segments the lead belongs to.

When adding a compliance profile to a segment (purpose or topic), both active and inactive profiles are displayed, causing confusion and clutter in our workflow.

Suggestion: Only show active compliance profiles in segments

Currently it is not possible to have unique IDs when creating a custom trigger, so the idea is to be able to use IDs such as "Customer number" (alternate key) and pass this to the custom trigger. Currently, email and phone number is possible, and thus would be fantastic to pass "Customer number" or other alternate keys to the custom trigger.

If you have security enabled on some fields, it's currently not possible to use those fields in the query of a real-time marketing segment. Even if your user has a security profile giving the read privilege on the secured fields (and even if you're system administrator).