However, when I added the SO_Invoice.Wrk table, and added the field ExtendedDescriptionText to the report, it resulted in an error when trying to print. What am I doing wrong?
However, when I added the SO_Invoice.Wrk table, and added the field ExtendedDescriptionText to the report, it resulted in an error when trying to print. What am I doing wrong?
Oops, I spoke too quickly. I do not have the extended description appearing in my report. I do have only one page, though. I thought perhaps I needed to also link CI_Item, but that generated multiple pages again.
If you add your UDF to the report do you have data in it? I am wondering if that actually contains the data we think it should.
If it were me here is what I would try next...
I would have the BM_GrossReqrmntWrk, CI_Item, and CI_ExtendedDescription tables. Clear your existing links and relink them like this:
I am assuming you want the extended description for your component item codes... It is important to note that for the link between CI_Item.ExtendedDescriptionKey > CI_ExtendedDescription.ExtendedDescriptionKey I have used a Left Outer Join, if you do not use a left outer join you will only see records for items that have extended descriptions. I am assuming not every item in your system does.
When placing the extended description on the report it is important to have it in a section where it would be directly linked to an item. For example in the details section, or in the ComponentItemAndRevision group.
Hope this helps.
- Jonathan K.
I'm still looking for an answer if anyone has other insights. I may have to concede defeat and talk to the reseller, as my employer says that the report is useless without the extended descriptions on it. My stubbornness is about to be trumped by my inability to figure this out.
*Community Hub is the new name for Sage City