Skip to main content
J
JakeBrown
September 28, 2022

Data Imports

  • September 28, 2022
  • 2 replies
  • 0 views

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 getting the following error in any other time period......

I have got the Scenario as 'Current Datakey' and Time as matrix datakey in my columns

Summary: No valid DataKeys (Scenario / Time) found in data source.  Review the source data load processing log and check one-to-one transformation rules to ensure that you have created proper Scenario and Time dimension rules for this data source.

 

Any ideas? I am assuming this might be one simple setting change somewhere 

2 replies

H
Henning
September 28, 2022

Hi 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. 

J
JakeBrownAuthor
September 28, 2022

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"

H
Henning
September 28, 2022

Do you have more than one year in your load file? If so, did you set this to True?


Henning_0-1664380486190.png

 

S
Sai_Maganti
September 28, 2022

Jake

Print the sYear to error log and see what you get. Sometimes there might be a space etc. I assume you have a transformation rule for all the time periods you're loading data to. Are you able to see any data rows in the log file?

Sai

J
JakeBrownAuthor
September 29, 2022

Hi Sai 

We are reasonably new to OneStream.... Do you have any guidance on how to print the SYear to error log?

I think this is what is causing the issue as I have just enabled multi year loads and my file (when trying to load into 2019) imported into 2022. Therefore making my think my sYear formula is defaulting to 2022 on all import years

Jake

S
Sai_Maganti
September 29, 2022

Jake

Add the following line after you declare the sYear. Then you can check what is being output in the error log.

brapi.ErrorLog.LogMessage(si, sYear)

Sai

Terms & ConditionsAccessibility statement