What is the best practice to keep copies of the entire apps page in a periodic manner in case of reference required in the later period.
Duplicate App and store it with date mentioned.
One point for consideration is the retention period, as the underlying/linked models change the relevance of an duplicated UX pages may be impacted. Cards may no longer work as originally designed.
This will vary by use case but from my experience the utility of these duplications have a limited shelf life.
@BlessyDube - While creating your duplicate app, you can provide instructions in the app with the date you created and also the app name can also include the date created.
Hi @BlessyDube , One more point worth noting is to remove the access to the older/copied app pages for the user so they don't end up in the wrong/outdated pages.
Hi everyone 👋 If you build or maintain Anaplan models, you've probably hit the same walls I kept hitting. Some basic questions about a model's structure have no single screen to answer them. You end up clicking through modules and pages one by one, or writing API scripts just to get a list. These were the gaps that…
Hi Everyone, We have a requirement in Anaplan Consolidation & Reporting (Fluence) where the Entity Structure needs to change effective January 2026. The key requirement is that the existing entity structure should continue to be applicable for all reporting and consolidation periods through December 2025, while the new…
We've been building a tool called aplan4sheets and we'd genuinely like input from this community — both on what we've built so far and on what we should prioritize next. The problem we set out to solve: Anaplan's Excel add-in is Windows-centric, and there's no real native way to pivot Anaplan data in Google Sheets. We…
