Hi guys.I've never seen so much RTC crashes as yesterday.
The scenario is: I'm upgrading a 4.0 Sp1 Czech DB to Nav2009R2, and yesterday I'd to convert one report.
Layout not difficult at all, so I did it in one single shoot. Finished, I ran it and... Crash.
I tried to delete pieces of layout to find the problem, but nothing... if the layout was clean (no controls and code in it) report crashed.
I removed also a lot of code because I thought uhm... maybe it's too heavy for RTC?? but nothing...
In the end my colleague Belias had a great idea! To check the DataSetFieldName property and found the problem.
Obviously the captions had Czech and Slovak translation, and system create DataSetFieldName starting from these translation.
What we found was DataSetFieldNames with characters that in English aren't used (see attachment).
Changing them the report started to work.
What I'm wondering is if is a know issue and if anyone has already faced this problem.
Thx in advance
~Rik~
It works as expected... More or Less...
0
Comments
The call stack might reveal if a hot fix is on its way or not.
Software Design Engineer II
Dynamics NAV Office 365
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
this is from client eventviewer:
and this is from server
It works as expected... More or Less...
(and Měna = Currency)
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
1. to export and delete the language module (CSY for example)
2. let nav to create DataSetFieldNames for all the fields
3. import the language module
in this way I don't lose translations and datasetfieldname will be all in english.
Am I wrong?
It works as expected... More or Less...
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
It works as expected... More or Less...