Search results for query: *

This sorts out the problem: ApplySimple("concat(to_char(date2, 'YYYY'),(to_char(date2, 'MM')))") The attribute must have an attribute ID Form, as this applySimple only works as a Description Form.

Thanks reisw. I'll take a look at the Applysimple stuff & see if I can make sense of it. I spoke to MSTR yesterday who advised creating a solution in the database - ie a new column in the db that extracts the month for me. In addition to this, they also recommended creating a db table that...

I have a datetime field in the database, that I need to extract just the month from. I can do this in Oracle sql but I cannot figure out how to achieve this in MSTR. At the report front end, I can alter the format of the datetime which will give the Month, but I need to create an attribute to...

If you can get your DBA to review the SQL, they'll probably be able to advise on the most efficient tables/joins to use. Try to hit Indexed fields in your attribute ID's (again, check with your DBA if you're unsure which are indexed). Try to keep attributes simple (ie, don't complicate the...

A fix has been recommended by MicroStrategy (which works perfectly): The problem is with the Relationship between the tables. When using a Star Schema, the joins need to be Many To Many. Using a 1:Many relationship creates Cross Joins when used in a Star Schema set up.

I have 3 tables: A, B & C. A joins to B & B joins to C. When I pull data from A & B, or B & C, everything works fine, but the moment I pull from all 3 tables, I get a cross join on one table. Any ideas why the Join suddenly fails? All the objects are Attributes. The joins are...