GI - Unable to add unbound field in Condition

AI was used to create this answer

The issue you're encountering when adding an unbound field as a condition in a Generic Inquiry (GI) after upgrading to Acumatica 2023 R1 likely relates to changes in the validation of table relationships and aliases within the GI's relational structure.

In Acumatica 2023 R1, stricter enforcement of relational integrity between tables in GIs has been introduced. This means that any field (bound or unbound) you wish to use in a condition must now strictly adhere to the following:

1. Table Joins: The table containing the unbound field must be explicitly joined to the main table or other related tables in the Relations tab.

2. Alias Matching: The alias specified for the table in the Relations tab must correctly match the table's alias where the unbound field is being referenced.

Error Breakdown

The error message, “The CurrentBAccount field cannot be used because the table with the CurrentPlaceholders alias is not joined with other tables on the Relations tab,” indicates that:

• The alias CurrentPlaceholders for the table containing CurrentBAccount is not correctly joined or recognized in the Relations tab.
• The unbound field (CurrentBAccount) depends on a valid and recognized alias.

Suggested Fix

To resolve this:

1. Go to the Relations tab of the GI.
2. Add or ensure the table (or the alias) for the unbound field is present and properly joined with the required tables.
   • Ensure the Join Type is correct (e.g., Inner Join, Left Join).
   • Verify the Join Conditions accurately link the tables.
3. Check if the unbound field is using an alias. If yes:
   • Verify that the alias matches exactly as used in the Relations tab.
   • Update the alias if necessary for consistency.

Additional Notes

• If the unbound field is calculated using DAC attributes or formula logic, ensure that these are defined properly in the corresponding table or DAC extension.
• Any changes in table structure or alias handling from 2022 R1 to 2023 R1 should be accounted for by reviewing release notes or consulting updated developer documentation.

If the issue persists, please ensure the GI aligns with any updated best practices introduced in 2023 R1.

If you haven't solved this yet, could you screenshot the Relations tab and the join statement for that table?

​@darylbowman , have added as table and made the joins and conditions but while opening the GI screen get this error.

​@ vib1980 Can you re validate the Joins once?

​@mohammadnawaz51 , I have checked couple of times, deleted and re-added them not sure what else needs to be done.

This is the DAC for one of the unbound field