Legacy Data Flow BRG Import Failure LAE 6.1.4 to D3SA 3.2.6

Comments

4 comments

  • Avatar
    Adrian Williams

    This issue  relates to support ticket #72760.

    The import error can occur in the following narrow set of circumstances:

        When a Lavastorm core library node has been overridden and the node's name was not changed.

    A fix for this issue will be available in the next maintenance release (v.3.4.2).

    A work-around for this issue has also been provided in the mean time.

    0
    Comment actions Permalink
  • Avatar
    Stuart Nelson

    Hi Adrian, we have experienced this in 3.2.7 - can you provide details of the workaround please?

    0
    Comment actions Permalink
  • Avatar
    Adrian Williams

    The issue will be in one or more local library nodes within the Lavastorm graph. Open the affected .brg file in a text editor and look for the library node definitions which will be in the stanzas starting with libnode:

    The affected libnode(s) will not include a line similar to this

        editor:Label=<foo>

    where <foo> is the name of the node.

    For example, depending on the core node the start of the stanza may look like:

    libnode:Filter_3
    bretype:core::Filter
    editor:handle=5aba410f03217f3f

    ...

    or

    libnode:Output_Delimited
    bretype:core::Output Delimited
    editor:handle=5aba410f36e72d0f

    ...

    You need to insert a line to specify the label, so in the above case the definitions would start with:

    libnode:Filter_3
    bretype:core::Filter
    editor:Label=Filter
    editor:handle=5aba410f03217f3f

    ...

    or

    libnode:Output_Delimited
    bretype:core::Output Delimited
    editor:Label=Output Delimited

    editor:handle=5aba410f36e72d0f

    ...

     

    0
    Comment actions Permalink
  • Avatar
    Stuart Nelson

    Thanks Adrian.

    0
    Comment actions Permalink

Please sign in to leave a comment.



Powered by Zendesk