Hi, We are using Excel for importing PK and plasma concentration data to a screening database. For QC purposes we would like to have an export time stamp in the history sheet for comparison. Is this possible or is there another (easy) way of comparing exported Excel worksheets with phoenix result worksheets? BR Carsten
Hi Carsten, I am not sure if I fully understand the question. What output are you exporting via Excel, a full object (like NCA) via the browser or individual results worksheets? Which timestamps are you trying to compare? I will try to help if I better understand the question. Thanks, Ana
Carsten - another idea to consider - if you want move data directly to another data base would ODBC be better without having an interim file exported.transferred and imported? This functioanilty is licensed by Phoenix Connect but could enable a direct link to your database (also for import e.g. an example is provided for a simple Watson import). Simon
Hi Ana & Simon, To specify a little further. We use standardized workflows in PHX to generate NCA PK data from PK screening, profiling and characterization studies. Furthermore, we calculate descriptive stats on both the obtained Cplasma and PK data. The descriptive stats worksheets are exported to Excel and the PK and Cplasma data imported together via Excel to the data base: During this process a link between Cplasma and PK data is generated, but also references to other datbases; compounds and protocols are incorporated. If “export to excel” timestamps were possible to generate in the history sheets of the descriptive stats workbooks. We would accept comparing the timestamps for export and time for file creation for QC purposes. I’m not a database specialist so I can’t comment on the ODBC solution but pass the information on to someone else. BR Carsten
Hello Carsten, I think I understand what you are requesting. I am not sure this is technically possible but I will discuss with Pharsight developers for consideration on a future release (not 1.3 which is about to be released at the end of this month). Your request is that the action of exporting a file is recorded in the history. I think there are some difficulties with this but I have logged it for consideration - QC 11864. You might want to consider doing the following and see if this works best for you. Highlight the workflow where the descriptive stats is located. Right click and choose ‘Dependencies’. Save in an empty folder the default option (xml). Click yes to open dependencies and you will see an .xml file in explorer. From there you can access all the results (have really been exported) and they are linked to the Phoenix project. This might not work for you but it is worth investigating. Ana
Hello Carsten, I think I understand what you are requesting. I am not sure this is technically possible but I will discuss with Pharsight developers for consideration on a future release (not 1.3 which is about to be released at the end of this month). Your request is that the action of exporting a file is recorded in the history. I think there are some difficulties with this but I have logged it for consideration - QC 11864. You might want to consider doing the following and see if this works best for you. Highlight the workflow where the descriptive stats is located. Right click and choose ‘Dependencies’. Save in an empty folder the default option (xml). Click yes to open dependencies and you will see an .xml file in explorer. From there you can access all the results (have really been exported) and they are linked to the Phoenix project. This might not work for you but it is worth investigating. Ana