I am getting to the point where I am ready to show my web application to the Cost Recovery section. I have a section where the billing is handled and then a section for reports. In each, I have editing capabilities for each entry or site. This is fine and practical once all the Cost Recovery data is imported and polished from the Excel workbooks used to track these sites. However, I added an "Edit" section which still allows editing of these sites. Why the redunancy? I don't intend to duplicate what is all ready handled in the other sections.
My intention is to handle the editing differently. In the first two, editing is done on a selected site or entry by bringing up a page with that information. The user will have to go back to the list and select another using the menus. Fine for few edits.
Once this web application is in production, at least initially, there will be a lot of editing to fit the data into the application and match it with the other databases.
My Edit section will allow the user to select each site and pop up the modal with its information to be edited. It is saved and the modal closed leaving the site selector intact and unchanged. The user selects the next site and repeats the process.
Using a Ajax modal is pretty straight forward. Using the Ajax Toolkit, set the TargetID as the control to activate the modal and PopUpID as a Panel to display and atleast a CancelControlID for the control to close the modal.
The issue at hand is the TargetID is actually not a control such as a Button or LinkButton, but the Select in a GridView. You add the PopUpModal to the GridView, but just clicking on the GridView pops up the modal. This prevents the user from selecting an entry in the GridView and as a result no specific site information can be passed on to the edit modal. I will demostrate how to solve this in the next post.
Subscribe to:
Post Comments (Atom)

No comments:
Post a Comment