Best Of

Hello everyone,

Thanks for your answer !

Everything was as you. I continue to dig and I found that post :

"Step 2: Create a module and insert two line items. First format it to Flat List and Second Format it to Exhaustive List"

The first time you're working with the flat list, you need to do the step two in two steps as it is explained in the post. Once you've done it one time it will work even if you do the two steps in one.

Have a nice day,

Emilie

@BMayur
Data02 logic is fine but keep the required dimension.
Data02 PY Revenue(import from data hub), PY revenue to CY (formulated)(A2 Account>Product#) →TAR01(A2 Account>Product#)
Revisit the sprint and dive deep

@BMayur
Not sure if it is mentioned to create but in L3 you are suppose to do modelling by considering the use case based on your understanding unlike Level1/Level 2 step by step process of creating the modules, line items, naming conventions, actions, mapping , logics will not be given. Level 3 is similar as a live project in short deriving the desired output based on the use cases.

Hi @DeveloperCYT ,

Alternatively you can turn off all Users from the Module 

Hope this helps.

~Jitendra

Hi @RitaD
As already mentioned.
Below are the few points to check when you change any Model Name?
1. If the model has outbound, In the target Model Source Model mapping has to be updated.
2. All the integration scripts have to be repointed to the New Model Name, if Model name is used for integration mapping.
3. Communicate to all the end users that model name has been changed so that it will not be a surprise for them.

The current time line is for a Beta in April with Early Adopters being able to leverage Anaplan DMS from July of this year.
In the Beta data can be loaded from S3, local CSV file and Anaplan models.

In the July release we expect to add Azure Blob, GBQ, SFDC, Snowflake and SAP through OData.
Post July we have plans for connectors to Workday and SQL Databases.
Additional connectors will be added based in customer demand.

Hello @PaulCooper

I think you are very close! The previous formula can reference the same line it is written in, since the previous function and time make it so that it will not cause a circular reference in this case.

I tried to mock this up to show.

As you can see, I referenced the Previous to my Final Line, since this would continue my logic until the end of time.

Had I put Previous(Moving 3) then it would just show the 200 in April 24, since each month it would continue to look to the Moving 3 line.

The arrows in both cases are showing where the calculation is pulling from.

I hope this helps!
Jason