In my organization, we have two prod models and one dev for both of them. Can we create an action in this case? The user asks to reflect the data from one UI page to another, but they are from two different models and a common dev. Is this doable?
@keerthikancharla
Yes, this can be done. In your Dev model, create an action importing the data from Prod 1 to the target module (in your Dev model). So when you are defining the import action, truly chose the Prod Model. Remember, all actions should be created from views, not the module.
Make sure the data loads correctly. I am a bit of a nut, but it is very helpful to clean up the Action Name and Import Source name in order to keep things straight.
Create a Revision in Dev and sync it to Prod 1 and Prod 2.
Go into Prod 1 and make sure data is in the desired module
Log into Prod 2 and run the action
Before action is run
After Action is run
Hope this helps,
Rob
Hi @rob_marshall Thanks for the input, but here is the catch Prod A is in one workspace and Prod B is in one workspace in this case how can we map the data flow from model to other?
Workspaces don't matter as when you set up the action from Dev to Prod 1, that workspace is defined for the action.
We are looking for Anaplan end-users to provide feedback on their experiences with the Excel add-in. Interested individuals will respond to this 5-minute survey to help us understand personal needs and behavior when using the add-in. The feedback provided by survey takers is essential to the roadmap of Anaplan's products.…
Estimated Level of Effort:4-8 Hours of Model Building Level of Difficulty: Beginner Recommended Training: L2 Model Builder Training Persona: Casual Model Builder Potential ROI: Decreased planning time Increased accuracy of targets/spreads You Might Also Like: * Historical Snapshotting Top-Down Allocations Whether it's…
This item has been identified as an outstanding known issue. A workaround is provided until the issue is officially fixed. Issue For versions 1.6, 1.7 and 1.8 of the PowerPoint Add-in elevated privileges are required to install the add-in through command line and for the "all users" option. Workaround * Installing through…