Txt2AL Error - Githubissues

microsoft / AL

Home of the Dynamics 365 Business Central AL Language extension for Visual Studio Code. Used to track issues regarding the latest version of the AL compiler and developer tools available in the Visual Studio Code Marketplace or as part of the AL Developer Preview builds for Dynamics 365 Business Central.

MIT License

733 stars 243 forks source link

Txt2AL Error #5488

Closed lloydb-insys closed 4 years ago

lloydb-insys commented 4 years ago

I'm upgrading from BC Spring 2019 (version 14) to Wave 2 (version 15). I'm working through the steps in the "Code Conversion from C/AL to AL" here:

https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/devenv-code-conversion

When i get to Task 5: Convert the C/AL TXT files to AL I run txt2al: "txt2al --source=C:\export2al\baseapplication --target=C:\export2al\baseapplication\al --injectDotNetAddIns --dotNetAddInsPackage=C:\export2al\dotnet\mydotnet.al --dotNetTypePrefix=BC"

It runs for a while and then I get this error:

Anybody know how to get past this?

atoader commented 4 years ago

Hi! What version of Txt2Al are you using?

lloydb-insys commented 4 years ago

14.0.3457.0

lloydb-insys commented 4 years ago

I figured out it's the multi-language captions in the objects. I had to use the Remove-NAVApplicationObjectLanguage cmdlet to get past this error.

atoader commented 4 years ago

Can you provide a sample to reproduce the issue?

atoader commented 4 years ago

This issue has been closed because it needs more information and has not had recent activity. Please open a new issue if you believe this has not been resolved and reference the current issue.

SteveKrisjanovsD365 commented 4 years ago

I just experienced this too. The culprit is the menusuites (BC13.2 onprem).

MEN1053.TXT, MEN1061.TXT, and MEN1080.TXT all have hex code x14 in our BC13 database.

Personally I think this issue should be reopened:

txt2al doesn't have a -verbose switch to identify which .TXT file it can't convert when it fails(I had to use notepad++ to hunt it down)
why did Export-NAVApplicationObject export a file with bad data?
why is txt2al.exe even processing menusuite objects?

UPDATE - I omitted the menusuites from my filter and it still errored out with the 0x14 invalid character. I did an exhaustive search for all the .TXT files however and no character code was found. its a mystery