Skip to main content

NAV 2013 - Development Environment Crash During Creation of Report Request Page.

Hi all,

I found a issue while upgrading reports to NAV 2013 and Plan to share same with you all.

During Upgrading Classic Reports with Request Form to NAV 2013 (say from Version 5), while trying to create request page for Report - NAV 2013 Development Environment Crashes.



Resolution (Detailed Explanation Below)-

1. "Export the Upgraded Report as Text File from NAV 2013 and search for "REQUESTPAGE".

2. Delete Lines Shown Below -

  REQUESTPAGE
  {
    PROPERTIES
    {
    }
    CONTROLS
    {
    }
  }

OR 

  REQUESTPAGE
  {
  }

3. Save the Text File, Import it back to NAV 2013 and start development of Request Page.

Detailed Steps (Issue Replication)-

*For Demo i am saving Standard Report 7319 Warehouse Bin List as Report 50000. Below images are for the same report.

1. If Report you want to upgrade have Request Form.



2. As per upgrade Plan we export the customized Object(in our Case Report 50000) from Version 5 and import it in NAV 2013.

3. When i try to desing Report, it says Report Must be Upgraded.



4. So i Select Upgrade Reports From Tools Menu.



5. After This report have been upgraded and a suggested layout have also been created.



6. Now i need the request Page to be created.

7. I Navigate to Request Option Page From View -> Request Page.

8. I Developed Request Page as per requirment.



9. Now as i tried to save the report, Navision client carshed.



Detailed Steps (ISSUE RESOLUTION)-

1. Export Report 50001 from NAV 2013 as Text File.

2. Open Text File and Search for RequestPage.

3. Delete the Request Page From Text File (selected Part).



4. Save the Text File.

5. Import Text File in NAV 2013.

6. Compile Report, Design Request Page and Save.

You will be able to save the report.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.