Relationship version 2018.2.2

[Leandro Borges]

Hello.

When you perform a relationship from a Data Source with another Data Source through New Relation, the following error appears: Constraint 'Relation' does not belong to this DataTable. What do I do now?

Thank you.

[Edward]

Hi Leandro,

Please try the following in that case:

1) Rename 'Relation' -> 'Relation1' or some other name, to make it not-repeatable, unique
2) Please set Report.CacheAllData property to true.

Thank you,
Edward

[Leandro Borges]

Hello.

Did not work.
Even renaming the Relation and setting the Report.CacheAllData property to true, the error persists.
This error did not occur in previous versions. What has changed in this version for the error to occur?

Thank you.

[Lech Kulikowski]

Hello,

We couldn't reproduce the issue.
Please send us a sample report and step by step guide how to reproduce the issue.

Thank you.

[Leandro Borges]

Hello.

I could not simulate the error on a test basis.
It seems to me that the error occurs when one of the DataSources has variables and relation. Variables need to be executed before the relationship. I think variables are running after the relationship or, the DataSources are not being able to relate when the report is rendered.

Please try to create a test report that uses variables in the DataSources and these DataSources have a relationship with each other.

I think it will be possible to reproduce the error.

Thank you.

[Lech Kulikowski]

Hello,

We have tried several tests with variables and couldn't reproduce the issue.

Thank you.

[Leandro Borges]

Hello.

Attaching the exception of the error.
You can analyze the exception?

Thank you.

[Edward]

Hi Leandro,

I tried again to reproduce the problem, but again - no luck, sorry! Thank you for the provided exception, obviously, we could see the method that causing the issue in your case, but in order to fix this bug, we still need to reproduce the issue.
I suggest the following if you do not mind:
1) In your application, please edit the mrt file in the way, so you could remove as much of confidential and other not related to the issue report components, texts, datasources, etc. as possible.
When you are still able to reproduce the issue in the 'bare mrt template skeleton' mrt-report file, please:
2) send this mrt file only and any code that you think was relevant to create that exception to us for analysis to support[at]stimulsoft.com
3) We will take the mrt file and any code that you add to your email as a starting point of our reproducing the exception.
4) Once the bug is reproduced on our side, we will be able to help and to have it fixed eventually

Sorry about that tedious error reproducing process, but I believe that is the quickest possible way after all our and your attempts to nail the issue!

Thank you for your understanding,
Edward

[Leandro Borges]

Hello.

I did not understand some things you said but I'll try to send you an example.

Thank you.

[Leandro Borges]

Hello.

I was able to simulate the error.
The report and the MS SQL database are attached.
You will need to restore the database and then run the report by clicking Pre-View.
Then the error will appear.

Thank you.