Items from within the "Business (Primary)" reflect on the record set as the Primary Business for the returned record. These items will no longer apply to the Filters set on the Ad-Hoc query. To clarify this we can use the following example:
In the database we'll have an Organization record "Example Org" and two constituent records "John" and "Jane," whom both work at Example Org. On both the constituent records, Example Org is set as the Primary Business'.
Building out an Ad-Hoc query with the following Filters:
* Constituent first name equal to "John"
* Business (Primary)\Relationships\Employment Information\Job Title
When run, the Business (Primary) will replace the use of John with itself. Now the output will look to Example Org and pull everyone that has it set as their Primary Business and list out their Job Titles, such as the following example:
Name: John | Job Title: Programmer
Name: Jane | Job Title: CEO
Here we can see that while the original filter wouldn't include Jane in the output, however she was pulled in because:
The return of John in the filter triggered the system to use his org, Example Org.
The output from Example Org lists everyone where it is the Primary Business, and outputs their information.
Currently, this is how the system is designed. As a workaround we can use the following Output to narrow down who is listed out by removing the "Business (Primary)" node:
- Relationships\Related Constituent\Name
- Relationships\Employment Information\Job Title
- Relationships\Is primary business
- Their name
- The name of their relationship (Business Name)
- The Job Title set in that relationship
- One of the following:
- "Yes" if this is the particular job that is the primary job currently for the constituent
- "No" if this is a relationship listed, but is not the primary job listed for the constituent
- "" (blank) if there is no organization ever listed on the constituents record