Does anyone know a workaround to import from a subsidiary view?
@BahalR
You can make saved view out of subsidary and use it as your import source
I think, you can't import from subsidiary view directly. You can create a saved view with the subsidiary view and can import.
I need to import data from a module in which one line item has a subsidiary view, When I create the saved view including the other line items the values in the subsidiary view line item don't show up
You may need to just split your import into two separate actions.
Also, if your subsidiary view is that different from the main module such that it doesn't show up in the main view, it's an indication that perhaps that line item should be in another module entirely. See best practice Planual rule 2.01-06 Avoid Using Subsidiary Views for more info.
So, for this case it'll not show. you just create another module with that dimension what you given in that line item and with that you can create saved view and import.
Hello everyone, We are trying to use Anaplan Connect in order to push data from a dwh to Anaplan Data Hub. To do so, we need an authentication by token. We can't make it work, we receive the following error: ERROR 16020 |-- Anaplan API: Invalid key path Any suggestions? Thank you all in advance for the help! Michele
I am attempting to connect to an azure SQL database vis at the MSSQL connector in data orchestrator but am having issues and I believe it is due to hyphens in database name (which is a fairly standard naming convention I will note!) Example below (fake credentials) - has anyone else encountered similar and is there a way…
Has anyone found success using Anaplan XL with Polaris models in a shared drive with or without concurrent users? My team has experienced a variety of errors, login failures, etc. sometimes it works, sometimes it doesn't. We've been recommended to save and edit files locally, which helps but certainly with its limitations…
