I have two complex data pages that are both submission data pages. Because they are submission data pages, I do not have the ability to use view data to help create the new records. Because of this, I am being forced to make MANY database calls in order to get the data I need to create the new records.
Requirement: Log user Login activity, load external parameters, redirect user to appropriate landing page based on user type
Scenario #1: 3 states (User exists and is Member, User exists and is Admin, User doesn't exist and is NEW)
Based on User Status:
If Exist, Get Profile information and load external parameters (currently 12 params)
If Exists, Get Profile Preferences and load external parameters (currently 27 params)
Redirect to appropriate location
Problem: If I keep with a Submission DP (submitting ProfileLoginLog), then I need 39 individual calls to the database because I don't have a view I can rely on.
What I am Thinking: If I change the data page to an Update DP, I can then use a view that will support the Profile and Profile Preferences.
But then I end up with two problems:
How do I handle the condition (a VALID condition) of when the user is NOT found?
How do I insert a record into the ProfileLoginLog table?
Any Ideas?
If I can solve this for one situation, I can solve this for both situations.
You can post now and register later.
If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.
Question
Lynda
I have two complex data pages that are both submission data pages. Because they are submission data pages, I do not have the ability to use view data to help create the new records. Because of this, I am being forced to make MANY database calls in order to get the data I need to create the new records.
Requirement: Log user Login activity, load external parameters, redirect user to appropriate landing page based on user type
Scenario #1: 3 states (User exists and is Member, User exists and is Admin, User doesn't exist and is NEW)
Based on User Status:
Problem: If I keep with a Submission DP (submitting ProfileLoginLog), then I need 39 individual calls to the database because I don't have a view I can rely on.
What I am Thinking: If I change the data page to an Update DP, I can then use a view that will support the Profile and Profile Preferences.
But then I end up with two problems:
Any Ideas?
If I can solve this for one situation, I can solve this for both situations.
Your help would be much appreciated.
Lynda
Link to comment
Share on other sites
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.