Description: I'm encountering difficulties creating reports within a specific application due to issues with catalog item variables not persisting when used as filter conditions.
Background: The application I'm working with utilizes custom tables, and one such table, let's refer to it as the "feedback table," stores user feedback data. I aim to generate reports from this table, intending to filter feedback entries based on specific catalog item variables.
Issue Analysis: When attempting to create reports, I encounter challenges incorporating catalog item variables as filter conditions. Despite following established procedures, such as those suggested here, the variables fail to persist in the report settings.
Probable Cause: The complexity of linking the feedback table entries to catalog items, and subsequently to their associated variables, within the report creation process seems to be a contributing factor. Since the application relies on custom tables and possibly intricate relational structures, the straightforward inclusion of catalog item variables as filter conditions presents challenges. This complexity likely arises from the need to reference multiple tables and establish relationships between them within the report configuration.
Resolution Request: I'm seeking assistance for this reporting issue, either as a solution or a workaround. The proposed solution should address the intricacies of incorporating catalog item variables into report filter conditions within the context of custom table usage. A comprehensive explanation of the problem, coupled with insights into potential solutions or best practices, would greatly benefit me in overcoming this challenge.
