Best Of
Re: Did anyone faced this issue, why Anaplan is not allowing me to fetch Items using FINDITEM formula?
A couple of questions:
- is the above row axis the Custom Weeks?
- If so, what is the code that it is using?
- if you don't have one, I highly suggest creating one where you can add 1 to it in order to get the next week.
- Instead of breaking it down to the day, why not just add one to the code and do a finditem() on that.
- How does the Custom week list differ from the regular Week list that comes with Anaplan or is the timescale for the model at the month level?
Re: Confirmed PO Delivery - offset function
Hi Misbah,
Can you help me understand why - sign here?
SwapnaB
Re: Confirmed PO Delivery - offset function
suzboyd
Re: Using the same DEV for 3 different production models
I would recommend picking one of two methodologies, although I am sure there are options out there:
- Use 1 DEV and have all models be structurally the same and write booleans into the logic to either include or exclude the region-specific logic. This would be ideal if the models are nearly identical with just some minor variations by Region.
- Have a DEV for each PROD model. Restoring DEV and making changes is not sustainable as you will lose compatibility quickly and it would be very complex to manage. If you needed to make the same update for all 3 PROD models, you would have to make those changes separately in each of your 3 DEV models.
To me, it really comes down to how similar or different the models will be long term.
Jason
Help us shape the admin experience for NLQ at Anaplan!
Hi all!
We’re running customer research to help build an administrative experience for Natural Language Query (NLQ) at Anaplan. We're looking for Anaplan Administrators to take part in this initiative! Take a look at the study details below:
- Video call
- 60 minutes
- $75 incentive
If this sounds like something you’d be interested in you can apply to join the study by answering a couple of questions here!
Thanks for your support,
Emily from Anaplan
EmilyL
Re: "Fake Versions", vs. Native Versions. How do "Fake Versions" work and how do you set them up.
Hi @RijkersB These are pros & Cons of Native and Fake versions.
Native Versions |
Pros: |
1. We can use switchover |
2. We can use bulk copy action |
3. Allow us to compare |
Limitations: |
1. Cannot use Lookup and Sum |
2. Cannout use as line item formatted |
3. Cannot create Version Subsets |
Custom Versions |
Pros: |
1. We can use Sum and Lookup |
2. We can use as line item formmated |
3. We can use subsets |
4. Can be use as production list |
Cons: |
1. We cannot use native switchover |
2. We have to control it by DCA
Thanks,
Bishal
Re: "Fake Versions", vs. Native Versions. How do "Fake Versions" work and how do you set them up.
I replied to your other post asking the same question.
Re: "Fake Versions", vs. Native Versions. How do "Fake Versions" work and how do you set them up.
Fake versions are just a list used a dimension in the same way that real versions would be.
Here is a great article that shows some of the differences:
Re: Can someone help explain what is the difference between a fake version list and native lists?
Native Versions are the versions that come with Anaplan.
"Fake Versions" or Custom Version is a list found under General Lists that is created by the model builder.
Re: Can someone help explain what is the difference between a fake version list and native lists?
It is just another list that you create under General Lists, but happens to be called Scenarios or Version List or whatever you want to call it. The members ste likely Actual, Budget, Plan, and/or Forecast.