Is it possbile if we can get list of all models in the workspace inclluding the archived model and export this information in excel or csv just like the option is available for modules?
This will be helpful for the documentation.
Hi @swapnil_J , There are possible ways to get the model details located under the particular workspace. 1. Using Python script you can get the model details.
2. Using Ananplan connect batch script.
Please find the script below:
set AnaplanUser="username:password"
set ServiceUrl="https://api.anaplan.com"
set AuthUrl="https://us1a.app.anaplan.com"
Set WorkspaceId=""
set Operation=-debug -service %ServiceUrl% -auth %AuthUrl% -Workspace %Workspaceid% -models
rem *** End of settings - Do not edit below this line ***
setlocal enableextensions enabledelayedexpansion || exit /b 1
set Credentials=-user %AnaplanUser%
set Command=AnaplanClient.bat %Credentials% %Operation% @echo %Command%
cmd /c %Command%
pause
Hope this helps :).
Regards, Venkatesh
Thank you for the response! it worked.
It will be good if WSA get simple alternative without involving integration team (or no coding effort)
Hi @swapnil_J , I agree with you. I think as of now these are the only option available even you can get the details using python also. Hope this helps :). Regards, Venkatesh
In multiple Anaplan implementations across FP&A, S&OP, and operational planning use cases, a recurring design challenge is the overuse of hierarchical lists with Top Levels, especially on large transactional or operational lists. In many projects, hierarchies are introduced early with the intention of providing “future…
Phenomenon: When the page is opened after launching the browser, FY25 is selected in the selector, but the year displayed in the grid is FY24. Current Workaround and Impact: The grid will display FY25 if the user first changes the selector in the page header to FY24, and then changes it back to FY25. Currently, end-users…
In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds: The "w/e" prefix is quite bothersome, especially when it appears on our graph axis labels. My business and executive users often…
