windbeneathyourwings
commented
3 years ago The last part of this is figuring out how to save panel page form submits. Also possibly implementing enhanced table with datasource using multiple viewable bindings.
this is done -- saved using crud adaptor
Use panel pages to create tour of heros demo.
All the pieces are nearly in place for this.
The last thing to do for a initial mvp is to create an entity datasource. Once an entity data source is created entities will be able to be used as a datasource. At the moment the functionality is limited to a rest request and static json. However, the panel page form entities are stored inside idb using a crud adaptor. Luckily they are entities which means all that needs to be done is allow a user to select the entity datasource and pass the name of the entity to query for result data.
The panel page form is stored as a transformed object inside idb not the actually panel page form. However, it would be ideal send back the data in the object format not the panel page format. Data in the transformed format is much easier to understand and better represents construct. So what is actually needed is a crud adaptor. Implementing a crud datasource is a well defined path to achieving the intended target.
Both the crud and entity datasources have been created. All the necessary pieces are now in place to create a complete data entry workflow demo.
Demo will provide form for users to save hero. Hero will be saved to idb as panelpageform Master page will use crud datasource to display panelpageform prefixes as list. User will be able to click item and edit. Delete hero -- how to?
The top heros display will be an autocomplete inside a repeating section panel.