Data360 Analyze

 View Only
Expand all | Collapse all

git/source control for LNA/data flow files

  • 1.  git/source control for LNA/data flow files

    Posted 01-18-2021 06:58

    What's the latest guidance on performing source control for Analyze?

    Our current routine for development is:

    - open the existing data flow, Save As and increment the version tag (all flows have a suffix e.g. "[v12]" for twelfth iteration

    - place the older version into "_archive" subdirectory

    - after new version finalised, export it as LNA and commit this from local machine up into repository

    - this doesn't allow line-by-line diff (e.g. as you'd see with XML format) but at least offers an extra layer of clarity & security with respect to versioning and backups



  • 2.  RE: git/source control for LNA/data flow files

    Employee
    Posted 01-19-2021 04:02

    Unfortunately, there is no 'one size fits all' approach to version control as the details of the SDLC process will vary between different organisations. You may want to investigate this article that provides a mechanism to automatically export all data flows/ data flows that have been modified. When a data flow is exported the .lna filename includes the datetime stamp of the export.



  • 3.  RE: git/source control for LNA/data flow files

    Posted 08-09-2023 08:58

    Any update on this from Precisely? The linked article does not exist anymore...



    ------------------------------
    Jonas Sinnaeve
    Data Trust Associates
    ------------------------------



  • 4.  RE: git/source control for LNA/data flow files

    Employee
    Posted 08-09-2023 11:17

    The AnalyzeCli tool can be used to export multiple data flows. Information on the AnalyzeCli tool is here:

    https://help.precisely.com/r/Data360-Analyze-CLI/main/en-US/Data360-Analyze-CLI-Help/Latest-release-Build-639

    After logging into the Analyze server, the 'export' command enables you to export all data flows recursively from a specified point in the directory structure or perform a full dump:

    analyzeCli --host <hostname> --port <Port> export -R -f "<Destination_File.zip>" <Analyze_Directory_Path>

    For example:

    ## Export data flows from a specified point in the directory structure

    analyzeCli --host https://analyze.example.com/ --port 443 export -R -f "C:/temp/export_Adrian_2023-08-09.zip" /Users/Adrian

    ## Export all data flows in the system

    analyzeCli --host https://analyze.example.com/ --port 443 export -R -f "C:/temp/export_All_2023-08-09.zip" /



    ------------------------------
    Adrian Williams
    Precisely Software Inc.
    ------------------------------



  • 5.  RE: git/source control for LNA/data flow files

    Posted 08-11-2023 03:07

    Thanks for the information. I was able to install and login into Analyze CLI.

    But when trying to execute your last command to export all data flows, I'm getting this error: 

    Any advice?



    ------------------------------
    Jonas Sinnaeve
    Data Trust Associates
    ------------------------------



  • 6.  RE: git/source control for LNA/data flow files

    Employee
    Posted 08-14-2023 17:03

    Instead of exporting everything using "/", try exporting "/Users" or "/Public Documents".  I've run into trouble exporting every single object by specifying the root folder.  Maybe the new version will fix it.



    ------------------------------
    Ernest Jones
    Precisely Software Inc.
    PEARL RIVER NY
    ------------------------------



  • 7.  RE: git/source control for LNA/data flow files

    Posted 08-17-2023 08:15

    So for the moment there is now way to export all dataflows at once? Still a manual export then?



    ------------------------------
    Jonas Sinnaeve
    Data Trust Associates
    ------------------------------



  • 8.  RE: git/source control for LNA/data flow files

    Employee
    Posted 08-17-2023 10:58

    All of the data flow assets that are created by users of a Data360 Analyze system will be created under either the "/Users" or "/Public Documents" directories of the Analyze directory structure.

    Using a script with two AnalyzeCli export commands which specify the two path names will have the effect of exporting all of the users' data flows.

    In addition if you have modified the default  'Data360 Failed Schedule Email Notification V2.0' data flow in the "/Data360 Services" directory then you should export the contents of that directory too. 



    ------------------------------
    Adrian Williams
    Precisely Software Inc.
    ------------------------------



  • 9.  RE: git/source control for LNA/data flow files

    Posted 08-23-2023 10:05

    I've found the command to export the dataflows; but when running I always get this error:

    ERROR: export: Export to 'Action_LeadingDataSubdomain (UAT)' failed, status code: 400

    And only part of the flows is exported. Please note that the file is related to a schedule added to the Data Flow



    ------------------------------
    Jonas Sinnaeve
    Data Trust Associates
    ------------------------------



  • 10.  RE: git/source control for LNA/data flow files

    Employee
    Posted 08-24-2023 06:45

    I understand there is a new release of AnalyzeCli that will be released in the next couple of weeks which fixes some bugs relating to the export functionality.



    ------------------------------
    Adrian Williams
    Precisely Software Inc.
    ------------------------------



  • 11.  RE: git/source control for LNA/data flow files

    Employee
    Posted 08-24-2023 07:04

    It is not possible to export Schedules and Run Property Sets. Separating your data flows from other objects may allow the export to succeed in the interim.



    ------------------------------
    Adrian Williams
    Precisely Software Inc.
    ------------------------------