Getting error while importing data Attaching screenshots for reference. need help
@Kunal0489
I believe the 'WWYY' format expects only a numeric input. So, your "Week 11 FY19" entry would be "1119". Below is a Best Practice page on handling time imports.
Untangling Anaplan Time Mapping in Imports
Thanksi figured out ...
What did you do to solve it? I have tried Custom and Match Names - none worked, obviously I am missing something.
@singhprashant8
Custom it as - ???? WW ??YY
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…
We’ve recently started using Anaplan to model and manage our supply chain and production planning for a niche ecommerce business that sells custom-designed dolls — each made-to-order with specific features, materials, and delivery lead times. A few interesting challenges we faced: SKU Explosion: Each doll can be customized…
We had a recent challenge with the need to "clean" invoice data descriptions from special characters. This was done previously in SQL with the a long convoluted formula "REPLACE(REPLACE(REPLACE('Ana&plan', '&', '') that would have to edited by a developer in case any new special characters came through. Using the replace…
