Exposed Column from embedded page property is null after login
An application consists of an exposed column in the Data-Admin-Operator-ID class, which is populated from an embedded page property, that is defined on a different class. On logging in as a user, the value of the exposed column changes to NULL. However, this works when the property is optimized through the App Explorer.
Steps to Reproduce
- Expose a column for a property in an embedded page, which is embedded in the top class of the Data-Admin-Operator-ID.
- Execute an Obj-Browse that depends on the exposed column containing data. The query displays the results correctly.
- Log in as a user returned in the Obj-Browse in Step 2. The property is empty.
The page property referred to a data page defined in another class but was created in the Data-Admin-Operator-ID class. The page had properties optimized for the OperatorID class and changed to NULL during log in.
The issue occurred because every log in and log off of the system created an update to the OperatorID record to revise the pyLastSignOn and the failure attempts required for authentication.
During the Save operation of the Operator, the system does not have the Scope of the Page properties and sets them to NULL.
Perform the following local-change:
Change the Page property to use 'Copy data from a data page' instead of 'Refer to a DataPage'.
Published August 4, 2020 - Updated December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.