Comments

4 comments

  • Official comment
    Joel Stewart

    Amin, thanks for pointing out this inconsistency. Based on reviewing the data, I believe this is the actual function that was used in the example: GROUPLAST(#RawData!Item;#RawData!Item). 

    In this case, the value to display and the value to sort from are the same and are the "Item" column. 

    We'll work with our documentation team to get this corrected in the public documentation as well. 

    Comment actions Permalink
  • Amin Torabi

    Hi Joel,

    The DAS50 example (see the link below) has an "order" column, which makes sense to me.

    I'm just curious to know if the DAS50 example was intentionally changed and if so, why?

     

    https://documentation.datameer.com/documentation/display/DAS50/GROUPLAST

    0
    Comment actions Permalink
  • Joel Stewart

    The example from the Datameer 5 version does make sense as it is. It's unlikely that this change was intentional since it's represented from a screenshot only. In this example, there are two separate columns we're using. Specifically, we're ordering by the "Order" column and then passing through the "Item" column as the result.

    In the Datameer 6 example, the version that I shared is valid as well: GROUPLAST(#RawData!Item;#RawData!Item) This simply indicates that we're using the same value to include in our grouplast output that we're using to sort. Specifically, we're ordering by the "Item" column (alphabetically) and then passing through the "Item" column directly as the result.

    Both of these use cases are valid for GROUPLAST itself. Regardless, we'll be sure to provide an update to the documentation such that the screenshots are consistent with the text on a given page.

    0
    Comment actions Permalink
  • Joel Stewart

    Datameer has published updated documentation to include the "Order" column in the https://www.datameer.com/documentation/display/DAS60/GROUPLAST page. 

    0
    Comment actions Permalink

Please sign in to leave a comment.