The "Contact Point Consent" (msdynmkt_contactpointconsent) table can still be used in segments even if it is not directly related to the Contact table. However, its usability depends on how you plan to link it with the Contact table. Here are some ways to resolve the issue:
A. Verify Table Availability
Ensure the "Contact Point Consent" table is available for segmentation:
Go to Advanced Find or Power Apps Maker Portal and confirm that the "Contact Point Consent" table is set to be searchable.
Check its metadata in the Dataverse table settings to ensure the table is enabled for querying or use in segments.
B. Create a Custom Relationship
If no existing relationship connects the "Contact Point Consent" table with the Contact table, you can create a custom relationship:
1. Go to Power Apps Maker Portal
2. Open the "Contact Point Consent" table and click Relationships.
3. Add a 1:N or N:1 relationship to the Contact table using a meaningful linking field, such as email address or contact ID.
Once this relationship is created, you can directly reference related records in your segment.
C. Use FetchXML or Dataverse Query Builder
If adding a relationship is not possible, you can use advanced querying to build relationships based on data:
Use FetchXML to create a query that links records in the "Contact Point Consent" table to the Contact table using common fields (e.g., email address, phone number).
You can embed FetchXML queries in Dynamics 365 segments or other parts of the system (if your use case allows it).
