v2020 Crystal Reports conversion from Company Maintenance... two issues

SOLVED

This is a new feature with v2020 (to use with upgrades), which I have just seen work for the first time.

There are two issues I spotted.

1. Where there is an error with the report conversion, it does not always name the report file where the error happened, making it difficult to see what file needs to be corrected.

2.  Reports stored in \MAS90\MAS_System\Reports\ were skipped entirely.

  • +1
    verified answer

    Kevin,

    This logic should be converting the reports under MAS_System.  I think it was doing that at one point but there is now an issue. I need to do some testing and see what is happening.

    As for the log, it contains the error message that comes back from Crystal Reports when the conversion fails. Typically, this includes the report name.  Not sure why it doesn't in your case. We can certainly add the report name to this output but it may be duplicated in the log.

    Please open a case with Customer Support and report these issues.  That will help us to track them and make sure that they are corrected.

    Thank you,

    Kent

  • 0 in reply to Kent Mackall

    Some of the errors did have the report name, but a few did not.

    I'll create a case when I find the time, with a link to this discussion for details (so I don't have to re-document everything).

    Edit:

    Done.  Case 8008296689.

  • 0 in reply to Kent Mackall

    Kent,

    Here is a better example for the log problem.  The Live file didn't convert, and without the file name it can be hard to know if the "No Error" is a problem in an active file (or an old copy).

  • 0 in reply to Kevin M

    Odd... using mascrcw to scan the folder manually it does not show in the list to convert, even with the wrong "Keywords".

    Within Sage, trying to use the form, there is a prompt to convert, with the same result:  No Error:

    Very strange.