Hello Support,

While running the report convertor tool the following error message is generated

Conversion Results
PSI Daily Invoices and CR notes.rpt There is no entry in the table mapping file for <OEW65 Sales Order Header Ext>
PSI Daily Invoices.rpt There is no entry in the table mapping file for <OEW65 Sales Order Header Ext>


How to deal with this error ?

Second question: How to work with 'Change Version ID' fields and where it is applicable ?

Hi Vlad

Are you familiar with the document ReportConverter.pdf in the \Softrak\System folder?

Steve

Hi Vlad,

in the Partner area of our website is a document to assist in using the Report Convertor. This is the same document that Steve referred to.

On pages 3 and 4, there is a utility called the Report/Dictionary Usage Survey, which is the ReportDictUsage.exe program in the \Softrak\System\ReportConvertor directory. It's purpose is to let you know which reports using QRW tables are able to be converted, because not every QRW table from all time have been included in the table mapping file.

I created an old-style Crystal 8.5 report that had the Sales Order Extension file in it, and I was able to replicate the message you also received. Looking at the table map file, I can see the Sales Order Extension line for the OEW65 table, so I am not sure why this error is occurring. I will need to ask R&D.
--
As for your second question, the Change Version ID fields only come into play if you are trying to convert a report based on one dictionary version that uses an ODBC connection to another newer ODBC connection. We have not yet shipped any Adagio upgrades after 9.2A, so this portion does not yet come into play. But say when an upgrade such as Adagio Payables 9.2B ships and requires a database conversion, then you would use this Change Version ID to convert a report that already uses an ODBC connection for 9.2A, to the newer 9.2B.

Hi Vlad,

We did some investigation, and the problem is due to the old table alias 'OEW65 Sales Order Header Ext.' exceeding a maximum length of 28 characters - this has 29. Thus the last character (a period) is missing and causing a mis-match to the table mapping file, and this is the reason that the table is being reported as not there.

It's probably easier to have us convert the 2 reports for you, rather than walk you through doing the conversion manually. If you can upload or email the RPT files to the attention of tech support, I can forward them to R&D for the purpose of doing the manual conversion for you, and sent back the converted RPTs.

Thank you for bringing this to our attention.

This is great. I will prepare the list of reports to ship to you. Please let me know which email address to sent it to.

Thank you