What do all the TM1 file extensions mean? Here we explain the file types and identify what each extension means for the data in your TM1 data folder.
TM1 in Memory Objects and Saved Files
TM1 Models (Servers) are stored in files on the server when the TM1 model is saved. When saving, the server translates the application server objects from memory onto the computers hard drive. From there they can be easily backed up or copied and deployed to a different server.
The following table identifies each object type and it’s saved file equivalent:
| TM1 Object | TM1 File Extension | Directory | Description |
| Cube | *.cub | Data | Data store |
| View | *.vue | Data | Pre-saved view of a cube |
| Dimension | *.dim | Data | Complete list of Elements or Measures to store data against in a cube |
| Rules | *.rux | Data | The formulae that determine how things are calculated in cubes and pull data from other cubes. |
| Process | *.pro | Data | TI Processes – used to load data, update dimensions and manage the model |
| Chore | *.cho | Data | Scheduled jobs |
| Set | *.sub | Data | Selection of Elements or Measures from a dimension |
| Feeder | *.feeder | Data | Contains all the specific feeders generated by the fewer commands in rules. |
| Blob | *.blb | Data | Style and Formats of a view and temporary files for rules |
| Message log | Tm1sTIME.log | Log | Logs of all activity in TM1 |
| Process Log | Tm1ProcessErrTIME.log | Log | Logs of all TI Process Errors |
TM1 Control Objects
In your TM1 model there are control objects that are hidden unless you explicitly choose to view them. They are all named with a curly bracket (a “{” ) at the start of the object name. These are also saved to disk when the model is saved and are stored in the file system with the same curly bracket as the first character. Obviously they are also saved with the same TM1 file extensions as the rest of the model.
to view TM1 Control Objects, just got to the View menu in Architect and select Display Control Objects.
Temporary TM1 Files
When saving, TM1 produces files one by one, each time appending a ‘$’ to the filename until the output of that file is complete. After it is saved the server deletes the original and renames the file, removing the appended ‘$’.
