set Operation=-debug -service %ServiceUrl% -auth %AuthUrl% -workspace %WorkspaceId% -model %ModelId% -chunksize %Chunksize% -file "問題37.csv" -put "C:\anaplan-connect\ANY_files\問題37.csv" -import "問題37_import" -execute -output "問題37.csv_dump" 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% %Operation% @Echo%Command% cmd /c %Command% pause
Can you try passing the numeric file ID with -file instead of the name, and the numeric import ID with -import instead of the name? You should be able to retrieve these by listing them with -files and -imports.
HI Ben , Hope you are doing great! Looking for your Kind Advice .. Actually , I am working with Anaplan Connect to Import/Export files from server. Due to Security policy my client is not willing to Whitelist below both services.
api.anaplan.com & auth.anaplan.com . where as they are suggesting to use proxy and port in my Script . or Data Power path Anaplan Connect -> www.XXXX.ws.ABC.com/API & www.XXXX.ws.ABC.com/AUTH -> api.anaplan.com & auth.anaplan.com - No proxy config
If you specify a proxy URL using the "-via" option, Anaplan Connect will create a tunnelled connection through that proxy. Some proxies require authentication, and there is an additional option to pass credentials.
Great to hear that solution worked for you. You mark it as resolved.
In my case i was facing issue that script was on client server and without a proxy the Anaplan Connect API was not able to connect to Anaplan. We used the proxy specific to that system where script is stored and not the local machine.
If you are doing it on client server, they can provide you the same.
I know this thread is old, but I don't see my particular issue behind error 650 in community, so I thought I'd post my resolution here.
I have received the same 650 error when attempting to use an SSO ID with basic authentication. I switched to an exception user (non-SSO) and the error went away. From the AC 1.4.4 guide: "If you use Anaplan’s Basic authentication, the Anaplan Connect ... user must be an Exception User".