Data validation (pick list) in TM1

[craig_karr]

I am new to TM1. When building my model, for some text formated cells I would like to have some kind of data validation. For example I have one column where the user should enter a relase month, in that column I would like to make a validation so that only the values I have in another dimension (the month dimension in this case) can be entered, or even better that the user could choose values from a pick list.

Otherwise if you have an open text field one user might enter January, one Jan and on Januayr (missspelled). How can I deal with this problem in TM1? In Cognos Planning I would have used a dlist formatted item

[OLAPBPMguy]

If you are using 9.5 then you simply define a picklist. This is covered reasonably well in the documentation.

If you are using earlier versions of TM1 then you would need to use Excel cell validation.

[craig_karr]

Thanks for your reply. I'm using 9.4 (or actually IBM Cognos Express). One limitation with Excel validation is of course that it could be overruled if data is entered directly into the cube

[craig_karr]

Does anyone know if these real pick lists available in 9.5 works in TM1 web as well? I have now used Excel data validation and it seems like it doesn't work in TM1 web

[OLAPBPMguy]

Excel cell validation certainly does work in TM1 Web!

In 9.5 picklists once defined work in all GUIs:
- Perspectives cube viewer
- Excel slices and active forms
- Web sheets
- Web cube viewer
- Contributor
- (& will also work in EV 9.5 once released ...)

[craig_karr]

I noticed now that the Excel validations that doesn't work in TM1 web is the ones where the list of allowed entries doesn't consist of a cell area but a list that has been written directly for example short lists like "Yes", "No"

[OLAPBPMguy]

Yes that's true, validation defined as a hardcoded list separated by commas doesn't work on the web.  Validation has to be defined from a range. (which is best practice anyway, as with any model, system or coding never a good idea to have hard-coded values lying around when you could use a defined variable or array instead.)