The 'Optimize for reporting' option does not work as expected
'Optimize for reporting' option does not work correctly. The user is able to optimize the same property the second time.
Steps to Reproduce
- Select a property and navigate to the Actions tab
- Click the 'Optimize for reporting' option
- Verify the schema whether the column is created or not
- Perform a property optimization for the same property
An issue in the custom application code or rules.
Here’s the explanation for the reported behavior:
The user was optimizing a property from the class group which is at the Framework layer. In the optimization wizard, all the frame work classes associated to the class group are displayed with the associated database table. Additionally, another set of implementation classes are also displayed along with the associated database table. Hence, the user can select the table in which they want the property to be optimized. For example, if the user selects one table form the displayed list of tables, the property is optimized in the selected table and is mapped to the associated classes.
On clicking the 'Optimize for reporting' option again, opens the optimization wizard and displays the remaining tables in which the property can be optimized. Thus, the same property can be optimized in different tables.
0% found this useful