That is ok, but I'd like to know how work with master and detail using navigation buttons Next, Previous etc instead of Scroll, and keep the current position of Master (record) after I have added a new register in Detail and Save. Everytime that I save anything, Apex lose the place where the record is and redirect to first page, first record. Considering yet that my detail, in fact is a Region Display Selector with three tabs, each one being a Interactive Grid.
HAHA, I could not get this to work! I THOUGHT I followed this video to the letter. Apparently not! I was doing a master detail detail. The first detail table was a link table. It just had PFKs in it. I still wanted to see the data of the key values , so I assigned it to a LOV. It was room number, so room number was more useful than ROOM_ID. Since there No need for any data in the link table, as it just linked tables together for many to many. Since using the LOV in the first table, the second detail would not show up. Apparently APEX was using the value returned from the LOV instead of the values in the first detail table! Changing it back from LOV to its own 'item value' fixed it! 🤣 Lesson, don't use LOVs on PK fields in a Master detail(detail) page!
Thanks. It helped me a lot
Thank you for the introduction!
That is ok, but I'd like to know how work with master and detail using navigation buttons Next, Previous etc instead of Scroll, and keep the current position of Master (record) after I have added a new register in Detail and Save. Everytime that I save anything, Apex lose the place where the record is and redirect to first page, first record. Considering yet that my detail, in fact is a Region Display Selector with three tabs, each one being a Interactive Grid.
HAHA, I could not get this to work! I THOUGHT I followed this video to the letter. Apparently not! I was doing a master detail detail. The first detail table was a link table. It just had PFKs in it. I still wanted to see the data of the key values , so I assigned it to a LOV. It was room number, so room number was more useful than ROOM_ID. Since there No need for any data in the link table, as it just linked tables together for many to many. Since using the LOV in the first table, the second detail would not show up. Apparently APEX was using the value returned from the LOV instead of the values in the first detail table! Changing it back from LOV to its own 'item value' fixed it! 🤣 Lesson, don't use LOVs on PK fields in a Master detail(detail) page!