Best Of
Re: Register for our October 29 platform release webinar!
@JEAlfaro1704 Here's the link to the recording:
You can also watch for a Community post on Monday that contains the link and some Q&A that wasn't answered live!
AbbySB
Re: Combo Grid with nested Line Items
@RyanQ @jan_sypkens This is the enhancement I was chatting to you about for combo grids.
Jonnyf
Re: Accessible by design: Our new accommodations for certification exams
We are not allowed to open any pages during the exam. Kryterion support says:
"I understand your concern regarding the recent changes with Anaplan and the ability to have multiple pages open during your exam. However, I must inform you that our system currently only allows one screen/tab to be used for the exam at this time."
I just passed this exam few minutes ago, but there was no option to open any page
Diana
Re: Is there a way to auto-generate ID for user who entered line item?
To my knowledge, there is not currently a means to capture the user name via data write as part of a form.
The work around we have used in past is a user dimensioned input module which we then use as part of an action to create the list item (or other data write activity), this allows for the user to be captured as part of a module to module import action.
Re: Combined Grids is now live!
First off, a huge thank you to the Anaplan team for the hard work to make this release happen. This feature is a game-changer for usability in Anaplan. Looking forward to more UX improvements like this one!
Two things I've noticed so far while working with combined grids: (1) the ability to specify column widths by pixel seems to be disabled when using combined grids, and (2) the grouping for hierarchical summaries seems to be stuck on group before and doesn't seem to change even when updating the settings to group after or group at end.
The inability to override column widths using specified pixel widths makes building visually consistent pages challenging, while the inability to change the order of hierarchical summaries results in manual changes to column ordering that add unnecessary maintenance overhead. Would love to know if these are already flagged as known issues and if they will be resolved in the near future.
Thanks again for the hard work on this feature. I look forward to hearing back about the two observations noted above.
etbell
Data integration best practices — Event recording available!
Last month, we hosted a Community Challenge inviting members to share their best practices on data integrations. We provided both beginner and advanced prompts to encourage members to discuss how they move data in and out of Anaplan, share tips for smooth integrations, and inspire others in the Community.
Yesterday, we hosted an event to highlight the responses we received from the Community Challenge. Jon Ferneau (@JonFerneau), Data Integration Principal, shared his expert insights, recognized participants for their contributions, and presented key takeaways for practitioners along with call-to-action items for our Community to consider.
During the event, Jon gave a shout out to our Community Challenge participants, including @andrewtye @matthewreed @SunnyNafraz @Prajjwal88!
Watch the recording
Timestamps:
- Welcome — 0:00
- Guest host introductions and overview — 1:40
- Community Challenge recap presentation — 3:47
- Q&A — 23:35
- Closing — 42:54
A PDF of the presentation is available here:
Resources for Data Integration Best Practices
- OEG Best Practice: Data Integration Decision App
- OEG Best Practice: Data Hubs: Purpose and Peak Performance
- Getting Started with Anaplan APIs: What you need to know
- [Start Here] Anaplan APIs in a Nutshell
- Understanding Errors and Rejected Lines When Importing Data Via APIs
Questions? Leave a comment!
Re: Combined Grids is now live!
Such a game changer ! My only concern was the ability to reorder grid section but I can see it already in the roadmap. Such a good job !
Re: Combined Grids is now live!
Goodbye endless subsidiary views and repeated attribute line items! I’m sure there are plenty of great use cases for this feature. Thanks, Anaplan!
MoraruD
Re: How many bytes is a list item?
In a Classic model, a list formatted line item (in a module) is 4 bytes, as part of a list it is 500 bytes which includes the member, the code, and the parent. Any more properties adds to it.
In Polaris, a list formatted line item that has data (not blank) is roughly 24 bytes and the member in a list is roughly 600 bytes.
