Re: Populate a List Control's Detail View Programmatically
I'm not aware of anything that will allow you to do this. You're essentially bypassing the data-bound List, populating it manually, but you still want data-bound features. I thought providing a Custom data source might work, but again, you're just providing a delimited list of data. In all cases other than SQL, you're not providing table information... and so syncing can't really take place.
You can always sync manually with another callback. Apart from Syncing, displaying data in the Detail View does not require the Primary Key in any Data Source except SQL. If you provide a Custom data source or a Static data source, Detail View will be populated upon row selection. You just can't sync.
You write something that sticks out, though. "Overall, the goal is to convert many UXs to be list based, instead of using data binding in the UX.". The List Control can be data bound... and this data binding is completely separated from a UX being data bound. So, I'm not sure what you mean. Are you converting UX Repeating Sections?
As far as I know, using any method other than SQL is just filling the List with data... it's one sided. As said... you can always update your tables manually with another callback.
In actual practice... let's say you could use an Ajax Callback to populate a List and have everything work. Why do you need to? What's the advantage of filling a List with an Ajax Callback?
I'm not aware of anything that will allow you to do this. You're essentially bypassing the data-bound List, populating it manually, but you still want data-bound features. I thought providing a Custom data source might work, but again, you're just providing a delimited list of data. In all cases other than SQL, you're not providing table information... and so syncing can't really take place.
You can always sync manually with another callback. Apart from Syncing, displaying data in the Detail View does not require the Primary Key in any Data Source except SQL. If you provide a Custom data source or a Static data source, Detail View will be populated upon row selection. You just can't sync.
You write something that sticks out, though. "Overall, the goal is to convert many UXs to be list based, instead of using data binding in the UX.". The List Control can be data bound... and this data binding is completely separated from a UX being data bound. So, I'm not sure what you mean. Are you converting UX Repeating Sections?
As far as I know, using any method other than SQL is just filling the List with data... it's one sided. As said... you can always update your tables manually with another callback.
In actual practice... let's say you could use an Ajax Callback to populate a List and have everything work. Why do you need to? What's the advantage of filling a List with an Ajax Callback?
Comment