The OneStream Community is temporarily frozen until June 29th due to the ongoing maintenance. Please read the blog post here to learn more.

Forum Discussion

kchampion's avatar
kchampion
New Contributor III
2 years ago

File Explorer Incoming workflow folders missing in copied applications

This post is to provide information about File Explorer Incoming workflow folders.  Based on what we've seen in our environments, when an application is copied, the new application does not contain the folder structure located at: 

\File Share\Applications\<Application Name>\Incoming\<Cube Root Name>_Cube\<Workflow Base Input Name>\<Workflow Import Name>

We noticed these folders were missing in our last application copy when we were trying to copy files through SIC and drop them into the workflow import folders since our requirement was to drop them there for users to manually import when they choose (instead of automatically loading the files through batch import from batch harvest).  

To fix this issue we exported the Workflows and re-imported them back into the copied application.  This triggered OneStream to create the cube root folders and workflow folders for the workflows that were imported.

Hope this helps someone else who might be running into the same issue.

Data Integration
FileSystem
Workflow

10 Replies

  • Krishna's avatar
    Krishna
    Valued Contributor
    2 years ago

    Thanks kchampion  for the information. It was useful. I have a follow up question. Did you use the Cloud Admin Tool to copy the application ? If that is the case and it is frequent I would recommend to create a support ticket as well.

     

     

    • kchampion's avatar
      kchampion
      New Contributor III
      2 years ago

      Hi Krishna,

      Most recently the issue occurred when OneStream copied applications for us as part of a request, but it happens also when I use Cloud Administration Tools to copy applications.  I logged a case with OneStream Support and they suggested for me to create a batch load DM from the Harvest folder, but that option doesn't meet our requirements and it doesn't fix the issue with the folders being missing.

      Thanks!

      Kathryn

  • SxD's avatar
    SxD
    New Contributor III
    2 months ago

    Surprised there aren't more likes for this. Thank you so much for being proactive and posting this!! I just ran into this issue on v9.1.

  • KH1's avatar
    KH1
    Contributor III
    2 months ago

    JackLacava​,
    Should the finding documented by Kathryn in v7 and by SxD in v9 be considered a bug?
    If so, how soon should this be fixed?
    TY.

  • KH1's avatar
    KH1
    Contributor III
    2 months ago

    OS Support just confirmed that this separation is BAU, not a bug.
    Recap below the insight from OS Support just now:

    "It's important to note, that this exists separately from the application on our end.
    It would require copying the "File Share" contents specifically if you want that to be included in an app copy.

    It would be important to show them as separate tickets as they are separate functions.
    It's the leading practice to have an audit trail in case of any related issues arise."

  • sameburn's avatar
    sameburn
    Icon for OneStream Employee rankOneStream Employee
    2 months ago

    File Share is a self-service directory which supports file storage external from the OneStreamApplication and System Databases.  Therefore it is not stored in the application database and represents a real UNC path on server(s).  Therefore this isn't a bug and is expected behaviour. 

    https://documentation.onestream.com/docs/Content/Design%20and%20Reference/System%20Tools/File%20Share.html?Highlight=file%20share

    Hope this helps clarify

     

    • SxD's avatar
      SxD
      New Contributor III
      2 months ago

      Is the best method to duplicate the file structure to do the export/import of workflow profiles or is there a better way to sync between two application?