We have a requirement of using completely separate customer table in pega marketing Outbound channel as a customer context.
We tried to create a secondary context but that we are not able to create as the second table has different set of columns and there are no common key for both the table.
also tried to create association for the secondary table and added that in primary context. Although the context got saved but while creating the Segment using this newly added association getting SQL generation error. screenshot attached.
***Edited by Moderator Marissa to update Platform Capability tags****
Not within 1 system. As indicated, you can create 2 instances of the system to do so. Another alternative is that you fit the data of the 2 customer bases into 1 entity and have a flag on the entity that describes it as base 1 or 2 and use that in your processing.