KPI List Web Part in MOSS 2007 - How Do I Display an 'As of Date' For Indicators?

I have created an SQL 2005 SSAS cube with many different KPIs defined. In MOSS 2007 (SP2) I have created a site to display these various KPIs in several KPI Lists. Some of the indicators in the underlying cube are updated daily, others weekly, others quarterly, etc.

What are some ways to display to the user what date or time slice each specific indicator is "as of"?

Thanks in advance for any help you can provide.

-Steve

Hello. I do not think that there is a property in SSAS2005 that you can use for this.

The easy way is to create separate KPI:s depending on the time slice /or update window and simply name the KPI:s in SSAS2005 in this way.

I can think of ActSalesBudSalesMonth and ActSalesBudSalesYearToDate. I usually use shorter names.

Else I recommend you to find a property/information field in MOSS 2007

HTH

Thomas Ivarsson

KPI List Web Part in MOSS 2007 - How Do I Display an 'As of Date' For Indicators?

I have created an SQL 2005 SSAS cube with many different KPIs defined. In MOSS 2007 (SP2) I have created a site to display these various KPIs in several KPI Lists. Some of the indicators in the underlying cube are updated daily, others weekly, others quarterly, etc.

What are some ways to display to the user what date or time slice each specific indicator is "as of"?

Thanks in advance for any help you can provide.

-Steve

Hello. I do not think that there is a property in SSAS2005 that you can use for this.

The easy way is to create separate KPI:s depending on the time slice /or update window and simply name the KPI:s in SSAS2005 in this way.

I can think of ActSalesBudSalesMonth and ActSalesBudSalesYearToDate. I usually use shorter names.

Else I recommend you to find a property/information field in MOSS 2007

HTH

Thomas Ivarsson

Key and Index issues

I have a table without any key defined for it.
But I have an index comprising of 4 fields say -
1. Field1 Not Null
2. Field2 Can be Null
3. Field3 Can be Null
4. Field4 Can be Null
I have data in Field1 and Field2. However Fields Field3 and
Field4 are both Null.
Field1 = 'A' and Field2 = 'BB01' contain the same data
for two records.
I found this problem -
1. In the database I see two records
created for the above. The only difference being
the description in two records is different.
2. When I goto retrieve records using Access database,
it shows me 1st record twice.
'cause it shows the same description for both records.
How can I ensure that -
1. It won't create two records with the same key.
2. It should retrieve records correctly.
Thank you,
-M
"Me" <Me@.discussions.microsoft.com> wrote in message
news:B89EA964-D9B9-4AE4-97D0-F1A9B0232C74@.microsoft.com...
>I have a table without any key defined for it.
> But I have an index comprising of 4 fields say -
> 1. Field1 Not Null
> 2. Field2 Can be Null
> 3. Field3 Can be Null
> 4. Field4 Can be Null
> I have data in Field1 and Field2. However Fields Field3 and
> Field4 are both Null.
> Field1 = 'A' and Field2 = 'BB01' contain the same data
> for two records.
> I found this problem -
> 1. In the database I see two records
> created for the above. The only difference being
> the description in two records is different.
> 2. When I goto retrieve records using Access database,
> it shows me 1st record twice.
> 'cause it shows the same description for both records.
> How can I ensure that -
> 1. It won't create two records with the same key.
> 2. It should retrieve records correctly.
> Thank you,
> -M
>
>
Can you post the DDL to CREATE the table in question, some INSERT statements
to populate and then show us the results that you would like to get back? I
would have to make several assumptions here about your data and how it is
being used.
Rick Sawtell
MCT, MCSD, MCDBA
|||What is typical when you link or import a table in MS Access is that it will
ask for a key for the data, if you answer this question and provide some
columns, Access will give you the behavior you describe.
Drop the linked table and remap it, except, this time, when it asks for a
key, cancel the dialog. This will force Access to assume all columns for a
key and should provide you with the duplicate information.
Sincerely,
Anthony Thomas

"Me" <Me@.discussions.microsoft.com> wrote in message
news:B89EA964-D9B9-4AE4-97D0-F1A9B0232C74@.microsoft.com...
> I have a table without any key defined for it.
> But I have an index comprising of 4 fields say -
> 1. Field1 Not Null
> 2. Field2 Can be Null
> 3. Field3 Can be Null
> 4. Field4 Can be Null
> I have data in Field1 and Field2. However Fields Field3 and
> Field4 are both Null.
> Field1 = 'A' and Field2 = 'BB01' contain the same data
> for two records.
> I found this problem -
> 1. In the database I see two records
> created for the above. The only difference being
> the description in two records is different.
> 2. When I goto retrieve records using Access database,
> it shows me 1st record twice.
> 'cause it shows the same description for both records.
> How can I ensure that -
> 1. It won't create two records with the same key.
> 2. It should retrieve records correctly.
> Thank you,
> -M
>
>
|||If you don't specify any columns for the unique identifier
and there is no primary key, Access will assume there are no
columns that uniquely identify a record (rather than all
columns). This is why you end up with a read only recordset
when linking tables under such a scenario.
-Sue
On Sun, 14 Nov 2004 23:11:58 -0600, "AnthonyThomas"
<Anthony.Thomas@.CommerceBank.com> wrote:

>What is typical when you link or import a table in MS Access is that it will
>ask for a key for the data, if you answer this question and provide some
>columns, Access will give you the behavior you describe.
>Drop the linked table and remap it, except, this time, when it asks for a
>key, cancel the dialog. This will force Access to assume all columns for a
>key and should provide you with the duplicate information.
>Sincerely,
>
>Anthony Thomas

Key and Index issues

I have a table without any key defined for it.
But I have an index comprising of 4 fields say -
1. Field1 Not Null
2. Field2 Can be Null
3. Field3 Can be Null
4. Field4 Can be Null
I have data in Field1 and Field2. However Fields Field3 and
Field4 are both Null.
Field1 = 'A' and Field2 = 'BB01' contain the same data
for two records.
I found this problem -
1. In the database I see two records
created for the above. The only difference being
the description in two records is different.
2. When I goto retrieve records using Access database,
it shows me 1st record twice.
'cause it shows the same description for both records.
How can I ensure that -
1. It won't create two records with the same key.
2. It should retrieve records correctly.
Thank you,
-M"Me" <Me@.discussions.microsoft.com> wrote in message
news:B89EA964-D9B9-4AE4-97D0-F1A9B0232C74@.microsoft.com...
>I have a table without any key defined for it.
> But I have an index comprising of 4 fields say -
> 1. Field1 Not Null
> 2. Field2 Can be Null
> 3. Field3 Can be Null
> 4. Field4 Can be Null
> I have data in Field1 and Field2. However Fields Field3 and
> Field4 are both Null.
> Field1 = 'A' and Field2 = 'BB01' contain the same data
> for two records.
> I found this problem -
> 1. In the database I see two records
> created for the above. The only difference being
> the description in two records is different.
> 2. When I goto retrieve records using Access database,
> it shows me 1st record twice.
> 'cause it shows the same description for both records.
> How can I ensure that -
> 1. It won't create two records with the same key.
> 2. It should retrieve records correctly.
> Thank you,
> -M
>
>
Can you post the DDL to CREATE the table in question, some INSERT statements
to populate and then show us the results that you would like to get back? I
would have to make several assumptions here about your data and how it is
being used.
Rick Sawtell
MCT, MCSD, MCDBA|||What is typical when you link or import a table in MS Access is that it will
ask for a key for the data, if you answer this question and provide some
columns, Access will give you the behavior you describe.
Drop the linked table and remap it, except, this time, when it asks for a
key, cancel the dialog. This will force Access to assume all columns for a
key and should provide you with the duplicate information.
Sincerely,
Anthony Thomas
"Me" <Me@.discussions.microsoft.com> wrote in message
news:B89EA964-D9B9-4AE4-97D0-F1A9B0232C74@.microsoft.com...
> I have a table without any key defined for it.
> But I have an index comprising of 4 fields say -
> 1. Field1 Not Null
> 2. Field2 Can be Null
> 3. Field3 Can be Null
> 4. Field4 Can be Null
> I have data in Field1 and Field2. However Fields Field3 and
> Field4 are both Null.
> Field1 = 'A' and Field2 = 'BB01' contain the same data
> for two records.
> I found this problem -
> 1. In the database I see two records
> created for the above. The only difference being
> the description in two records is different.
> 2. When I goto retrieve records using Access database,
> it shows me 1st record twice.
> 'cause it shows the same description for both records.
> How can I ensure that -
> 1. It won't create two records with the same key.
> 2. It should retrieve records correctly.
> Thank you,
> -M
>
>|||If you don't specify any columns for the unique identifier
and there is no primary key, Access will assume there are no
columns that uniquely identify a record (rather than all
columns). This is why you end up with a read only recordset
when linking tables under such a scenario.
-Sue
On Sun, 14 Nov 2004 23:11:58 -0600, "AnthonyThomas"
<Anthony.Thomas@.CommerceBank.com> wrote:

>What is typical when you link or import a table in MS Access is that it wil
l
>ask for a key for the data, if you answer this question and provide some
>columns, Access will give you the behavior you describe.
>Drop the linked table and remap it, except, this time, when it asks for a
>key, cancel the dialog. This will force Access to assume all columns for a
>key and should provide you with the duplicate information.
>Sincerely,
>
>Anthony Thomas

Key and Index issues

I have a table without any key defined for it.
But I have an index comprising of 4 fields say -
1. Field1 Not Null
2. Field2 Can be Null
3. Field3 Can be Null
4. Field4 Can be Null
I have data in Field1 and Field2. However Fields Field3 and
Field4 are both Null.
Field1 = 'A' and Field2 = 'BB01' contain the same data
for two records.
I found this problem -
1. In the database I see two records
created for the above. The only difference being
the description in two records is different.
2. When I goto retrieve records using Access database,
it shows me 1st record twice.
'cause it shows the same description for both records.
How can I ensure that -
1. It won't create two records with the same key.
2. It should retrieve records correctly.
Thank you,
-M"Me" <Me@.discussions.microsoft.com> wrote in message
news:B89EA964-D9B9-4AE4-97D0-F1A9B0232C74@.microsoft.com...
>I have a table without any key defined for it.
> But I have an index comprising of 4 fields say -
> 1. Field1 Not Null
> 2. Field2 Can be Null
> 3. Field3 Can be Null
> 4. Field4 Can be Null
> I have data in Field1 and Field2. However Fields Field3 and
> Field4 are both Null.
> Field1 = 'A' and Field2 = 'BB01' contain the same data
> for two records.
> I found this problem -
> 1. In the database I see two records
> created for the above. The only difference being
> the description in two records is different.
> 2. When I goto retrieve records using Access database,
> it shows me 1st record twice.
> 'cause it shows the same description for both records.
> How can I ensure that -
> 1. It won't create two records with the same key.
> 2. It should retrieve records correctly.
> Thank you,
> -M
>
>
Can you post the DDL to CREATE the table in question, some INSERT statements
to populate and then show us the results that you would like to get back? I
would have to make several assumptions here about your data and how it is
being used.
Rick Sawtell
MCT, MCSD, MCDBA|||What is typical when you link or import a table in MS Access is that it will
ask for a key for the data, if you answer this question and provide some
columns, Access will give you the behavior you describe.
Drop the linked table and remap it, except, this time, when it asks for a
key, cancel the dialog. This will force Access to assume all columns for a
key and should provide you with the duplicate information.
Sincerely,
Anthony Thomas
"Me" <Me@.discussions.microsoft.com> wrote in message
news:B89EA964-D9B9-4AE4-97D0-F1A9B0232C74@.microsoft.com...
> I have a table without any key defined for it.
> But I have an index comprising of 4 fields say -
> 1. Field1 Not Null
> 2. Field2 Can be Null
> 3. Field3 Can be Null
> 4. Field4 Can be Null
> I have data in Field1 and Field2. However Fields Field3 and
> Field4 are both Null.
> Field1 = 'A' and Field2 = 'BB01' contain the same data
> for two records.
> I found this problem -
> 1. In the database I see two records
> created for the above. The only difference being
> the description in two records is different.
> 2. When I goto retrieve records using Access database,
> it shows me 1st record twice.
> 'cause it shows the same description for both records.
> How can I ensure that -
> 1. It won't create two records with the same key.
> 2. It should retrieve records correctly.
> Thank you,
> -M
>
>|||If you don't specify any columns for the unique identifier
and there is no primary key, Access will assume there are no
columns that uniquely identify a record (rather than all
columns). This is why you end up with a read only recordset
when linking tables under such a scenario.
-Sue
On Sun, 14 Nov 2004 23:11:58 -0600, "AnthonyThomas"
<Anthony.Thomas@.CommerceBank.com> wrote:
>What is typical when you link or import a table in MS Access is that it will
>ask for a key for the data, if you answer this question and provide some
>columns, Access will give you the behavior you describe.
>Drop the linked table and remap it, except, this time, when it asks for a
>key, cancel the dialog. This will force Access to assume all columns for a
>key and should provide you with the duplicate information.
>Sincerely,
>
>Anthony Thomas

Keep Details belonging to a Group together on a page

Hi,
this is my problem:
I have a Table defined in some report (Reporting Services); the Table has a
grouping, and each Group has one or more detail rows. So far so good.
When details belonging to some group do not fit on the current page, they
move to the next page - and this is my problem. I would like to have a
"KeepTogether" property on the the Group level, but unfortunately, this
doesn't seem to exist; I can only say "KeepTogether" on the Table level,
which is of no use for the Group.
Does anyone have an idea how some Group can be kept together with the detail
rows belonging to it on one page, such that in cases where at least one of
the details would move to the next page, the whole Group would move, instead?
Thanks for any hint, Axel Hecker.
--
Axel HeckerOn Feb 28, 7:55 am, AxelHecker <AxelHec...@.discussions.microsoft.com>
wrote:
> Hi,
> this is my problem:
> I have a Table defined in some report (Reporting Services); the Table has a
> grouping, and each Group has one or more detail rows. So far so good.
> When details belonging to some group do not fit on the current page, they
> move to the next page - and this is my problem. I would like to have a
> "KeepTogether" property on the the Group level, but unfortunately, this
> doesn't seem to exist; I can only say "KeepTogether" on the Table level,
> which is of no use for the Group.
> Does anyone have an idea how some Group can be kept together with the detail
> rows belonging to it on one page, such that in cases where at least one of
> the details would move to the next page, the whole Group would move, instead?
> Thanks for any hint, Axel Hecker.
> --
> Axel Hecker
You might be able to accomplish this by putting the table in a list.
Otherwise, it might be quite difficult to accomplish this.
Regards,
Enrique Martinez
Sr. SQL Server Developer|||Enrique, thanks very much for your comment.
But I cannot really follow you: when I put the table into a list, anything I
define for the list might have effects on the table level, but not on the
group level, because, as far as I know, the list would not "see" the groups
anyway. Or is my thinking wrong somehow?
--
Axel Hecker
"EMartinez" wrote:
> On Feb 28, 7:55 am, AxelHecker <AxelHec...@.discussions.microsoft.com>
> wrote:
> > Hi,
> >
> > this is my problem:
> >
> > I have a Table defined in some report (Reporting Services); the Table has a
> > grouping, and each Group has one or more detail rows. So far so good.
> >
> > When details belonging to some group do not fit on the current page, they
> > move to the next page - and this is my problem. I would like to have a
> > "KeepTogether" property on the the Group level, but unfortunately, this
> > doesn't seem to exist; I can only say "KeepTogether" on the Table level,
> > which is of no use for the Group.
> >
> > Does anyone have an idea how some Group can be kept together with the detail
> > rows belonging to it on one page, such that in cases where at least one of
> > the details would move to the next page, the whole Group would move, instead?
> >
> > Thanks for any hint, Axel Hecker.
> >
> > --
> > Axel Hecker
> You might be able to accomplish this by putting the table in a list.
> Otherwise, it might be quite difficult to accomplish this.
> Regards,
> Enrique Martinez
> Sr. SQL Server Developer
>|||On Mar 1, 2:52 am, AxelHecker <AxelHec...@.discussions.microsoft.com>
wrote:
> Enrique, thanks very much for your comment.
> But I cannot really follow you: when I put the table into a list, anything I
> define for the list might have effects on the table level, but not on the
> group level, because, as far as I know, the list would not "see" the groups
> anyway. Or is my thinking wrong somehow?
> --
> Axel Hecker
> "EMartinez" wrote:
> > On Feb 28, 7:55 am, AxelHecker <AxelHec...@.discussions.microsoft.com>
> > wrote:
> > > Hi,
> > > this is my problem:
> > > I have a Table defined in some report (Reporting Services); the Table has a
> > > grouping, and each Group has one or more detail rows. So far so good.
> > > When details belonging to some group do not fit on the current page, they
> > > move to the next page - and this is my problem. I would like to have a
> > > "KeepTogether" property on the the Group level, but unfortunately, this
> > > doesn't seem to exist; I can only say "KeepTogether" on the Table level,
> > > which is of no use for the Group.
> > > Does anyone have an idea how some Group can be kept together with the detail
> > > rows belonging to it on one page, such that in cases where at least one of
> > > the details would move to the next page, the whole Group would move, instead?
> > > Thanks for any hint, Axel Hecker.
> > > --
> > > Axel Hecker
> > You might be able to accomplish this by putting the table in a list.
> > Otherwise, it might be quite difficult to accomplish this.
> > Regards,
> > Enrique Martinez
> > Sr. SQL Server Developer
Theoretically that is correct; however, sometimes in RS the list helps
restrict the table groups (atleast in some cases). The only other
suggestion I would have is to select the page break after group
functionality, which may not give the exact results you are looking
for, but may be the only other option. Ofcourse, adding an extra
column to the report query and specifying grouping on that might be
another way to go to control your format; but is not a guarantee.
Regards,
Enrique Martinez
Sr. SQL Server Developer