LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Correct use of brainscript and brainscriptexp parameter types

    Employee
    Posted 09-22-2015 23:02

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: arkore

    I have a need to assign a parameter value based on another parameter value. Specifically I have financial reporting that has one runtime paramter set as the date the report is to be generated but I need to derive the end date of the prior financial year. I cannot calculate this within a Filter node as I am obtaining the original data from a Python node that interfaces with an API.

    Am I correct in assuming that brainscript parameters can derive their value from other paramters using BRAINscript? Which of the three forms should I use?


  • 2.  RE: Correct use of brainscript and brainscriptexp parameter types

    Employee
    Posted 09-23-2015 09:08

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: stonysmith

    First, you need to understand that Parameters are implemented as textual substitution. They exist only at design time.. they are changed to hard-coded values as the node is executed. In other words, Parameters can not be changed (by data) at RunTime.

    Parameters can refer to other Parameters, but their value can't change after a node is started.

    You say that you can't calculate the value in a filter... why not?


  • 3.  RE: Correct use of brainscript and brainscriptexp parameter types

    Employee
    Posted 09-24-2015 19:52

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: arkore

    I cannot calculate the value in a filter because it is being used as a local node parameter for a python node to access data from a REST API.

    I have been thinking it may be easier to simply ask the user to type in the prior financial year end date as an additional parameter. For ongoing maintainance of the code I don't want to fork the python node to create a special version that adapts the date in the python code for the call to the REST API. The only other way I can think of solving this is by requiring a specially formatted input node to obtain the correct date.