No Valid Data Keys in File.

[wm2]

How do you add a data key to a OneStream application?

[FredLucas]

Hi @wm2, not sure what you mean, can you elaborate further? 

[wm2]

Sorry, data keys in terms of scenario and time. This is the report I am receiving and the error message:

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.

[FredLucas]

Thanks @wm2. You get this error when your file contains no data to be imported.

This is usually due to issues in your data source and/or transformation rules set up.

From the log I can see that you have 41 rows in your source file but none of them is correctly mapping to a valid intersection. I'd start by ensuring that you have the one-to-one mappings for the Scenario and Time set up correctly.

[FredLucas]

After a closer look, the log is actually saying that all lines are non-numeric which seems to point to an issue with the definition of your amount column?

[wm2]

If I was using global POV for time and scenario, would I still need one to one rules and what would those look like?

And I should be uploading from a CSV right?

[FredLucas · Accepted solution]

Yes, the mappings for scenario and time are required even if using global POV.

Sure, the Delimited files sources accept the csv format.

I'd look into your amount column / definition as it seems to be resulting in a non-numerical value.

[wm2]

It was the amount column thank you so much

Last question, everything is working except for the view transformation rule

Do you know what the source value would be if the target value is YTD?

[FredLucas]

That's good news!

If the file brings YTD values, you may want to set a Static Value of YTD as part of your Data Source View Dimension and then make sure you have a One-to-One mapping defined that maps YTD to YTD.

[wm2]

do you know why it wont let me upload like this?

[FredLucas]

Can you try changing from Text to "Stored Text" on your Data Source View Dimension definition?

[wm2]

I tried that, that didn't work either. I can't think of any other settings that would ban that

[wm2]

Here is what is showing in OnePlace

[FredLucas]

That's a strange one, what is the import step showing?

Have you ensured there is no spaces on the YTD static value and mapping?

I'm assuming you've double clicked on the YTD member when defining the target value for the mapping rule?

[wm2]

I re-imported and for some reason that worked.

Ok serious last question now, you are actually the best.

With intersections:

I have the constraitns for entities and accounts like this:

Do you know how to fix this?