in

 

Case statement for check boxes

Last post 10-02-2008 9:18 PM by matilda. 4 replies.
Page 1 of 1 (5 items)
Sort Posts: Previous Next
  • 07-16-2008 8:47 AM

    Case statement for check boxes

    Ok, here's my issue.

    On our tasks, we have a custom field called "Task Type" which as two check boxes, called "Implementation" and "Communication".

    I'm building a prompt page using that field so they can run a report on one or the other task type (ideally, I'd like a both option as well, but that may be further down the line).

     In the database, because they are check boxes, they are simply numbers.  If I put them in a list report, I get 0-4.  This is true of all multi-select type fields (very annoying by the way).  So, I know I need to build a case statement to say 0 is nothing and 1 is Implementation and so on.  I'm not sure the format.  Also, how do I then use that to build the prompt?  I want them to make a radio button choice on which report to run.  I need for Daptiv to know which task types to show in the report.

  • 07-17-2008 6:44 AM In reply to

    Re: Case statement for check boxes

    I believe we already have a field called "Task Type" that is native so be sure you are grabbing the Custom Field.  Regardless if it is the custom field or not, it should be showing the text values and not a numeric assignment from the database so I would consider this a bug to be submitted to support.    

    Steve Thompson | Solutions Consultant
    Daptiv


  • 07-17-2008 6:56 AM In reply to

    Re: Case statement for check boxes

    Tested this to be sure, below is a screenshot of the Task Type which is our native field and Task Category which is the custom field like you're using.  So text is what I'm getting instead of numbers.

     


    Steve Thompson | Solutions Consultant
    Daptiv


  • 08-27-2008 11:22 PM In reply to

    • matilda
    • Top 75 Contributor
    • Joined on 11-13-2007
    • Brisbane, Australia
    • Posts 9

    Re: Case statement for check boxes

    Just to confirm initial users post - our Enterprise also experiences the isse with multi select pick lists returning numeric value not textual value. For most reports I have done the case statement work around but when you get pick lists that allow multiple options the number of possible values quickly becomes too many to individually map.

    Support case was logged in June, initial investigation done by daptiv who confirmed it is an issue. It is now in the queue for technical assistance, I have heard no more since last month

    Also question was asked in same forum see post: http://community.daptiv.com/forums/t/1559.aspx 

     

  • 10-02-2008 9:18 PM In reply to

    • matilda
    • Top 75 Contributor
    • Joined on 11-13-2007
    • Brisbane, Australia
    • Posts 9

    Re: Case statement for check boxes

    Daptiv have now fixed this issue (October 08)

    thanks

Page 1 of 1 (5 items)

Navigate: Home | Blogs | Forums | Solution Library  Get Help:  Contact | Feedback | FAQ   Terms of Use:  Terms & Conditions | Privacy Policy