topic Re: relationship in Desktop

relationship

ChenChristyYu — Thu, 01 Mar 2018 00:11:38 GMT

I joined together tblCustBatch, tblCustJob, and BRPrint Batch Detail and use country(2) as a slicer, but it keeps messing up the grouping. By which I mean, it does not accurately group the data by country. I cannot figure out the reason? Is it something wrong in the relationship? where should I start to examine?

Re: relationship

Anonymous — Thu, 01 Mar 2018 01:06:03 GMT

The first thing i've noticed is that you have two versions of your Country table? I would expect you should only have 1 and then link it to each place you need it in your table structure.

Re: relationship

ChenChristyYu — Thu, 01 Mar 2018 16:26:09 GMT

Hi Ross,

BRPrint Sum and Latest Report Sum are linked through IDEN on each side. But BRPrint Sum has additional records that do not exist in Latest Report Sum table, if I use Country table to group rows in BRPrint Sum table, it will filter out the additional records in BRPrint Sum. However, I would like to include all records in BRPrint table. that is why I added Country(2), so it does not need to go through Latest Report Sum table.

Re: relationship

Anonymous — Thu, 01 Mar 2018 23:12:26 GMT

Does your report have additional page or report filters that might be applied to other areas of your table mapping that could be adversly affecting your output?

Taking the structure of your tables in isolation for the tables mentioned in your OP, nothing immediately stands out with those in particular. Its likely the problem is related to something else that is related but unexpectidly affecting the results.

Re: relationship

ChenChristyYu — Thu, 01 Mar 2018 23:20:43 GMT

Yes, I have multiple pages in this report. But a slicer or filter should only affect the visualization on its current page I assume?

Re: relationship

Anonymous — Thu, 01 Mar 2018 23:27:45 GMT

In your visualisation pane you have an area called "Page Level Filters" and "Report Level Filters". That is where you might need to check first. You will need to step through the logic of any filters contained there to see if they might be hiding information long before your slicer has an effect. A filter that affects 1 table, might in turn hide information from other tables its linked to.

Re: relationship

ChenChristyYu — Fri, 02 Mar 2018 16:07:16 GMT

Thanks Ross!!!!!

I checked query edit, and I am wondering if it has something to do with this. "Limit of 1000 values reached" Do you have any idea how to fix that?

Re: relationship

Anonymous — Sun, 04 Mar 2018 23:16:06 GMT

The query editor, for performance reasons, only takes in a small sample of your dataset. Since you have access to the code itself, via "Advanced Editor", you should be able to tweak written code yourself.

For example if you wished to filter out a particular string, you could use the UI to filter out the wrong string temporarily. This would create the necessary code for you to hand change.