Hi ​@abhinayaananadhan22 , Please add BAccount table in Relations tab and make necessary joins as mentioned in screenshot. Attached the modified GI.

Thanks arthi , 

Configured the same but based on Notification source the Notification template should be visible 

Checking for that where the Email is nonexistent in DB 

For eg :Email Template: CC Card expiration will have the recipient Mail Different
                                       CC Card will have the recipient mail different configuring that 

 

Hi ​@abhinayaananadhan22,

You may have to join Contact table in relations to fetch the Email field. i.e Contact.Email.

You also need to join NotificationSetup DAC to display Notification Description.

Hope, it helps!

AI was used to create this answer

To connect the Notification Source and Notification Recipient to the Customer table in Acumatica ERP's Generic Inquiry, you need to ensure that the relationships between the tables are correctly established. 

1. **Check Table Relationships**:
   - Make sure the Customer table has a unique identifier (like Customer ID) that can be used to join with the Notification Source and Notification Recipient tables. 
   - Ensure that the relevant fields in the Notification Source and Notification Recipient tables reference the Customer ID.

2. **Create Joins**:
   - In the Generic Inquiry, go to the "Tables" section and add the Customer table if it’s not already included.
   - Create a join between the Notification Source and the Customer table. The join condition should be based on the Customer ID.
   - Repeat this for the Notification Recipient table.

3. **Display Customer Information**:
   - Once the joins are correctly configured, add fields from the Customer table (like Customer ID and Customer Name) to the "Results Grid" in your inquiry.

4. **Filter Notifications Based on Email Existence**:
   - To filter notifications based on whether an email exists, you can add a condition to the inquiry. 
   - For example, you can add a condition that checks if the Email field is not null or empty.

5. **Configure Email Templates**:
   - For each notification template, you may have different recipients. Ensure that your inquiry can distinguish between these templates. You might need to include a field that identifies the template and set conditions accordingly.

6. **Testing**:
   - After you’ve set up the joins and conditions, run the inquiry to see if the data is displayed as expected. If not, check the join conditions and field mappings.

If you continue to have issues with the configuration, you might want to review the specific field mappings and ensure that the data types match between the tables.