On a related note: does anyone use multiple data directories for 1 model ? We can specify multiple folders in the crg file but I have never been a fan of it.
There was a very interesting idea in tm1forum (I couldn't find the thread) to separate DATA to 2 folders: CODE (.rux and .pro files) and DATA (other files); and commit changes in CODE folder to git or any other "put your favorite version control system".
On a related note: does anyone use multiple data directories for 1 model ? We can specify multiple folders in the crg file but I have never been a fan of it.
There was a very interesting idea in tm1forum (I couldn't find the thread) to separate DATA to 2 folders: CODE (.rux and .pro files) and DATA (other files); and commit changes in CODE folder to git or any other "put your favorite version control system".
Interesting. it’s similar to what Lotsaram said. The difficulty will be to split the new objects regarding their type and have similar objects in the same folder.
Best regards,
Wim Gielis
IBM Champion 2024
Excel Most Valuable Professional, 2011-2014 https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
qml wrote: ↑Fri Apr 12, 2013 10:37 am
I'm in favour of having a consistent folder structure for all environments - tm1s.cfg in the main folder and Data and Logging subdirectories sitting under that main folder too. Or any other way that is consistent. Since you can easily get the Logging directory path using GetProcessErrorFileDirectory, it is easy to construct a formula that will return the Data directory, no matter what the environment. Something along these lines: