Hi,
I cannot find any information about my issue so I though I would ask in this forum.
We have created views on top on some table to filter the column that can be used by the user to create their report. the underline tables have no FK constrains but I was task to recreate the constrains in the views so that the user would be able to make sense of the relations between the views.
Using the Relations was easy but the problem that I ran into is that the column used in the relation are of the same type i.e INT but some are nullable and some are not so although the relation are created without problem when I run a report I get this error.
I do understand why this is happening but is there anyway that I could reconciled the column type so that I do not get this error
changing the column type in the database isn't a solution
I could do the work in the view but I would be more interested to find out if you could think of another solution.
The key types of the relation does not correspond
'CardID-CardID' column types which were specified as keys for the 'ViewCardHolders.CardID' relation does not correspond! Such a relation cannot be created when report rendering!
Thanks,
Relations
Re: Relations
Hello,
Can you please send us a simple report with test data which reproduces the issue for analysis.
Also, please check the last build.
Thank you.
Can you please send us a simple report with test data which reproduces the issue for analysis.
Also, please check the last build.
Thank you.
Re: Relations
Hello,
Thanks for your reply.
I am using 2015.1.21.0
It is easy to reproduce the problem without data as it is not related to data but the structure of the database .
think of it this way.
view one as a column named CardId of type int not null
view two as a column named CardId of type int null
when I create a StiDataRelation, it create it without problem but as the report run it complain of the type mismatch.
I did find a solution where as I ISNULL(CardId , 0) as CardId in view two but I was wondering if I could to something similar in Stimulsoft.
Thanks
Thanks for your reply.
I am using 2015.1.21.0
It is easy to reproduce the problem without data as it is not related to data but the structure of the database .
think of it this way.
view one as a column named CardId of type int not null
view two as a column named CardId of type int null
when I create a StiDataRelation, it create it without problem but as the report run it complain of the type mismatch.
I did find a solution where as I ISNULL(CardId , 0) as CardId in view two but I was wondering if I could to something similar in Stimulsoft.
Thanks
Re: Relations
Hello,
We couldn't reproduce this bug.
Please clarify which version do you use?
Thank you.
We couldn't reproduce this bug.
Please clarify which version do you use?
Thank you.
- Attachments
-
- Capture.PNG (35.88 KiB) Viewed 2196 times
Re: Relations
Hello,
version is 2015.1.21.0
Base on your screenshot you have not created a relation between your 2 table and therefore you will not see the issue (I think).
Thanks.
version is 2015.1.21.0
Base on your screenshot you have not created a relation between your 2 table and therefore you will not see the issue (I think).
Thanks.
Re: Relations
Hello,
Can you please send us a simple report with test data which reproduces the issue for analysis.
Thank you.
Can you please send us a simple report with test data which reproduces the issue for analysis.
Thank you.