PackSlip Report (Duplicate Details Group)

Kinetic ERP
, , ,
1

Happy new year all,

I’ve been working within the PackSlip report and found a recent annoying issue. The Details Group within the Tablix of the report gets duplicated. I’ve done some testing and troubleshooting and it appears to be the Part table that is causing this. Without the Part relationship within the report, this issue does not occur.

image
image737×172 15.6 KB

This should only be appearing like the below with one,

image
image736×96 10.1 KB

This is the relationship I have setup within the RDD,

image
image1177×345 10.4 KB

I’m out of ideas on where to check and what could possibly be causing this issue?

Part is required as we pull the UD fields that we created into our report using this table.

Any help would be greatly appreciated!

1 Like
2

What information are you trying to get from the Part table?

Do you need to add a relationship at all? PartNum is already a “linked table” on ShipDtl (already turned on in the base PackSlip RDD). You should just be able to add query fields, like T2.PartNum_whatever.

May have to review the description fields on the PartNum linked table… but you shouldn’t need to add a relationship to the query.

3 Likes
3

Hi David,

I’m trying to pull the following UD fields into the report. They are stored within Part_UD.

image
image856×617 24.5 KB

I’ve not had to touch Linked Tables too much so i’m not too familiar with this. I’ve gone into ShipDtl and can see PartNum as a Linked Table.

image
image1615×340 20.4 KB

Through checking the Description Fields of PartNum I can find my UD fields within this.

image
image1625×338 23.5 KB

So would I just need to make the fields within the dataset T2.UD_ExportRating_C & T2.UD_SecGrading_c or is there more to the process to be able to pull these fields in?

Thank you for the support!

1 Like
4

Yes, all you should need do is unexclude any linked table columns you wish to add to the report, and update the dataset correctly with the added fields.

2 Likes
5

@CSmith @dcamlin

Thank you both for your support! I got it to work and no more duplication within the reports. Also makes a lot of sense now and really useful to know that now for future reports.

Thanks again!

2 Likes
6

Hi David,

Sorry going back to this we found a issue that I am struggling to resolve.

So within ShipDtl, I have selected PartNum and also selected CommodityCode (As one of the examples).

image
image1612×707 44.3 KB

I then used the following structure within the dataset

T2.PartNum_UD_ExportRating_c,
T2.PartNum_UD_SecGrading_c,
T2.PartNum_CommodityCode
          FROM ShipHead_" + Parameters!TableGuid.Value + " T1
          LEFT OUTER JOIN ShipDtl_" + Parameters!TableGuid.Value + " T2
          ON T1.Company = T2.Company AND T1.PackNum = T2.PackNum

However, the issue is that the data within Commodity Code is not pulled into the report this way. If I was to put Part back into the dataset, this would pull the data although, of course the data would then be duplicated which was the original issue.

I have tried using different PartNum linked tables within other datasources of the RDD but they all have this issue where the fields show up under the linked table description, but they don’t pull the data.

I then decided to try something like the below to see if that would work but yet again nothing. Linked tables has been really helpful in working on other reports but I just can’t figure out this one and it’s really bugging me. :confused:

T2.PartNum_UD_ExportRating_c,
T2.PartNum_UD_SecGrading_c,
T2.PartNum_CommodityCode
          FROM ShipHead_" + Parameters!TableGuid.Value + " T1
          LEFT OUTER JOIN ShipDtl_" + Parameters!TableGuid.Value + " T2
          ON T1.Company = T2.Company AND T1.PackNum = T2.PackNum
          LEFT OUTER JOIN Part_" + Parameters!TableGuid.Value + " T3
          ON T2.Company = T3.Company AND T2.PartNum = T3.PartNum"

As always, appretiate any support on this!

7

Is CommodityCode the only one that isn’t coming over?