In custom office, the table is called:  JT_WorkTicketTemplate it is not called "JT_Template".  (I don't know why)

StefanouM I would have thought the same. However, the UDF I am looking for is set to String 4. Everywhere else it exists is String 10.

This is the data source in Crystal for JT_Template

This is same UDF in the JT_WorkTicketTemplate data source.

In CR do a Database - Verify Database. 

The report's data structure (including field size) doesn't change unless you refresh it in this way.

Hey Kevin M

I tried that and the string value is still 4. That seems to be where my specific problem lies. The sub report is for our quality control tests. As it is, it seems to be pulling multiple versions of tests for different products. The way we have it set up, our QC codes are mostly 3-4 digits. But now we are in the 5 digit range and if there are multiple QC codes that are in numerical order (22207, 22208, 22209), when we print the work ticket, it pulls the QC tests for all three codes into one product. So, for instance, QC Code 22207 will have the QC Tests for 22207, 22208, and 22209.

It seems that, since the string value of the UDF (QC_ID), is set at 4, it is onle looking at 2220 and omitting the last number.

Make sure the report is pointing at the correct data source when doing the Verify Database (and not an old version).

Sage does give tables alias' in UDF /UDT maintenance (like how AR_Customer is called "AR Customer Master") it sometimes takes a bit of guess work to find the right table.

StefanouM is correct.  The real table name shows when you open it to work on UDF's.

Kevin M

I have verified I'm using the correct data source. When I use Database Expert to check the sources, I authenticate to the appropriate company and it all looks good.

Kevin M

This is interesting because when I re-add that table back in via Database Expert, the UDF string value is still 4. But when I view that UDF in Custom Office, it shows string 10. I have to be either missing something, or something isn't updating appropriately.

What about version?  Are you running v2021, but have an old MAS90 folder with v2020 data (which might have the UDF as a different size)?  If that were the case, the company / login would appear the same...

Kevin M

We do have an old Mas90 folder, but it was 4.5, and we didn't have Manufacturing before. We are currently using 2019 Advanced, and it;s the first time we've had this kind of integration, so it doesn't seem like anything old would have carried over.