web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

Upgrade to 2017, problems with importing reports in text files

(0) ShareShare
ReportReport
Posted on by

I'm facing a problem during upgrading application 2016 to 2017. All the reports can't imported, because there is an error.

---------------------------
Microsoft Dynamics NAV Development Environment
---------------------------
Could not upgrade RDL on Report 50000 Test.
Illegal characters in path.
---------------------------
OK   
---------------------------

I make a new report, with only one data item in NAV 2017, no columns, and only the standard RDL layout. I export it, and then i want to import it again. There is also the same error. When i use ProcessingOnly, there is no problem to import the text file.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    IshwarSharma Profile Picture
    729 on at

    Please try this, it might help. Remove the RDL Data from the text file you are importing into NAV. To do so, find 'RDLData' in the object's text file. Remove all the content which exists in between the curly parenthesis {} which start after the RDLData.

    Try importing the file. It has helped me once in resolving this error.

  • Community Member Profile Picture
    on at

    yes.. i know.. But i'm upgrading a database from 2015 to 2017, and there are maybee 50 reports.

  • Community Member Profile Picture
    on at

    yes.. i know.. But I'm upgrading a database from 2015 to 2017, and there are maybe 50 reports.

  • Community Member Profile Picture
    on at

    Might be useful, if your problem is something similar like this ; community.dynamics.com/.../167321

    It seems like problem with your RDLData, so take a single report and try to remove controls one by one then try to reimport the object txt file. In this way you can find where the actual error happens.

  • Community Member Profile Picture
    on at

    See my comment:

    I make a new report, with only one data item in NAV 2017, no columns, and only the standard RDL layout. I export it, and then i want to import it again. There is also the same error. When i use ProcessingOnly, there is no problem to import the text file.

     

    This is strange, the rdlc section is almost empty. But even when I exporting an existing standard report, and this one I want to import I get the same error. You have it alreadt try this in 2017 too?

  • Suggested answer
    Community Member Profile Picture
    on at

    Hi bule,

    I had same issue. What SQL server are you using? I was using a SQL server 2014 - NAV 2016. I had installed reportbuilder 2016 and got the same error as you did.

    I uninstalled the reportbuilder 2016 and installed a 2008R Report build and it worked. Here is the link www.microsoft.com/.../details.aspx

  • Kennie Nybo Pontoppidan Profile Picture
    on at

    Please read the following on SQL Server 2016 SSRS components (Report Builder and Report Viewer) and Dynamics NAV RDLC reports:

    blogs.msdn.microsoft.com/.../sql-server-2016-and-dynamics-nav

  • Verified answer
    Community Member Profile Picture
    on at

    Yes.. this works.. Thank you. !

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
HoangNam Profile Picture

HoangNam 7

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans