Data360 Analyze

 View Only

Pasting of code = impossible?

  • 1.  Pasting of code = impossible?

    Posted 06-30-2022 09:08
    Dear all,

    In Lavastorm, it was possible to copy/paste the raw content of nodes via e-mail/chat/text editor etc.

    A very simple example of a Sort node would be:
    node:Force_Sort_order
    bretype:core::Sort
    editor:Label=Force_Sort_order
    editor:sortkey=6256d82a239a2140
    input:@40fd2c743ebf4304/=Fields_in_both_tables.457826825d7c2de0
    output:@40fd2c746a2a3b47/=
    prop:CompareOrderExpr=<<EOX
    'FieldNumber'
    EOX
    editor:XY=590,270
    end:Force_Sort_order

    We had a very special use case for this: We have a Lavastorm-project with the sole task to generate (based on a set of parameters) the Lavastorm-code for the cell-by-cell comparison of 2 tables in SQL Server, based on 1 or more key fields, and to report differences (the first 10,000 or 100,000 differences per field) to Excel.

    The output of the analytic routine is a table with 1 single cell containing all the Lavastorm-code necessary which, if copy/pasted in a Lavastorm-project would give you all the nodes (DB Execute with all necessary SQL code and as many outputs as there were fields, Head-nodes with 10,000 or 100,000 records output and the Output Excel-node with all the named inputs necessary to report the differences; There even is a composite which creates, if necessary, the output folder. lines between inputs/outputs were also drawn correctly).

    This functionality is fan-tas-tic in our huge project, because we produce 10's of tables each week and these cannot be taken into production before a rigorous testing procedure has taken place. This cell-by-cell comparison between the table in "staging" versus the same table in "production" gives us a fantastic tool to spot possible errors our the business logic (amongst other testing procedures, of course). We developed this routine because the tables we produce change a lot over time (columns added or removed, for example) and maintaining the logic per table by hand is a LOT of work; So simply having the logic created for you is just fantastic.

    However, it seems to be impossible to do the same thing in Data360 Analyze: copy/pasting of code (not node) seems to be just impossible in Analyze.
    I saw that .LNA-files seem to have an entirely different file structure than .BRG-files; Saving the code as a .LNA-file (in order to Import the generated code) doesn't work either.

    Is there ANY workaround for this problem?

    Any help or nudge in the right direction is greatly appreciated!!!!!

    Best regards from The Netherlands,
    Bart,
    Coney Solutions.

    ------------------------------
    Bart Roeleveld
    Rabobank
    ------------------------------