Loading...

Setting qListForm item ID with Session or Connection?

Setting qListForm item ID with Session or Connection?

Home Forums QuickApps Forum Setting qListForm item ID with Session or Connection?

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • #5085
      Anonymous
      Anonymous
      Participant

      Hi Rumple,

       

        The http param is the only way to edit/display a specific item.

    • #3882
      Anonymous
      Anonymous
      Participant

      When editing or displaying an item in qListForm is there any way to set the item to edit besides reading the ID from the http param? Can item to be edited by set by via session or a connection (e.g. a connection from qItemDisplay)? Or is http param the only way?

    • #5084
      Anonymous
      Anonymous
      Participant

      Rumple,

           I doubt this is what you are asking for, especially since you mentioned Edit, but just FYI: we are making use of qListView in webpart pages where the primary purpose of the webpart page is for showing a qListForm.  We are only doing this for layout out some of the item data in custom ways, only for data that is not to be edited.

           By putting a qListView on the page (either the readform or the editform) and connecting it to the primary qListForm, and then using the custom layout option available on qListView, you can do some cool things.  Take a look at my post from a few months back if you are interested. You may know already that the custom layout feature in qListView is very straightforward, especially compared with the custom layout option on qListForm.

           Another technique we have used is to create specialty edit forms, where perhaps only a particular subset of fields need to be edited.  In this case we will use two qListForms.  The upper one is defined as a read page and the lower is an edit page with only the subset that I want to allow the user access to.  The upper one is used to show header information from the item just for context.

           We have used this technique for something like a kiosk environment, where limited data is changing – specifically a site pass for a location.  The location item has a lot of data columns which are maintained for numerous purposes, but the webpart page for the site pass just includes a few fields that the guard shack needs to update.

Viewing 2 reply threads

You must be logged in to reply to this topic.