Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Writing BigText to file in Role Tailored Client
Nav_Noob
Member Posts: 25
Hello,
I have a code unit that writes some data to a file using a BigText variable. The code runs fine in the classic client but when I run the same code from the role tailored client I run into some problems when working with the BigText variable. Here are the errors I'm getting...
The line that is causing the error is:
"BigTextVariable".AddText('some text');
I get the following error:
Compilation of module '...' failed. This could be caused by differences between binaries in your installation or your database. Enusre that all installation components are consistent and up to date. Error details: The best overloaded method match for 'Microsoft.Dynamics.Nav.Runtime.NavBigText.ALAddText(Microsoft.Dynamics.Nav.Runtime.NavBigText, string)' has some invalid arguments: error CS1503: Argument '2': cannot convert from 'byte' to 'string'.
So I commented that line and tried to write the empty BigText variable to the file like this:
"My File".WRITE("BigTextVariable");
In this case, I get the following error:
ALStream.ALWrite, invalid stream mode: FileText
Any ideas on what might be going wrong? This code is working just fine in the classic client. Any ideas would be greatly appreciated.
Thanks,
Adam
I have a code unit that writes some data to a file using a BigText variable. The code runs fine in the classic client but when I run the same code from the role tailored client I run into some problems when working with the BigText variable. Here are the errors I'm getting...
The line that is causing the error is:
"BigTextVariable".AddText('some text');
I get the following error:
Compilation of module '...' failed. This could be caused by differences between binaries in your installation or your database. Enusre that all installation components are consistent and up to date. Error details: The best overloaded method match for 'Microsoft.Dynamics.Nav.Runtime.NavBigText.ALAddText(Microsoft.Dynamics.Nav.Runtime.NavBigText, string)' has some invalid arguments: error CS1503: Argument '2': cannot convert from 'byte' to 'string'.
So I commented that line and tried to write the empty BigText variable to the file like this:
"My File".WRITE("BigTextVariable");
In this case, I get the following error:
ALStream.ALWrite, invalid stream mode: FileText
Any ideas on what might be going wrong? This code is working just fine in the classic client. Any ideas would be greatly appreciated.
Thanks,
Adam
0
Answers
I have a feeling of dejavu when I saw this, but I cannot find the error.
I think you should try replacing this:
"BigTextVariable".AddText('some text');
with
strvar := 'some text';
"BigTextVariable".AddText(strvar);
and see whether that fixes your problem.
Reg. the write, I think you need to use
"BigTextVariable".WRITE(OutStream)
on an OutStream you have created based on the file - when writing a BigText to a file.
Group Program Manager, Client
Microsoft Dynamics NAV
http://blogs.msdn.com/freddyk
The information in this post is provided "AS IS" with no warranties, and confers no rights. This post does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion.
That also worked perfectly, thanks again!