Announcements
Issue resolved, thank you!
I analyzed the flow of the report to understand how the data was being printed. Actually, the header line was being inserted into the second table, and the lines records were being inserted into the LineHistory table.
From there, the data was being passed to a TempTable and then printed on the report. I checked to see if there was anything unique in the line tables, and I found the SequenceNumber field to be unique.
This field was present in the LineHistory table, but it was not being shown in the report’s TempTable.
So,I passed the SequenceNumber from LineHistory to my method, where I was already passing the PurchId and ItemId — I added SequenceNumber as well.
As a result, I got the exact description against the ItemId.
ItemID
and Description
or another unique field.This issue is likely happening because the report is grouping data based on the Item ID, which causes it to show the same description for all occurrences of that Item ID. Even though the Purchase Requisition Line table has different descriptions for the same Item ID, the report might be pulling only the first occurrence due to grouping or join conditions.
Here are a few things you can check to fix this:
Review Grouping in the Report – In the report designer (SSRS), check if the report groups data by Item ID. If so, try modifying it to include the unique line identifier (like Line Num) to ensure each entry is displayed separately.
Check the Dataset Query – Look at the SQL query or data source feeding the report. Ensure it retrieves all distinct descriptions instead of summarizing or merging them.
Verify Joins in the Report Dataset – If the report is pulling data from multiple tables, check if the joins (inner or outer) are affecting how descriptions are displayed.
Try these steps and see if they resolve the issue. Let me know if you need further help!
André Arnaud de Cal...
294,095
Super User 2025 Season 1
Martin Dráb
232,866
Most Valuable Professional
nmaenpaa
101,158
Moderator