About DmitrySorokin

Hi manuebilly,   I don't like too many nested if statments either.  My preference would be to use mapping instead of formula. I would create a list "age list" of  values from 1 to 100 (or whatever is reasonalble) and then create a property Bracket formated as list Age Bracket. Then mannually map every age value to the Age Bracket list - only takes one time.  In your module you already have 2 line items age (as number) and age bracket (as list) I would create one more line item:  age list = finditem(age list, text(age)) and then use formula in your age bracket line item: Age Bracket = age list.Bracket [lookup: age list] You will have blanks for all values above 100, so I would adjust formula like this: Age Bracket = if isblank( list.Bracket [lookup: age list] ) then "above 100" else list.Bracket [lookup: age list].   Hope that helps, Dmitry ... View more

Hi pvijayateja,   1. Views do not take up extra space. Only modules do. You could see the number of Cells that moudles take up within each Model. The biggest one are easy to identify and usually they have too many dimensions to allow all sorts of slices for the user. I try to keep number of dimensions in the module to maximum three or four including time and versions.  2. The only way to know which dashboards are using the view is to have a very good description for your view, something like: Headcount View for CFO Dashboard. However, keep in mind that over time, CFO Dashboard maybe renamed to Exec Dashboard which is a problem.  3. If you delete the view, it is NOT going to disappear from the dashboard. However, you won't be able to publish that exact view again to other dashboard unless you re-create it again. What is important though, if you delete the view that was used for any of your export actions, then your action will not work again, it won't find the source of data. So you will have to 'record' that action again. You can review which views are used for any of the actions within your model by going to Model Settings-> Actions-> Imports and look over Source Object column. Keep in mind, that there maybe other Models that use the View and you won't find out unless you remember. That is why it is important to have a well descriptive name for your views with info where they are used.    Thanks and let me know if that helps, Dmitry ... View more