Calling Column Properties

Welcome to our Forums Technical Support Support Desk Calling Column Properties

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #1920
    jordan
    Participant

      I would like to call a column property as a parameter for another column, but it seems like DataGraph only expects a global variable. Is there a way to do this without setting global variables for the property? The reason I want to do this this way, is because with column properties, I can have the same column names  with different parent groups, and I don’t have to change the syntax. If I make global variables, then I will have to make a new variable for each new column group…that is a big ask when dealing with scores of column groups!Screen Shot 2019-10-05 at 11.46.35

      #1921
      dgteam
      Moderator

        You can get the average without needing to set the ‘# of rows’.

        Use the expression:

        Baseline.average + Baseline*0

        This will make a column with the average as a constant and it will have the same length as the column Baseline.

        Does that help?

         

         

         

        #1957
        jordan
        Participant

          That works exactly how I want it to work, but I don’t understand why it works. Can you shed some light on that?

           

          #2015
          dgteam
          Moderator

            No problem.

            We added an explanation to the Expression Column documentation.

            The section is ‘# of Rows’ at the bottom of the page.

            Does this help explain?

            #2016
            jordan
            Participant

              This explanation describes the behavior but doesn’t explain it. Why can the user not specify that she only wants 4 rows of “A+B”? DataGraph assumes that the users wants the entire row. What is the behavior if “A” and “B” are different lengths? I can test it to find out, but the logic is somewhat lost on me. That is what I was looking for. Also why is the property from a column give different behavior from referencing the column. They may not be a reason, and that is ok, it is just easier for a user to understand the paradigm when they are learning to navigate the interface. That sort explanation is probably beyond the scope for the user manual, and there may not be a logical reason for the behavior, and that is ok too. Thanks for the information and work around that you have provided!

              jordan

            Viewing 5 posts - 1 through 5 (of 5 total)
            • You must be logged in to reply to this topic.

            Welcome to our Forums Technical Support Support Desk Calling Column Properties