State column on RIDAC page doesn't show state for all RIDAC tables in single column

[Anmol123]

The Issue, Action, and Request Change tables are extended from the Task table, whereas the Risk and Decision tables are independent. This causes a mismatch in the backend name of the State field between the Risk/Decision tables and the others. To address this, we can create a custom State field on all five tables with a consistent backend name, replicating the values from the original State field. By adding this new custom field to RIDAC, end users will be able to view the State for all five tables in a single column.

[M Iftikhar]

Hi @Anmol123, 

Your solution addresses the inconsistency of the "State" field's backend name that arises because the Issue, Action, and Request Change tables are extended from the Task table, while the Risk and Decision tables are not. By creating a new custom "State" field with a uniform backend name across all five tables and populating it with the values from the original state fields, a unified view becomes possible. This allows for the addition of this single, consistent custom field to the RIDAC view, enabling end-users to see the state of all five record types in one consolidated column.

Thanks & Regards,
Muhammad Iftikhar
If my response helped, please mark it as the accepted solution so others can benefit as well.