My timescale of historical data is correctly identified when no attributes are included in the data collection... The problem occurs when Attributes are added (and the attributes do not have timescale, so i don't see where my timescale is incorrrect).
What an akward issue. Thank you for your help anyway.
Thank you for your response. Yes, I submitted a support request a few days ago, but the problem was not resolved, so I still seek for help.
Do you have any examples or experience with any set of attributes that were succesfully added to data collection? Maybe such a blueprint could serve as an inspiration. I made numerous attempts to set up the attributes, but it always ends with a collection failure.
Re: PlanIQ - failure to add Attributes in Forecast Model
I messed around with my data collection, and I finally made it work.
The change that made this error go away was adding a letter to the codes of my Item Unique Identifier list, which only contained numbers previously. For example, I changed my codes from being 6010125204 to A6010125204.
Is it possible that the error came from the fact that PlanIQ would read my item ID as 6.01E+09 instead of 6010125204 because of the .csv export? Adding a letter forced the .csv file to display the whole string.