Submit your Suggestions for Vista Web

Better Handle Custom Lookups in Checklist Display

We use custom lookups for checklists, which are great for filling checklists out, but not for displaying completed checklists. Upon filling a checklist out, the custom lookup allows selection of only "Active" employees. But, if we reference the checklist later, the current behavior of the portal is that upon load of a completed checklist, it will use that same custom lookup to check the database value for what it should display. Therefore, if the employee is no longer "Active," the checklist displays a blank, even though there is data in the database for that field.

It would be nice to have checklists enhanced do one of two things: 

  • Save the data and the display value, and ditch the second reference to the lookup
  • OR Allow separate custom lookup definitions for create/read/update actions in checklists

(This enhancement is related to Support Case #1598781: L2 Checklist Values Not Displaying)

  • Guest
  • Mar 13 2019
  • Shipped
Company FHG, Inc.
Job Title / Role Business Systems Specialist
I need it... 6 months
  • Attach files
  • Admin
    Michael Smith commented
    May 24, 2019 16:58

    At this time, it only works for the items.  

  • Guest commented
    May 24, 2019 12:14

    Hey Michael, thanks for your help so far, just following up on this item. Any new developments?

  • Guest commented
    May 13, 2019 12:15

    Michael,

    Is there a plan for the header fields receiving the same update? Across the board, header fields are the place most likely to have lookups to dynamic datasets for us--employee names, equipment names, etc.. We need this to be resolved for header fields much more than items. For us, items are usually simply lists of text entry boxes and check boxes.

  • Admin
    Michael Smith commented
    May 12, 2019 23:44

    Only the items were updated, not the headers.

  • Guest commented
    May 09, 2019 21:03

    Unfortunately, I'm still seeing the same behavior on the checklists we originally had the problem with. But, it may be because I'm looking at header fields here? Is the update only for checklist instance items, and not the checklist header fields? 

  • Admin
    Michael Smith commented
    May 09, 2019 20:57

    Yes this should be resolved moving forward.  Give it a try.

  • Guest commented
    May 09, 2019 18:59

    Hey Michael, I noticed this line in the 19.5 release notes that I thought might have been related to this issue: 

    • Improved historical dropdown binding for submitted checklists.

    Is this related to the issue we're seeing? 

  • Admin
    Michael Smith commented
    April 15, 2019 15:50

    This item has been promoted and the dev team is working on a solution.

  • Admin
    Michael Smith commented
    March 26, 2019 20:05

    Lets meet and review.  I'll send you an invite.

  • Guest commented
    March 26, 2019 18:05

    Michael, 

    This originated as an issue, but was redirected to an enhancement feature. Original issue was Support Case #1598781: L2 Checklist Values Not Displaying. I also argued that this should be handled as an issue. I will reopen the case with Support. Thanks! 

  • Admin
    Michael Smith commented
    March 26, 2019 17:50

    Hi Thomas,

    Can you submit this to support.  It should work as you are describing, if it is not, then support can review with you and we can get it perfect.  The behavior you are looking for should be the standard.

  • Guest commented
    March 26, 2019 13:59

    Hey Michael,

    Just following up on that last response, as we've converted all of our .pdf fillable forms to checklists in the Portal and are relying on the checklist functionality, this has become a bigger issue for us. 

  • Guest commented
    March 19, 2019 13:09

    Michael,

    The dropdown appears blank on load, and cannot be clicked (checklist has already been submitted).

  • Admin
    Michael Smith commented
    March 14, 2019 23:38

    Hi Thomas,

    Does the dropdown appear blank on load, or only appear blank when the dropdown is clicked?

Dear Viewpoint Suggestion Box contributor;

We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs. Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.

1515 SE Water Avenue, Suite 300, Portland, OR 97214 |  800.333.3197  | Contact Us | Terms of Use | Privacy | Support Policies

© 2024 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.