Author Topic: model advisor determinants issue  (Read 202 times)

Offline sdf

  • Statesman
  • ******
  • Join Date: Feb 2014
  • Posts: 322
  • Forum Citizenship: +3/-0
model advisor determinants issue
« on: 28 Dec 2017 04:37:16 am »
Hi,

This is generic under Model Advisor in FM. I would like to understand what this means and what are the effects and possible resolution.


The relationship 'Table A <--> Table B' does not reference all the keys of any uniquely identified determinant in the query subject 'Table A'. The relationship has a 0:1 or 1:1 cardinality, indicating that its keys should be an exact match to the keys of an uniquely identified determinant. Please review the cardinality of the relationship and the determinant information to determine if adjustments are required.

Please help!

Offline MFGF

  • Never knowingly correct
  • Super Moderator
  • Statesman
  • ******
  • Join Date: Jul 2005
  • Posts: 10,208
  • Forum Citizenship: +620/-10
  • Cognos Software Muppet
Re: model advisor determinants issue
« Reply #1 on: 28 Dec 2017 06:22:20 am »
Hi,

This is generic under Model Advisor in FM. I would like to understand what this means and what are the effects and possible resolution.


The relationship 'Table A <--> Table B' does not reference all the keys of any uniquely identified determinant in the query subject 'Table A'. The relationship has a 0:1 or 1:1 cardinality, indicating that its keys should be an exact match to the keys of an uniquely identified determinant. Please review the cardinality of the relationship and the determinant information to determine if adjustments are required.

Please help!

Hi,

What it's warning you about is that you have a unique determinant defined in your Table A query subject, based on a combination of query items as the key of the determinant. This should indicate that the combination of these values is unique within the underlying table. You also have a relationship between this query subject and a query subject for Table B. The cardinality of this relationship indicates that no more than one item from Table A links to Table B, so you'd expect that the items used in the relationship would combine to make a unique value in Table A, (ie the same combination of items in your unique determinant key). However, the warning is telling you that this is not the case, so you've probably either got a problem with the way your relationship is defined, or you've got a problem with the way your unique determinant is defined.

Cheers!

MF.
Meep!

Offline sdf

  • Statesman
  • ******
  • Join Date: Feb 2014
  • Posts: 322
  • Forum Citizenship: +3/-0
Re: model advisor determinants issue
« Reply #2 on: 01 Jan 2018 06:33:14 pm »
I have not setup any determinants, but as I checked the tables there exists determinants. I am not particularly familiar with determinants. But as per your comment, it seems I have a problem with the cardinalities as well. So correct me if my understanding is wrong. Based on the current determinants setup of my tables, Framework is expecting a 1..1 relationship between my tables.

I am still cross checking my data with the database source to validate my cardinalities.


Thanks for your reply!

cheers!
 

 


       
Twittear