CE1568 Error: Login Page Expects User_SecurityProfile Object, but It’s Not Available
0
Hey all! I’m encountering a CE1568 consistency error in my Mendix app, and I’m hoping for some guidance on how to resolve it. The error message states that the Login page expects an object of type User_SecurityProfile, which is not available. This error appears in the context of a user authentication flow involving User and User_SecurityProfile objects. Here’s an overview of my setup: Microflow Setup: I have a microflow (Login_User) that handles the user login process. The microflow retrieves the User_SecurityProfile object using an association from the User object ($User/User_SecurityProfile_User). After retrieving and modifying the User_SecurityProfile, the microflow proceeds with various checks (e.g., account lock, failed login attempts) and finally commits the User_SecurityProfile object. Login Page Configuration: The Login page is set to expect two parameters: User and User_SecurityProfile. I’ve confirmed that the page parameters are correctly set up, and the navigation action leading to the Login page is configured to pass both objects. Troubleshooting Steps Taken: Verification of Association Retrieval: I checked the “Retrieve User_SecurityProfile” action settings in the microflow. Currently, it retrieves User_SecurityProfile by association through $User/User_SecurityProfile_User. This should ideally retrieve the User_SecurityProfile associated with the User. Alternative Retrieval Attempt: As a troubleshooting step, I considered retrieving User_SecurityProfile directly from the database using a constraint like [User_SecurityProfile_User = $User], to ensure the correct User_SecurityProfile is fetched even if the association isn’t reliably set. Testing: I tested the flow after making these adjustments, but the CE1568 error persists. Questions: How do I fix this? I have simiar errors for other buttons on other pages. Any advice or insights from the community would be greatly appreciated! Thank you for your help! -Aidan
asked
Aidan Brotherhood
1 answers
0
Solution to this was simple - show the page via a microflow and pass the objects that way.