Excel add in versus running map within smartconnect
I originally though that it was an issue with trying to define the line sequence ID for the lines of the JE, yet I am still receiving the error after omitting that mapping. Is this a known issue that will resolve with an upgrade to the newest version?
When it comes to decimals places, it depends on how they are defined in the excel file. In this case there will be a difference because of how the ODBC driver reads the data in the excel sheet and how the add-in will be pulling the data.
There are two ways to resolve it.
First, make sure the Excel column truly has the right number of decimal place values in the data itself. Even though you change the display in Excel to something like two decimals there may be additional data in the column that is being pulled.
Or create a calculated column that rounds or truncates the column data within the map itself. Something like return Math.Round(_MyColumn,2) will round the column to two decimals. Then put that calculated column into the destination mapping.
Shouldn't I see a difference in the XML file if they were being read differently? The column that I thought was in question was the line sequence number. But when I remove that column completely there is still an issue. The error is referencing the BatchID, Jrnentry Number, Date, and Type. The type is currently set in my map to standard. I have been able to push GL docs in without error so I know the add in is working and configured properly.
If you would like to submit an answer or comment, please sign in to the eOne portal.