• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 15 subscribers
  • Views 3645 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

migrate render to PDF as blank for a few form types

Jiayun Yang
over 6 years ago

Hi,

We are currently working on a Notes DB migration with render html to PDF. We are migrating them by form types. There are 3 form types in this database currently all migrated as blank, while the other form types seem just fine with the migration job we created. Any thoughts of how we should look into this? We are currently at version 6.9.6.1572

Thanks.

Parents
  • 0 over 6 years ago
    Hello,

    Thanks for posting in the Migrator for Notes to SharePoint (MNSP) community forum. I understand you are experiencing issues with 3 particular forms when performing a render to PDF within MNSP.

    One of the advantages to Notes databases are that they are infinitely customizable, however, there are times, such as during a migration that this can also be a disadvantage. Unfortunately, we are not able to presume what kind of custom elements have been created within the 3 forms that are experiencing issues.

    In order to troubleshoot this type of issue we would typically need sample data, such as a copy of the Notes database with at least a couple of records that use the problematic forms, so that we can investigate the issue in our lab environment. Additionally, we would need a copy of the MNSP job file you are using for the migration.

    In order to protect your data and privacy, we would suggest creating a Service Request in order to submit this data:

    support.quest.com/create-service-request

    If you are unable to create a Service Request using the link above, then you can call in using your local Quest Support telephone number:

    support.quest.com/.../phone-number-listing

    Also, would you be able to double-check the version of MNSP you are currently using, as 6.9.6.1572 is not a valid version of MNSP?
Reply
  • 0 over 6 years ago
    Hello,

    Thanks for posting in the Migrator for Notes to SharePoint (MNSP) community forum. I understand you are experiencing issues with 3 particular forms when performing a render to PDF within MNSP.

    One of the advantages to Notes databases are that they are infinitely customizable, however, there are times, such as during a migration that this can also be a disadvantage. Unfortunately, we are not able to presume what kind of custom elements have been created within the 3 forms that are experiencing issues.

    In order to troubleshoot this type of issue we would typically need sample data, such as a copy of the Notes database with at least a couple of records that use the problematic forms, so that we can investigate the issue in our lab environment. Additionally, we would need a copy of the MNSP job file you are using for the migration.

    In order to protect your data and privacy, we would suggest creating a Service Request in order to submit this data:

    support.quest.com/create-service-request

    If you are unable to create a Service Request using the link above, then you can call in using your local Quest Support telephone number:

    support.quest.com/.../phone-number-listing

    Also, would you be able to double-check the version of MNSP you are currently using, as 6.9.6.1572 is not a valid version of MNSP?
Children
No Data