Skip to main content
M
MarkusWipp
October 16, 2023

Data source with fixed UNC-Path

  • October 16, 2023
  • 3 replies
  • 0 views

Hi all, 

is there a possibility to create a data source and give it a fixed file-name on an UNC path instead of having to select it in the user-interface? e.g. assume I get the file always put to \\fileserver\sharename\subfolder\filename.csv and want to directly load from there.

If not, what would be the workaround?

Thanks

Markus

    3 replies

    N
    NicolasArgente
    October 17, 2023

    Hi MarkusWipp 
    It is not possible to use it like this. It would probably even be against security rules to link it directly to an external file. What if the file changes? Or its format changes? For example, if the source file changes and it adds a new column, then it would have an impact on your OneStream datasource definition. It would break the datasource that is defined in OS.
    So. Quick answer, not possible.
    Have a good day,
    Nic

    M
    MarkusWippAuthor
    October 26, 2023

    Hi NicolasArgente ,

    Thanks for your answer, but the file is really a highly standardized one and only the OS servers and the servers of the producing system have access to that path. So there should be no unexpected format change, etc.

    in the meantime I also had an incident open with OS and this was the reply:

    • Include a workspace step as the first step in a workflow (before import). The workspace has a button which executes a rule, the rule copies the file and automatically executes an import or alternatively copies the file to the incoming folder and then the user manually selects and loads.
    • Connector which copies file and reads the file into a DataTable then processes.
    • Automated process which copies files to the batch harvest folder and executes the import/load process.

    I'm now going with the second option and directly read the file from the UNC path into a data table.

    Thanks

    Markus

    N
    NicolasArgente
    October 26, 2023

    Hi MarkusWipp 
    The second one is pretty common. It would need probably some WinSCP dll to transfer the file. You will find more info on the Knowledge Base and also in the community.
    Now, that being said, I do not understand the reason you process like importing new file in your datasource if its format is not changing. I think I do not fully understand the issue, as this makes no sense to me. OR do you mean that the datasource is the same, but you need to update a new file in your workflow? (not in the datasource)
    Have a good day,
    Nic

    Terms & ConditionsAccessibility statement