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.  Input pin name as a variable

    Employee
    Posted 08-22-2013 20:48

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

    Originally posted by: StuartOboler

    Hi,
    Can I use an input pin name as a variable in my code?
    For example, if I have a filter node where the input pin is called "SourceSystem_TableName"
    Can I then use the pin name in a formula such as

    NewFieldName = {{^inputPinName^}} + "_FieldName"


    Our actual task is using the meta data node to collect the field names, then replace the field names with a concatenated name using the change metadata node.

    Thanks,
    Stuart


  • 2.  RE: Input pin name as a variable

    Employee
    Posted 08-23-2013 07:46

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

    Originally posted by: stonysmith

    No, for a couple of reasons.
    1) There's currently no such parameter - I can see a couple of possible places where this might be a good idea.
    2) You can't use the value of a variable to set the name of an output column. This feature is likely not to change anytime soon.

    LAE uses the first pass of the data to set the field names and types for the output pin. If the value of a variable (or column value) used to build a column name were to change after the first record, then the node would be attempting to write to a column that doesn't exist, and there's currently no way to deal with that.


  • 3.  RE: Input pin name as a variable

    Employee
    Posted 05-02-2014 20:16

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

    Originally posted by: Umbaugh

    Is it possible to use an Input pin to create a Local Parameter Definition?


  • 4.  RE: Input pin name as a variable

    Employee
    Posted 05-03-2014 13:30

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

    Originally posted by: stonysmith

    No. This feature is often requested, but it's not available.

    What are you wanting to accomplish? There may be some other way to implement it.


  • 5.  RE: Input pin name as a variable

    Employee
    Posted 05-05-2014 10:10

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

    Originally posted by: Umbaugh

    I am attempting to deliver a file with the bill day for that file in the filename. I have the potential for 30 different filenames for the output file, but will only have one filename to create based on the particular day that the file is being created. XXX_Migrate_##.csv ## = the bill day variable I would like to create for the filename.


  • 6.  RE: Input pin name as a variable

    Employee
    Posted 05-05-2014 10:23

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

    Originally posted by: Umbaugh

    I found a node called Path Enabler in documentation that could possible assist me in accomplishing this task in a long winded way, however I am unable to find it in the library. Does this node still exist in 4.6.1?


  • 7.  RE: Input pin name as a variable

    Employee
    Posted 05-05-2014 11:20

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

    Originally posted by: Tim Meagher

    Hi,

    That node still exists however it is Experimental.
    In order to see Experimental nodes, go to Tools->Preferences->Advanced, then check the "Use Experimental Nodes" checkbox.
    Note that these nodes do not have the same support as other "official" nodes in that backwards compatibility on these nodes is not guaranteed.
    You will also see warnings when opening graphs which contain experimental nodes.

    A fully supported alternative to the Path Enabler node might be the Metacheck node, although I'm not sure that either of these are really what you are looking for...

    I might have misunderstood the use case somewhat, but if the filename is meant to be Date specific, can't you use the CurrentDate parameter?
    In order to use it, just use {{^CurrentDate^}}.
    The parameter is a "special parameter" and defined by default.
    The parameter, however, will not work when running as a BRX - there you would need to pass in the date of the run via a run parameter to the BRX being executed.

    Or is the filename meant to be specific to the data being loaded and the date?
    If so, then you might want to take a look at the "Output Delimited (MultiFile)" node.
    This node isn't provided with the LAE itself and isn't really supported in the same manner that other nodes posted on these forums are posted.
    In any case, if this suits your needs, you can find the node here: http://community.lavastorm.com/threa...ed-(Multifile)

    If none of these really address what you are trying to do, maybe I've misunderstood the requirements and might need some more clarification.

    Regards,
    Tim.