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
737 stars 243 forks source link

Tab-delimited xml port not recognizing middle fields in 2018 #4140

Closed JMenezesDev closed 5 years ago

JMenezesDev commented 5 years ago

Describe the bug I have an xmlport designed to import some data to the Gen. Journal Line that I converted from 2017's CAL to 2018's AL. In 2017 it works as intended. While it compiles in 2018, when importing it no longer detects anything for the contents of fields other than the first and last ones. sample.txt xmlpayrollAL.txt xmlpayrollCAL.txt

Attached is a sample file for import as well as the al and cal code in separate files. It wouldn't let me upload .al so i renamed the file's extension.

To Reproduce Create action to execute or launch directly into xmlport. Import the sample file or any tab-delimited text file that matches the xmlport's format.

Expected behavior This xmlport is intended to import and create General Journal Lines.

Screenshots Not sure if necessary.

If you supply an appropriate dataset you should incorrectly receive an invalid amount message out of the OnAfterInsertRecord trigger indicating that amount is 0 regardless of input for the second column (eg ABC, 123.45, -100).

Versions: AL Langauge: 2.0.48254 NAV 2018: 11.0.22292

If you need more information let me know.

JohanStenberg100 commented 5 years ago

This GitHub repository is dedicated to handling issues and feedback for the latest Developer Preview releases of the AL development tools for Dynamics 365 Business Central.

If you can reproduce the problem on the latest Business Central Developer preview version we will be happy to look further into it. Otherwise please contact the regular support channel.

You can open Support Request to CSS through PartnerSource portal or contact your Service Account Manager (SAM) in the local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also step by step direct you how to open a support request or how to get credentials if this is the first time for you / your company. For more details please read:

I'll keep this issue open a while longer, please retry it on a later NAV version.

StanislawStempin commented 5 years ago

You cannot use AL Language 2.0 with NAV 2018. It only works with Business Central (starting with BC Spring 2018 release)

JMenezesDev commented 5 years ago

At Directions we were told to download the newest version of AL from the marketplace and not use the cd/dvd one. I have several extensions deployed to customers on 2018 using this version of AL. Are you saying XML ports are not working in this version with 2018 or that this version of AL doesn't work with 2018?