N:N relationships in campaign and marketing list entities

May 2, 2012 at 9:27 AM

Hello everyone,

I've got some issues while trying to distribute workflows on N:N relationship between campaign and marketing lists. Workflow activity fails with following message:

"'List' entity doesn't contain attribute with Name = 'entityid'."

Am I doing something wrong? Other relationships work just fine (e.g. Contact-Account).

Aug 20, 2013 at 3:14 PM
Did you ever find a solution to this? I'm getting a similar error between Contact and Marketing List

"'Contact' entity doesn't contain attribute with Name = 'entityid'."

Apr 15, 2014 at 4:14 AM
Edited Apr 15, 2014 at 4:21 AM
For people with same problem in future, in case of Contact and Marketing list, the Entity intersect attribite is called entityid rather than contact id, causing the workflow to throw exception.
Relationship dump below.

replacing Entity2IntersectAttribute with contactid will fix the issue.

Same issue will be there for campaignlist_association, listaccount_association, listlead_association etc.

Since @current company we use only ML with contacts, I modified the DistributeWFActivityManytoMany class to have the following code between First link and second link.
        // First link
        secondaryToIntersection.LinkToEntityName = intersection;
        if (RelationshipName == "listcontact_association") {
            secondaryToIntersection.LinkFromAttributeName = "contactid";
            secondaryToIntersection.LinkToAttributeName = secondaryAttribute;
            secondaryToIntersection.LinkFromAttributeName =
            secondaryToIntersection.LinkToAttributeName = secondaryAttribute;
        // Second link
Let me know if and clarification.
Jul 7, 2015 at 3:00 PM
Edited Jul 7, 2015 at 3:01 PM

I encountered the same error with Marketing Lists ('List' entity doesn't contain attribute with Name = 'entityid'.) and this looks like the solution I've been searching for.

To apply the fix mentioned by Jithesh, is it a case of getting the source code, making the suggested change to the correct class then rebuild and import into CRM? Or is there by any chance a fixed version floating around for download and install?