![]() |
Sergey Kornilov admin 3/11/2016 |
If these two table are related as master-details you can choose to display details table info on Add/Edit/View pages of the master record. You can turn on this option in master-details relationship properties on 'Datasource tables' screen. |
![]() |
jadachDevClub member 3/12/2016 |
Another option is to join the enrollment table to your existing offering table in the sql editor (outer join). Then display those values as read only on add/edit pages. |
![]() |
Pete K author 3/14/2016 |
Thanks for the helpful replies. |
![]() |
jadachDevClub member 3/14/2016 |
Can you post your 2 table structures? I think there is a way, just not 100% following you. I'd like to try myself. |
![]() |
Pete K author 3/15/2016 |
Absolutely. I'd love to see what you can come up with, Jerry. Very much appreciate your taking a crack at it. |
![]() |
jadachDevClub member 3/15/2016 |
So I started thinking about this and contemplated the way I would approach it. I would be inclined to have users go to the offerings list page. There they can search, see more info, etc. I would then add a custom enroll button on each record of this list page. By clicking the button, it would insert relevant data into the enrollment table then redirect to my enrollment that will show all offerings that user enrolled in. They could then edit or delete from there. Does that make any sense at all to you? Am I understanding what you want to acheive? |
![]() |
Pete K author 3/16/2016 |
Yes, you are understanding it perfectly and that's exactly how I am implementing it, except that the folks I am working for really want to present the user with visual confirmation that they are in fact signing up for the offering they intended to pick, before they click the final enroll button. So I was thinking about how I have handled similar situations in Iron Speed and I think I have a workable solution, but I'm not sure how to implement it in ASPR. |
![]() |
jadachDevClub member 3/16/2016 |
Check your email. |