Appreciate some commentary to understand if I am on the right track...
I have a mobile app, within it is a list control on one of the panels which displays a bunch of tasks, within the 'list item' is a Task_ID field (GUID) which is also a primary key, I have configured this as the return value in the data source tab of the list builder.
Q1. The primary UX component has data bindings for the controls I initially established for the initial purpose of the component. I later decided there was more info I wanted to capture and submit to the DB, within the app, but I couldn't figure out how to tie the new controls I built within a new panel and submit them as I had 'used up' the afterValidateServerSide event for the initial controls. Am I right in thinking I need to create a new UX (User eXperience-took me ages to find this out) with its own bindings and embed this within the initial UX so it appears seemless and integrated? i.e. is this how you get multiple data submit capability for unrelated data within one mobile app (sorry if this sounds confused...I am)
On the basis that my assumptions of Q1 are correct, my next question is as follows:
Q2. In an embedded UX component (within the primary UX component) I need to populate the default value of a control with the return value of an item selected (the Task_ID) in the original list control...how do I access this? I can 'grab' session values by setting the default property of a text control to e.g. =session.User_ID where I create this session value at login through an a5 script on the login page but I cant figure out how to grab the return value of the list control on e.g. panel A after clicking it and putting this into a control on an embedded UX on e.g. panel 2, I'm not even sure if this can be done, perhaps I need to store the TASK_ID from the list control into a state variable when I click it and access the state variable from the embedded UX??
I have a mobile app, within it is a list control on one of the panels which displays a bunch of tasks, within the 'list item' is a Task_ID field (GUID) which is also a primary key, I have configured this as the return value in the data source tab of the list builder.
Q1. The primary UX component has data bindings for the controls I initially established for the initial purpose of the component. I later decided there was more info I wanted to capture and submit to the DB, within the app, but I couldn't figure out how to tie the new controls I built within a new panel and submit them as I had 'used up' the afterValidateServerSide event for the initial controls. Am I right in thinking I need to create a new UX (User eXperience-took me ages to find this out) with its own bindings and embed this within the initial UX so it appears seemless and integrated? i.e. is this how you get multiple data submit capability for unrelated data within one mobile app (sorry if this sounds confused...I am)
On the basis that my assumptions of Q1 are correct, my next question is as follows:
Q2. In an embedded UX component (within the primary UX component) I need to populate the default value of a control with the return value of an item selected (the Task_ID) in the original list control...how do I access this? I can 'grab' session values by setting the default property of a text control to e.g. =session.User_ID where I create this session value at login through an a5 script on the login page but I cant figure out how to grab the return value of the list control on e.g. panel A after clicking it and putting this into a control on an embedded UX on e.g. panel 2, I'm not even sure if this can be done, perhaps I need to store the TASK_ID from the list control into a state variable when I click it and access the state variable from the embedded UX??
Comment