|
Home > Archive > MS SQL Server OLAP > March 2006 > Attribute relatioships not working?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Attribute relatioships not working?
|
|
|
| Hi,
I was working my way through the SSAS Tutorial. In lesson 5, the
SaelsQuota measures are introduced. The granularity of this
measuregroup for the time dimension is Calendar Quarter. This is
defined in the dimension usage tab. So far so well.
The thing that I can not get working correctly is the fact that the
data cannot be viewed by the fiscal calendar hierarchy. An attribute
relation has been defined for the Calendar Quarter attibute to link it
to the Fiscal Quarter attribute. The linked attribute show correctly in
the cube browser. But placing the fiscal calendar on the rows does not
show data correctly. Each shown sales Quota figure contains the cubes
total sales quota figure.
Has anyone experienced the same problem? Any ideas why this is not
working?
Marc
| |
| Darren Gosbell 2006-02-28, 8:30 pm |
| I think you may have made a small error during lesson 4. There should
not be an attribute relationship between Calendar Quarter and Fiscal
Quarter. When you are defining attribute relationships for navigation
hierarchies, an attribute needs to have a relationship to it's "parent"
level.
So Calendar Quarter should have a many-to-one relationship with Calendar
Semester (which has a relationship with Calendar Year). The same pattern
is true for the Fiscal Hiearchy, Fiscal Quarter has a relationship to
Fiscal Semester and Fiscal Semester has a relationship to Fiscal Year.
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
In article <1141029691.600052.7450@v46g2000cwv.googlegroups.com>,
marc.sanders@nippur.nl says...
> Hi,
>
> I was working my way through the SSAS Tutorial. In lesson 5, the
> SaelsQuota measures are introduced. The granularity of this
> measuregroup for the time dimension is Calendar Quarter. This is
> defined in the dimension usage tab. So far so well.
> The thing that I can not get working correctly is the fact that the
> data cannot be viewed by the fiscal calendar hierarchy. An attribute
> relation has been defined for the Calendar Quarter attibute to link it
> to the Fiscal Quarter attribute. The linked attribute show correctly in
> the cube browser. But placing the fiscal calendar on the rows does not
> show data correctly. Each shown sales Quota figure contains the cubes
> total sales quota figure.
>
> Has anyone experienced the same problem? Any ideas why this is not
> working?
>
> Marc
>
>
| |
|
| Hi Daren,
Thank you for your response. At the end of lesson 4 everything still
works fine. It is the last chapter of lesson 5 where things get weird.
In this chapter the sales-quota data is added. The granularity of that
data is at calender quarter level. This is defined in the dimension
usage tab, and works fine. Also aggregating from calender quarter to
calender semester and year works fine.
But the tutorial states that the data could also be aggregated via the
fiscal hierarchy by creating an attribute relationship between the
calendar quarter and the fiscal quarter.
I quoted the actual text in the tutorial:
--
"Notice that although Calendar Year is linked to Calendar Quarter
through the Calendar Semester attribute, the fiscal calendar attributes
are linked only to one another; they are not linked to the Calendar
Quarter attribute and therefore will not aggregate correctly in the
Sales Quotas measure group"
--
I agree that it seems a bit strange that this would work. But he, I am
just following the tutorial. Wel it does not work. I cannot reproduce
the screen as shown in the tutorial for displaying sales-quota per
members of the fiscal hierarchy.
If you have the time, you should really try it. I wonder If you can
reproduce the last picture of lesson 5.
ind regards,
Marc
Darren Gosbell schreef:
[color=darkred]
> I think you may have made a small error during lesson 4. There should
> not be an attribute relationship between Calendar Quarter and Fiscal
> Quarter. When you are defining attribute relationships for navigation
> hierarchies, an attribute needs to have a relationship to it's "parent"
> level.
>
> So Calendar Quarter should have a many-to-one relationship with Calendar
> Semester (which has a relationship with Calendar Year). The same pattern
> is true for the Fiscal Hiearchy, Fiscal Quarter has a relationship to
> Fiscal Semester and Fiscal Semester has a relationship to Fiscal Year.
>
> --
> Regards
> Darren Gosbell [MCSD]
> Blog: http://www.geekswithblogs.net/darrengosbell
>
> In article <1141029691.600052.7450@v46g2000cwv.googlegroups.com>,
> marc.sanders@nippur.nl says...
| |
| klm@ag 2006-03-05, 8:35 pm |
| Marc,
I had a hard time with this part of the tutorial as well. I've copied below
what I eventually ended up with in my Time dimension, and this fixed my
problem as far as the end of Lesson 5 is concerned.
Now I'm having different problem with Lesson 7. If you can figure this one
out, please post your solution. After building the first KPI for Reseller
Sales compared to the Quota Amount (Goal Value), the filter on the Fiscal
Year does not work. It shows the lump Quota Amount for all fiscal years, but
it does filter the Reseller Sales amount correctly. When I go to the Browser
tool for the cube, place Sales Quota Amount on the detail pane, place Fiscal
Year 2004 on the rows or in the Filter, it works fine. However, when I place
Fiscal Year 2004 in the SubCube area, it doesn't work so I'm guessing the KPI
Browser filter works like a subcube. At the same time, if I use Calendar
Year in the SubCube area, I don't experinece the problem so I'm thinking it
still has something to do with the Time Dimension, but I'm at a loss on this.
Good luck!
Calendar Quarter
Relationships: Calendar Semester and Fiscal Quarter
Calendar Semester
Relationship: Calendar Year
Calendar Year
Date
Relationship: Month Name
Fiscal Quarter
Relationship: Fiscal Semester
Fiscal Semester
Relationship: Fiscal Year
Fiscal Year
Month Name
Relationships: Caledar Quarter, Fiscal Quarter, Month Number of Year
Month Number of Year
"Marc" wrote:
> Hi Daren,
>
> Thank you for your response. At the end of lesson 4 everything still
> works fine. It is the last chapter of lesson 5 where things get weird.
> In this chapter the sales-quota data is added. The granularity of that
> data is at calender quarter level. This is defined in the dimension
> usage tab, and works fine. Also aggregating from calender quarter to
> calender semester and year works fine.
>
> But the tutorial states that the data could also be aggregated via the
> fiscal hierarchy by creating an attribute relationship between the
> calendar quarter and the fiscal quarter.
> I quoted the actual text in the tutorial:
> --
> "Notice that although Calendar Year is linked to Calendar Quarter
> through the Calendar Semester attribute, the fiscal calendar attributes
> are linked only to one another; they are not linked to the Calendar
> Quarter attribute and therefore will not aggregate correctly in the
> Sales Quotas measure group"
> --
>
> I agree that it seems a bit strange that this would work. But he, I am
> just following the tutorial. Wel it does not work. I cannot reproduce
> the screen as shown in the tutorial for displaying sales-quota per
> members of the fiscal hierarchy.
>
> If you have the time, you should really try it. I wonder If you can
> reproduce the last picture of lesson 5.
>
> ind regards,
> Marc
>
>
>
> Darren Gosbell schreef:
>
>
>
| |
| klm@ag 2006-03-05, 8:35 pm |
| Commenting out the calculations from "SCOPE (ROOT());" to the end of the
script, fixed the problem I was having in the Analysis Services tutorial,
Lesson 7, where the Goal value did not show up as $43,240,000.00 after
filtering on Fiscal Year 2004. (It had been showing the total sales quota
amount).
The calculations that I commented out had been added in the last section of
Lesson 6.
Now my question is how do I put the scope statements back in so that Fiscal
Year 2005 quota amounts are calculated without messing up the KPI Goal value
when filtering on Fiscal Year?
"klm@ag" wrote:
[color=darkred]
> Marc,
>
> I had a hard time with this part of the tutorial as well. I've copied below
> what I eventually ended up with in my Time dimension, and this fixed my
> problem as far as the end of Lesson 5 is concerned.
>
> Now I'm having different problem with Lesson 7. If you can figure this one
> out, please post your solution. After building the first KPI for Reseller
> Sales compared to the Quota Amount (Goal Value), the filter on the Fiscal
> Year does not work. It shows the lump Quota Amount for all fiscal years, but
> it does filter the Reseller Sales amount correctly. When I go to the Browser
> tool for the cube, place Sales Quota Amount on the detail pane, place Fiscal
> Year 2004 on the rows or in the Filter, it works fine. However, when I place
> Fiscal Year 2004 in the SubCube area, it doesn't work so I'm guessing the KPI
> Browser filter works like a subcube. At the same time, if I use Calendar
> Year in the SubCube area, I don't experinece the problem so I'm thinking it
> still has something to do with the Time Dimension, but I'm at a loss on this.
>
> Good luck!
>
>
> Calendar Quarter
> Relationships: Calendar Semester and Fiscal Quarter
>
> Calendar Semester
> Relationship: Calendar Year
>
> Calendar Year
>
> Date
> Relationship: Month Name
>
> Fiscal Quarter
> Relationship: Fiscal Semester
>
> Fiscal Semester
> Relationship: Fiscal Year
>
> Fiscal Year
>
> Month Name
> Relationships: Caledar Quarter, Fiscal Quarter, Month Number of Year
>
> Month Number of Year
>
>
>
>
> "Marc" wrote:
>
| |
| Darren Gosbell 2006-03-05, 8:36 pm |
| Marc,
I have come across one possible solution after having a play in the
Adventure Works sample. When I had Calendar Quarter under Fiscal
Quarter, I got the results you described. Is it possible that you were
using this configuration?
When I dragged Fiscal Quarter under Calendar Quarter I got the correct
results.
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
In article <1141327994.520973.163670@i39g2000cwa.googlegroups.com>,
marc.sanders@nippur.nl says...[color=darkred]
> Hi Daren,
>
> Thank you for your response. At the end of lesson 4 everything still
> works fine. It is the last chapter of lesson 5 where things get weird.
> In this chapter the sales-quota data is added. The granularity of that
> data is at calender quarter level. This is defined in the dimension
> usage tab, and works fine. Also aggregating from calender quarter to
> calender semester and year works fine.
>
> But the tutorial states that the data could also be aggregated via the
> fiscal hierarchy by creating an attribute relationship between the
> calendar quarter and the fiscal quarter.
> I quoted the actual text in the tutorial:
> --
> "Notice that although Calendar Year is linked to Calendar Quarter
> through the Calendar Semester attribute, the fiscal calendar attributes
> are linked only to one another; they are not linked to the Calendar
> Quarter attribute and therefore will not aggregate correctly in the
> Sales Quotas measure group"
> --
>
> I agree that it seems a bit strange that this would work. But he, I am
> just following the tutorial. Wel it does not work. I cannot reproduce
> the screen as shown in the tutorial for displaying sales-quota per
> members of the fiscal hierarchy.
>
> If you have the time, you should really try it. I wonder If you can
> reproduce the last picture of lesson 5.
>
> ind regards,
> Marc
>
>
>
> Darren Gosbell schreef:
>
| |
|
| Hi darren,
The configuration of my time dimension is as described in teh tutorial.
Fiscal quarter is defined as an attribute of calendar quarter. And the
results are not OK. I have also tried to change the relationship the
other way around. But that did not work either. The I thought, maybe it
has something to do with the fact that the relationships are set to
"Rigid", so I changed those to "flexible". But that also did not solve
the problem.
I appreciate your attempts to help me with this.
Kind regards
Marc
| |
|
| Hi klm@ag
My time dimension exactly matches what you have. So I really am
confused why you get the correct results and I don't.
have you noticed that the browser "remembers" earlier set filters? Is
it possible that your data (in lesson 5) looks OK because a filter
still exists on the calender quarter?
For me the Fiscal quarter, semester and year are not working. Therefore
I also cannot help you with chapter 7. If I use the fiscal year 2004, I
get all data for all years. It doesn't matter if the filter area or
sub-cube area is used. If it works for you in one of teh cases, please
check if any filters are still active. There is a auto-filter button on
the browseers toolbar that you can use to turn auto-filter off.
The fact that the calender quarter does work OK is because all actual
data is actually stored at day level and can correctly be aggregated
along the fiscal and calendar hierarchies.
My guess is that the only way to make this work is to define calender
quarter somewhere in the fiscal hierarcy (calendar quarter as a child
of the fiscal quarter with a 1:1 relationship). I think I am going to
try that out. Afterall it suprises me that defining an attribute
relationship with a member is enough to create aggregated values along
another hierarchy. Normally aggregation is only done along the
hierarchies defined from the level of granularity of the fact data on
to the top of the defined hierarchies.
Kind regards
Marc
| |
| Darren Gosbell 2006-03-06, 7:24 am |
| Marc,
What I did to replicate your issue was to play with the sales target
measure in the adventure works sample. If you want to see this working
yourself, below are the step I took:
In the sample as it is deployed there is no relationship between fiscal
and calendar quarters. When you view the sales targets over fiscal
quarters you see no figures (the option to show null values or the
"All" value for unrelated attributes is configurable). Adding a
relationship under the calendar quarter for the fiscal quarter attribute
and then reprocessing the cube fixed this issue. (I set the relationship
up as a rigid, one-to-one relationship)
Cheers
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
In article <1141632452.423106.26280@p10g2000cwp.googlegroups.com>,
marc.sanders@nippur.nl says...
> Hi darren,
>
> The configuration of my time dimension is as described in teh tutorial.
> Fiscal quarter is defined as an attribute of calendar quarter. And the
> results are not OK. I have also tried to change the relationship the
> other way around. But that did not work either. The I thought, maybe it
> has something to do with the fact that the relationships are set to
> "Rigid", so I changed those to "flexible". But that also did not solve
> the problem.
>
> I appreciate your attempts to help me with this.
>
> Kind regards
> Marc
>
>
| |
| klm@ag 2006-03-08, 8:24 pm |
| Marc,
I did notice somewhere along the way that the browser remembers earlier set
filters. Unfortunately I haven't found a way to clear all of these at once,
but I did go back and make sure these filters were removed on the Calendar
hierarchy, and I'm still getting correct results based on the Fiscal
hierarchy.
I tried so many things to get this to work that it's hard to remember
exactly what it was that made a difference. I did change the relationships
to Flexible instead of Rigid, as you mentioned in another post. I also
verified that the other properties for the attributes and attribute
relationships were correct, but I don't recall a problem there.
There's one more thing that seemed strange to me at the time, but I thought
it had more to do with the filters I had set than the attribute
relationships. However, I'll throw it out here as something to try just in
case it may make a difference. At one point, it appeared to make a
difference whether I dragged the existing "Fiscal Quarter" attribute
RELATIONSHIP and placed it under "Calendar Quarter" as opposed to dragging
the "Fiscal Quarter" attribute itself under "Calendar Quarter". If you
haven't already tried this, you may want to delete the "Fiscal Quarter"
attribute relationship under "Calendar Quarter" and then drag the attribute
itself under "Calendar Quarter."
The theory above didn't seem to hold true after the problem disappeared so I
dismissed it, but maybe it fixed a problem that I've not been able to
duplicate.
"Marc" wrote:
> Hi klm@ag
>
> My time dimension exactly matches what you have. So I really am
> confused why you get the correct results and I don't.
> have you noticed that the browser "remembers" earlier set filters? Is
> it possible that your data (in lesson 5) looks OK because a filter
> still exists on the calender quarter?
>
> For me the Fiscal quarter, semester and year are not working. Therefore
> I also cannot help you with chapter 7. If I use the fiscal year 2004, I
> get all data for all years. It doesn't matter if the filter area or
> sub-cube area is used. If it works for you in one of teh cases, please
> check if any filters are still active. There is a auto-filter button on
> the browseers toolbar that you can use to turn auto-filter off.
> The fact that the calender quarter does work OK is because all actual
> data is actually stored at day level and can correctly be aggregated
> along the fiscal and calendar hierarchies.
>
> My guess is that the only way to make this work is to define calender
> quarter somewhere in the fiscal hierarcy (calendar quarter as a child
> of the fiscal quarter with a 1:1 relationship). I think I am going to
> try that out. Afterall it suprises me that defining an attribute
> relationship with a member is enough to create aggregated values along
> another hierarchy. Normally aggregation is only done along the
> hierarchies defined from the level of granularity of the fact data on
> to the top of the defined hierarchies.
>
> Kind regards
> Marc
>
>
| |
| Darren Gosbell 2006-03-09, 8:24 pm |
| In article <A7A29B51-8465-4A50-8D65- 4A95306C7B0A@microso
ft.com>,
klmag@discussions.microsoft.com says...
> At one point, it appeared to make a
> difference whether I dragged the existing "Fiscal Quarter" attribute
> RELATIONSHIP and placed it under "Calendar Quarter" as opposed to dragging
> the "Fiscal Quarter" attribute itself under "Calendar Quarter". If you
> haven't already tried this, you may want to delete the "Fiscal Quarter"
> attribute relationship under "Calendar Quarter" and then drag the attribute
> itself under "Calendar Quarter."
>
This is the same behaviour I am observing. I believe that because the
Measure Group is at a granularity of "Calendar Quarter" Analysis
Services needs to know what the relationship is from Calendar Quarter to
Fiscal Quarter.
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
| |
| klm@ag 2006-03-09, 8:24 pm |
| Darren,
Both Marc and I did exactly as the tutorial instructed us to do, including
creating an attribute relationship between Calendar Quarter and Fiscal
Quarter, as you suggested, but this did not fix the problem. We understand
that the granularity of the Measure Group is at the Quarter level. We
understand that the Calendar and Fiscal Quarters need to be related. We
followed the steps in the tutorial (Lesson 5: Defining Dimension Granularity
within a Measure Group, bottom of the page, Defining Attribute Relationships
Between the Calendar Quarter Attribute and the Other Dimension Attributes in
the Time Dimension). It didn't work. I spent a lot of time on this,
reworking the Time dimension, reading back through previous lessons in the
tutorial, etc. Eventually something I changed made a difference, but I'm not
sure what that was.
In my last post, I was making a distinction between the Fiscal Quarter
dimension attribute itself and the attribute relationship that was created
when the wizard process ran. That's the only other thing I can recall
changing that may have made a difference, as unlikely as it seems.
Is it possible that we are working with a different edition than you are?
I'm working with the Developer Edition. Did you follow the steps of the
tutorial for all of the lessons up thru Lesson 5, or did you create the cube
and dimensions in a different manner? It would be nice to know why the
instructions in the tutorial did not work. I would have to go back and start
from scratch, with the intial project that was installed with SQL Server 2005
to walk thru the steps, but I don't have time for that right now. I noticed
that you mentioned in another post that you reprocessed the cube. Did you
actually use the Process command or the Deploy command? The tutorial only
mentions having to run Deploy.
Thanks for sharing your thoughts on this.
"Darren Gosbell" wrote:
> In article <A7A29B51-8465-4A50-8D65- 4A95306C7B0A@microso
ft.com>,
> klmag@discussions.microsoft.com says...
>
> This is the same behaviour I am observing. I believe that because the
> Measure Group is at a granularity of "Calendar Quarter" Analysis
> Services needs to know what the relationship is from Calendar Quarter to
> Fiscal Quarter.
>
> --
> Regards
> Darren Gosbell [MCSD]
> Blog: http://www.geekswithblogs.net/darrengosbell
>
| |
|
| Thanks klm,
You very perfectly described the situation in tour reaction. I also use
the developer edition. To be exactly: Microsoft SQL Server 2005 -
9.00.1399.06 (Intel X86) Oct 14 2005 00:33:37 Copyright (c)
1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1
(Build 2600: Service Pack 2).
I also exprerimented with your idea's of using a "new" attribute
relationship in stead of the one already generated by the wizard in
earlier chapters. Something else I have tried is to phisically delete
the cube before deploying. Also changing from incremental to full
deployment did not solve the problem.
The longer I am struggling with this issue, th more I am comitted to
finding out why it won't work.
I created a new database with only the salesquota data and the time
dimension. My time dimension has both the fiscal and calendar
hierarchies, but I left out the levels below the fiscal quarter. If I
browse the cube via the calendar hierarchy everything is OK.
If I browse the cube by Fiscal Semester, I also see the correct data,
but I cannot view the data by fiscal quarter. Each fiscal quarter has
the value of the fiscal semester it belongs to. I am going to do some
further digging in this new database.
One interesting thing I have noticed is that if you reconnect in the
cube browser, the meta data pane is not (always) refreshed. I made som
significant changes in the time dimension. After reconnecting in the
cube browser, the data pane was refreshed, but the meta data remained
the same. Pressing F5 with the dimension or database object in the
metadata pane selected, actually refreshed the pane. One other thing
that crossed my mind is: could caching be part of the problem? I know
that data and meta data is cached on the server. I am going to do some
tests in that area as well.
I also have limited time to spend on this issue, but I keep you guys
posted with what I learn.
Marc
| |
| Darren Gosbell 2006-03-14, 7:24 am |
| Just to clarify that we are all working off the same version - I am also
running on the developer edition and I was using the "Deploy" command to
do the re-processing of the Olap database.
I had some time to work through this over the weekend. I was pretty sure
the issue hinges around two key areas, either the relationship between
the time dimension and the fact table or the configuration of the time
dimension itself.
I worked through the tutorial from lesson 4 onwards and initially found
that I was able to reproduce your issue. What I found (which surprised
me a little) was that I had missed adding the two quarter attribute
relationships under the "Month Name" attribute. Below is the
relationships I have setup in my time dimension.
Calendar Quarter
- CalendarSemester
- Fiscal Quarter
Calendar Semester
- CalendarYear
Calendar Year
-
Date
- EnglishMonthName
Fiscal Quarter
- Fiscal Semester
Fiscal Semester
- Fiscal Year
Fiscal Year
-
Month Name
- Fiscal Quarter
- CalendarQuarter
When my time dimension is set up as above it all just works the way the
tutorial says it should. If I remove the attribute relationships under
"Month Name" the fiscal hierarchy "breaks" and I just see the total
figure again. I have not quite work out why this is happening this way,
by I assume if has something to do with the fact that the dimension is
related to the fact table in the DSV through TimeKey (which is the
"Date" attribute)
--
Regards
Darren Gosbell [MCSD]
Blog: http://www.geekswithblogs.net/darrengosbell
In article <7CED4110-B0DF-4800-91FE- FFC812FCD31C@microso
ft.com>,
klmag@discussions.microsoft.com says...[color=darkred]
> Darren,
>
> Both Marc and I did exactly as the tutorial instructed us to do, including
> creating an attribute relationship between Calendar Quarter and Fiscal
> Quarter, as you suggested, but this did not fix the problem. We understand
> that the granularity of the Measure Group is at the Quarter level. We
> understand that the Calendar and Fiscal Quarters need to be related. We
> followed the steps in the tutorial (Lesson 5: Defining Dimension Granularity
> within a Measure Group, bottom of the page, Defining Attribute Relationships
> Between the Calendar Quarter Attribute and the Other Dimension Attributes in
> the Time Dimension). It didn't work. I spent a lot of time on this,
> reworking the Time dimension, reading back through previous lessons in the
> tutorial, etc. Eventually something I changed made a difference, but I'm not
> sure what that was.
>
> In my last post, I was making a distinction between the Fiscal Quarter
> dimension attribute itself and the attribute relationship that was created
> when the wizard process ran. That's the only other thing I can recall
> changing that may have made a difference, as unlikely as it seems.
>
> Is it possible that we are working with a different edition than you are?
> I'm working with the Developer Edition. Did you follow the steps of the
> tutorial for all of the lessons up thru Lesson 5, or did you create the cube
> and dimensions in a different manner? It would be nice to know why the
> instructions in the tutorial did not work. I would have to go back and start
> from scratch, with the intial project that was installed with SQL Server 2005
> to walk thru the steps, but I don't have time for that right now. I noticed
> that you mentioned in another post that you reprocessed the cube. Did you
> actually use the Process command or the Deploy command? The tutorial only
> mentions having to run Deploy.
>
> Thanks for sharing your thoughts on this.
>
>
> "Darren Gosbell" wrote:
>
| |
| Dale Chilson 2006-03-29, 8:27 pm |
| Marc (and others experiencing this issue),
I too had the same issue at the end of lesson 5. I went back and
reviewed (rebuilt) the relationships but moving the main Fiscal Quarter
attribute under the Calendar Quarter <new attribute> did not work, as
most of us have noticed. What DID work for me though was ... I noticed
that there was a Fiscal Quarter attribute relationship under Month Name.
I dragged this relationship under Calendar Quarter, deployed, and
waalaa, it worked. For grinds, I recreated the Fiscal Quarter attribute
relationship under Month Name by dragging the Fiscal Quarter attribute
under Month Name. I again deployed and every thing still works. Give
this a try!
Dale
*** Sent via Developersdex http://www.droptable.com ***
|
|
|
|
|