Greetings All,
Please check out my new article on Model cleanup activities. If you have any questions, please let me know.
Link here
Thanks and Regards,
Kavin.
Thanks @kavinkumar.
Great article. I know you're also very familiar with the data integration side of Anaplan too. Any data integration cleanup suggestions?
I was recently working with a client that was using practically every method available to integrate with Anaplan - Excel add-in, API with and without a certificate - mostly Python, Anaplan Connect, and the Informatica connector. Seemed to me that it would be a good idea to develop a consistent data integration policy. Maybe something that con be done during a cleanup activity. What has been your experience?
HI @JaredDolich,
Definitely, I will work and come up with findings pretty soon 🙂 !!
Regards,
Very good content and handy @kavinkumar.
For actions I'd add one thing:
I personally consider any action with a default name to be **** and will periodically remove them. It forces my team to rename actions when they want to keep them. good success so far !
Haha, that's lil aggressive!! but people should take ownership.
What about imports built for functionalities in the past now decommissioned ? They will be missed from your cleanup purview since the import action will have proper names, but no longer in use.
Hi all, The Client ID and Client Secret are available, intended for uploading and downloading files. Could anyone advise how to use these credentials DIRECTLY to make API requests? Thank you!
I have A6 as the parent list and two sibling lists: A6.5 and A7. The A7 list includes an attribute that maps to A6.5. In the UX, the user will select A6.5 using a content selector, and the grid (dimensioned by A7) should display only the A7 items associated with that selected A6.5. Since the selector is a page context and…
A quick reminder of the Bulk Copy functionality. Bulk Copy allows you copy large volumes of data from one slice of a model to another in a single, optimised operation, instead of using formulas or imports. Use case: copy a version (RF1) into a prior year version (PY RF1) using a versions list to allow for year-on-year…
