TM1 Cloud chores
Posted: Wed Mar 11, 2015 2:08 pm
Hi,
I am getting the following warning in Performance Modeler every time I'm moving from "Data Source" tab to "Maps" tab in TI process:
"Warning
The "Location of the file accessible from the Cognos TM1 server" field is not specified properly or the specified file can not be accessed from the TM1 server. For a process to run when scheduled as part of a chore, the file location must be accessible from the TM1 server. If you do not specify a proper file location, it will not be possible to schedule a refresh of the data using a chore."
I don't know what this could be about since all the CSV-files I use are located on the network drive where they to my understanding are meant to be. The field "Location of the file accessible from the Cognos TM1 server" in File Details is empty, and I've tried typing the data directory etc. in this field but the same error occurs regardless.
Therefore I'm afraid I will not be able to automate the processes with chores when moving into production. I wonder if I should be worried about this warning?
I am getting the following warning in Performance Modeler every time I'm moving from "Data Source" tab to "Maps" tab in TI process:
"Warning
The "Location of the file accessible from the Cognos TM1 server" field is not specified properly or the specified file can not be accessed from the TM1 server. For a process to run when scheduled as part of a chore, the file location must be accessible from the TM1 server. If you do not specify a proper file location, it will not be possible to schedule a refresh of the data using a chore."
I don't know what this could be about since all the CSV-files I use are located on the network drive where they to my understanding are meant to be. The field "Location of the file accessible from the Cognos TM1 server" in File Details is empty, and I've tried typing the data directory etc. in this field but the same error occurs regardless.
Therefore I'm afraid I will not be able to automate the processes with chores when moving into production. I wonder if I should be worried about this warning?