Search results for query: *

JerDale, where does the current "number of business days" come from? Is it already defined as a form of your Month attribute?

Is the Volume fact at the Product x Month level? Or is it a lower level on the time hierarchy?

What level is your Volume fact stored at on the fact table? Is it on multiple fact tables with different levels?

Oh, right! Now I remember! I never use it; it's too buggy. It's probably choking on you because you're using it to define two attributes that are directly related. Just use aliases.

TJM2, I'm sorry. You're absolutely right. My interpretation was that the report would contain the Year attribute in the column heading and a single YTD metric. The user would select 2/15/2005 and 2/15/2004 in the attribute element prompt and this would give two columns, 2005 and 2004, in the...

A report filter with the proper Attribute Join settings should do it.

What is an attribute role? Is this a new 7.5 feature? Based on what you are describing, though, it sounds like the existing Table Alias feature. Go into the Schema Objects\Tables folder. Right-click on the Employee table, and select Create Table Alias from the pop-up menu. Rename this table...

You can point the report to a specific XSL, and modify that XSL to not display the attribute name for that specific attribute. Someone else on the forum can help you with that. I need a refresher.

Are you displaying in Desktop or Web?

where b.calldate='2004-08-24 10:29:42.000' OR b.calldate IS NULL

TJM2, I don't think that your approach would work. If the transformation is done right, a filter isn't necessary. Just to review: The purpose of a transformation is to take a single attribute element and transform it into one or more different elements. A Last Year transform would take one...

I've had to do this before. You have an attribute that you need to be called A in some reports and B in others. Let A refer to the attribute with the long name. Let B refer to an attribute with the abbreviated name. Just build another attribute B one-to-one parent of the attribute A. Use B...

Ah... You simply need an extra version each of the Qty 1 and Qty 2 metrics. In this extra version, set the dimensionality to ignore the Group filter. We'll call these Qty 1 A and Qty 2 A. Place them in the report filter in a "[Qty 1 A] > 0 Or [Qty 2 A] > 0" filter expression. This way, when...

Oops, sorry. Didn't see the Prompt the first time around. Why are you filtering on ID in the subquery? As it stands currently, you will get a list of names and addresses with names shown only for the IDs chosen. The prompt won't filter the addresses returned. Is this what you want? Is this...

It's not a VLDB setting. Your PAY_PERIOD_END_DATE attribute isn't set up properly. You probably have two forms in your ID attribute form group. The first form is "PAY_PERIOD_END_DATE". The second form is "PAY_PERIOD_END_DATE - 365". Both forms are grouped in the ID form group. Is this...

Hmm, as I understand it you want a report that has a separate page for each Group attribute element. On that page, you want Qty 1 and Qty 2 only for that Group attribute element, but you want to display every Prov, even if there are no records in the fact table for that Prov. For those rows...

I'd like to second nlim's concerns. The speed of the query is important, but less important than the configuration on the app server. When you load a list of elements, the list isn't loaded directly from the table to the client. It enters the attribute element cache on the app server; memory...

How often will you be using the subquery?

Add an attribute named "Activity Join" to the activity table, with one expression in the ID form. This expression should simply be '1'. Add a attribute form value filter to your report, with "[Activity Join]@ID = 1" as the filter expression. MSTR will add the Activity table to the report SQL...

Yes, but it's not a good solution. Attributes have dimensionality; they are fixed in place at a given level in a dimension. If you want to create an object that only works at the company level, this is adequate. A better solution is to create a metric using ApplyAgg. Metrics have no...