Hi Experts,
We use Anaplan connect 1.4.4 to import data from SQL. we noticed that after import execution the file delimiter default itself to "Tab" even though it is set to "Comma" delimiter. this is weird.
Interesting part is even if the action changes from comma to tab further load using the same API call works when it was imported using Anaplan client 1.4.4 but this is not working when this action is called from AWS API (v2)
@Echo off
set ActionName="1.1 Current date upload from SQL"
set ActionFile="Current_Date.csv"
set JDBCFile=JDBC_Current_Date.properties
set ErrorFile=Current_Date_Error.txt
set Operation=-auth %AuthUrl% -file %ActionFile% -jdbcproperties "%JDBCpath%\%JDBCFile%" -import %ActionName% -execute -output "%Errorpath%\%ErrorFile%"
rem *** End of settings - Do not edit below this line ***
setlocal enableextensions enabledelayedexpansion || exit /b 1
cd %~dp0
if not %AnaplanUser% == "" set Credentials=-user %AnaplanUser%
set Command=.\AnaplanClient.bat %Credentials% -workspace %DatahubWSID% -model %DatahubModelID% %Operation%
cmd /c %Command%
Action is configured as "Comma" delimiter

After executing the API import, the delimiter automatically changes to "TAB" from "COMMA"

Please suggest why delimiter changes after Anaplan connect 1.4.4 API call
Regards,
Siva