Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Crystal error develops...
Microsoft Dynamics SL (Archived)

Crystal error develops from SL 7 to SL 2018

(0) ShareShare
ReportReport
Posted on by Tom R. B. 55

After our jump from Dynamics SL 7 to Dynamics SL 2018, a few Crystal reports began displaying an error that said:  This field name is not known.  Details:  errorKind.  Error in File   XXXXXXXXXXXXXXXXXX

Error in formula  Record_Selection:  xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

This field name is not known.

Details:  errorKind

the text within the Xs differs per report, but the issue always includes the words above.  I do not know how to fix this, as several solutions can be found by searching, but none seem to solve my issue. 

Any thoughts?   Thanks

*This post is locked for comments

  • Suggested answer
    Tom R. B. Profile Picture
    Tom R. B. 55 on at
    RE: Crystal error develops from SL 7 to SL 2018

    All is OK now.  Once I was successful in adding the rptcompany table, I did not notice that there were two links made from that table, not one  (you do not need to add fields and the link is normally on cpnyid to the main table of the report.).  The second link was not in the standard version of the report, so I removed it, just left the cpnyid link, and now data is being pulled in.

  • Verified answer
    CFROTON Profile Picture
    CFROTON 4,710 on at
    RE: Crystal error develops from SL 7 to SL 2018

    Generally, you can get into the crystal report (in usr_rpts usually or in the module folder) and Update Database.   In order for it to work, you must chose a login that has admin access to the tables invoved.  if you still get this message after doing that, let me know.

    in report go to Database/Set Datasource Location

    Click the Connection listed under My connections (or create a new ODBC)

    in ODBC pop up, pick the App DB in Data Source Name

    Click next

    Log in (best if can use sa password or and adminstrator of SQL's password)

    then in the lower "Replace with" area, click the + next to the connectionto see tables

    Select each table one at  at time in this area and the Current Data source area above and select the update button to update the table information to the new connection.

    Click close when you are done.

  • Tom R. B. Profile Picture
    Tom R. B. 55 on at
    RE: Crystal error develops from SL 7 to SL 2018

    I find that with the RptCompany table added into PA.150 allows the report to process without error, but as I mentioned, no data is brought back from the print preview function.  If I open the report in Crystal and select F5, for refresh report data, the correct data is pulled back into the report from my Dynamics database.  I the report query is now working.  But what could have caused the ROI to begin failing?  it works for other reports.  Is there any test I can run to help determine the cause of this problem?

  • Tom R. B. Profile Picture
    Tom R. B. 55 on at
    RE: Crystal error develops from SL 7 to SL 2018

    Thanks All.  I decided to try Mark's solution.  That did the trick.  I was able to see and add the RptCompany table once I excluded the option to view stored procedures.  Now the preview of the report comes up without seeing the following:  This field name is not known.  Details:  errorKind.  Error in File   XXXXXXXXXXXXXXXXXX

    So my print preview function now works.   No data is populated into the report at all, even though the report appears to be functioning.  Wonder if this is an entirely new problem, and how to troubleshoot it.  

    Thanks

  • Suggested answer
    Mark E Profile Picture
    Mark E 6,405 on at
    RE: Crystal error develops from SL 7 to SL 2018

    A simple solution I use to only show SQL Tables and Views (and not Stored Procedures) in Crystal is to:

    1. Go to File/Options/Database tab

    2. Uncheck Tables, Views & Stored Procedures checkboxes in Data Explorer section

    3. Re-check the Tables & Views options

    4.  Close and re-open Crystal.

    This will remove the SP's from the Data Explorer view, and show you all the Tables and Views within the dbo tree.

  • AlexDupuis Profile Picture
    AlexDupuis 310 on at
    RE: Crystal error develops from SL 7 to SL 2018

    Hi Tom,

    You didn't added the table but a Stored Proc. Solomon have too much elements in database for Crystal Reports default values.

    Go in "regedit.exe" and search for "NTablesMax", the default value of CR is 5000, I set mine to 18000 and I have everything (for now ;) ).

    After that, you will be able to see "dbo" and "tables" in CR to select the right one. 

    Have a nice day. 

    Alex.

  • Tom R. B. Profile Picture
    Tom R. B. 55 on at
    RE: Crystal error develops from SL 7 to SL 2018

    OK.  I won't worry about adding the fields.  But, when I proceed to try and add the table, rptcompany, I just see the three options shown on my first screen shot.

    Capture2.PNG

    Then I select one of the 3 circled tables to move to the "selected table" window, and I always get a window pop up that looks like my second screen shot.  Capture2.PNG

    Can I get some instruction on exactly how to move the rptcompany table to the selected tables list?

    Thanks

  • CFROTON Profile Picture
    CFROTON 4,710 on at
    RE: Crystal error develops from SL 7 to SL 2018

    you do not need to add feilds and the link is normally on cpnyid to the main table of the report.

  • Tom R. B. Profile Picture
    Tom R. B. 55 on at
    RE: Crystal error develops from SL 7 to SL 2018

    I now see that the rptcompany table is in the standard version of PA.150.  And the linked field is cpnyID.  But I have not been able to add rptcompany to my modified version.  The database expert function continues to complain and not allow the addition.  Can you offer any tutorial on how to do this, other than completely rebuild my customizations in the new standard report?

  • Tom R. B. Profile Picture
    Tom R. B. 55 on at
    RE: Crystal error develops from SL 7 to SL 2018

    They are custom, so your comments are encouraging.  I can try that tomorrow.  But what do you mean by add them to the report?  Does that mean I need to link them in some way to the other tables, and do I need to add any fields from any rpt table to the report, per say?  

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,269 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,198 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans