• State Suggested Answer
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 115 subscribers
  • Views 465 views
  • Users 0 members are here
Related

Agilent Knowledge Portal

Find maintenance, best practice, and troubleshooting articles.

Agilent Knowledge Portal

I'm working with OpenLab CDS 2.6. How do I define a default destination for .csv files to populate from the Reporting Tab?

jsugg

Our lab is currently trying to set up data transfer from OpenLab 2.6 to Sample Manager LIMS by generating reports as *.csv files that are sent to a destination folder for the LIMS to extract and post the results. I've created the report template in OpenLab and I'm able to generate the *.csv file as desired, but now I need to define a default destination for the files to populate so that we don't have to manually select the destination every time a report is generated.

I'm aware that I can define a destination path in the processing method menu but when I do this, the report generates automatically when the sample finishes running on the instrument before the technicians can review and validate the data. This would be okay except that the LIMS only pulls data from the first report and not the second which forces the technician to enter results manually into LIMS.

  • 0

    Hello,

    There is no way to set a default location for the report output tab in the CDS report tab. If you do not want the report created during the acquisition, then I would have the master method setup with no file copy but add the path. Then once the user has reviewed the data, switch back to windows file system, reprocess, and use the print all or print selected to create the report and copy to the central path. 

    Marty

  • 0
    Thank you, Martin.
     
    I’m listing the workflow steps below to make sure I’m understanding you:
     
    1. Create a master processing method that defines the report template and file destination but check “none” option in the field “Copy report to folder”.
      • This will make it so that a report is not generated to the destination folder when the samples are run on the instrument.
    1. After reviewing the results, the user modifies the processing method by selecting “Windows file system” option in the “Copy report to folder” field.
    2. The user saves the method, reprocesses and saves the results, and selects “Print” to generate the report as a *.csv in the defined file location.
      • Note: the user does not update the master method when the method is saved.
     
    Is this a correct assessment of what you described below?
     
    [Edited by Moderator to remove personal information] 
  • 0 in reply to jsugg

    Hello,

    Yes, that is correct. If for some reason the users need to update the master method make sure they do so before they change the report section. There is another option, but it would depend on how the AICs are setup.  If the AICs are setup so that the instrument service is running as system account not a service account, you could take advantage of that system account not having access to network shares. The acquisition essentially just fails to copy the file to the requested drive since it does not have access, this will give an error in the background logs but will not cause any issues with the sequence or results. You can then leave the method setting alone and when the user clicks print the system will copy the file based on the client system OS users to that network share. I know a couple of systems where they are taking advantage of this unintended workflow based on the permission failure.  

    Marty

Was this helpful?
Privacy Statement
Terms of Use
Contact Us
Site Help