TextIO Class Initialization Issue

(1) Share

Report

Posted on by D365_FO_Technical_Te

126

Hello everyone,

I am using TextIO Class in my code, but when i am debugging it - on initializing the class i am getting Null Value. can anyone please help me how can i initialize it. I am using below code. I have used same piece of code on AX , there it's working fine. But on D365 I am facing issue.

FilePath    _filePath;   //_filePath is my Global Variable

Public void ABC()
{
    TextIo    textIo;
    FileName  fileName;
    str       getFileName_Path;
    #File
    ;

    fileName = strfmt("barcode_%1.prn", curUserId());
    _filePath = InventParameter::find().FilePath;
    getFileName_Path =   _filePath +  fileName;
    
    //I have used both below code, but still i am receiving null value in debugger.
    //textIo = new TextIO(getFileName_Path, #IO_Write, 65001)
      textIo = new TextIO(getFileName_Path, #IO_Write)
}

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Martin Dráb 240,540 Most Valuable Professional on at

Like (2)

Report
Copy link

Link copied!

First of all, are you sure you need to create a file on the given AOS at all? Don't you want to use TextStreamIo, for example, instead?

If you have to, make sure that the location exists and it's writable. Letting users to configure the path doesn't make a good sense to me - I recommend simply using the Temp folder (e.g. WinApiServer::getTempPath()). The fact that you want to configure it suggests that you want to use as a data storage, which would be a bug in the design. There is more than one AOS and they can be added or deleted as needed.

Was this reply helpful? Yes No
Anton Venter 21,175 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Why not change your code to use the .NET MemoryStream class? Then you don't have to write anything to a physical file.

Was this reply helpful? Yes No
D365_FO_Technical_Te 126 on at

Like (0)

Report
Copy link

Link copied!

Thanks Anton & Martin for your response.

You were right Martin, it was a permission issue. I changed the path which was writable, and its started working.

Was this reply helpful? Yes No