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
Data Imports
I have currently set up a new data source and associated transformation rules (and allocated to the appropriate workflow). Data importing is correctly working for 2022 time period, however I am getti...
Henning
OneStream Employee
OneStream EmployeeHi Jake, do you have the time mappings in place for the time period you are loading data to? You probably have, but that is the first thing to check. Are you using the same scenario for the load that returns the error? If not, do you have a mapping set up for this? Also this, you probably have in place.
Other than that, a few screenshots and more details might help.
Hi - I believe I have everything in place (as the import works perfectly fine for 2022, just not for any other year....
I have looked at the log and its generating the following error;
Time Outside Workflow View.............. 11
My Time generation is as follows (then M1,M2...etc in difference columns)
Dim sYear As String = api.Parser.DelimitedParsedValues(2)
Return sYear & "M1"
- Henning
Do you have more than one year in your load file? If so, did you set this to True?
This helped me load a 3 year plan from another consolidation system with a FACT table setup. Thanks!
Not got multiple years in my import
Makes it more confusing the 2022 works fine, is just an issue any other year. Maybe my Year / Month importing value is not working correctly ?
- Henning
It could be a lot of things, and with the very limited information that is provided here, it is hard to guess, as all we can do is assume. Sai did provide a good hint. The next step, once you ruled out the basics that I asked for (which we have to believe you are in place), you go step by step. Analyze what the difference is between the load that is working and the one that is not working. Make it simple, reduce it to a single row/column with one data cell only. Then write your string variables (and anything else for that matter) in the error log and check whether this is all as expected. It is similar to working on a huge jigsaw puzzle. Hard work and frustrating, but in the end diligence pays off and you will probably slap your forehead.
