About MarkWarren

Hi Mark,   thanks for caveat and your help. I've already managed to do that. It's possible to find those id's in a console, after you open summary setting and choose ratio.   I know that's not good to have 800 line items in one module, but that's the only way to meet the requirement in this case. Anyway the module's total size is a pretty small, so it works fine.   Thanks again ... View more

Hi Vamshi,   Change the module Timescale to "Year" Format. ... View more

Please consider this guidance when using special characters, icons/emojis etc. within Anaplan. They can impact data integrations and also may not render the same across all browsers. https://help.anaplan.com/anapedia/Content/Modeling/Build%20Models/Naming%20Restrictions.html   ... View more

Thank You Mark for the response,   Its only for Northeast region that my values are mismatched, let me drill down and try finding it myself, Else i'll share my model with you.   Regards, Pulkit ... View more

Hi Andre, It is not possible to set the value of a line item from a page selector, so you will not be able to  synchronize the line item in module '1' with the page selector.   You could have the line item in module 1 drive other modules when its list formatted value is changed though... ... View more

Thanks for taking the time to reply, Mark.   I understand that as a workspace admin I am able to import into any cell. However, I am trying to let an end user import into the "Base" data type without giving her the write-access in selective access from Users permissions.   I was exploring using accounts (personnel exp vs non-personnel exp accounts) as a dimension along with data type and users to designate the level at which I want to control the dynamic cell access but it seems that selective access (in Users) supersedes dynamic cell access. Since DCA is in addition to selective access, does that mean the Base would have to be marked as write-only first and then apply the combination of read/write dynamic cell access to all other modules using the data type list? Thanks, Charly ... View more

Imports will work with semi-colons. You need to specify the separator format when you set up the import definition in Anaplan.   Some more info here https://help.anaplan.com/anapedia/Content/Import_and_Export/Get_Started_with_Imports.html ... View more

This is fantastic information! I have used the techniques here to improve performance on filters signficantly. In one case, I was able to reduce the load time for a saved view from over 2 minutes down to 2 seconds. ... View more

Hi,  I saw that you got an answer on this internally, here is that for reference: "No, basically you cannot do this. If you want to filter data on an export, you need to rely on 1/ user's data access 2/ the way you build the view your export is based on. In the case you describe, sending the username back to Anaplan will be indeed too lengthy. Instead, you should match the username that you can export and use it for authentication. As you do not want to store passwords, you should consider Certificate authentication." There isn't a mechanism for this in the API, the filter needs to be inculded in the export definition.  You could have a two stage process, where you set the export filter first (basically the scenario you have described). Or you do as Cristophe suggested and use the API process to select user based exports by dynamically referencing their cert file or credentials. ... View more

Can I also add the recommendation to add a Product Properties module in case you need to do similar lookups or need to  refer to items or parents elsewhere in the model. Here's an example: You can then refer to this in another module in a boolean dimensioned by Products with: Product Family.Forecasted Family[LOOKUP: Product Properties.Product Family] ... View more

Hi, I don't fully understand the issue, but I agree with Paul that a mapping module would probaly be the best approach. I can definitely say that it would be best to avoid SUM/LOOKUP combinations. LI2[SUM: M1.SL2, LOOKUP: SL1]  SUM/LOOKUP combinations generally perform poorly and this can be made worse when the dimensions between source and target differ, which I think they would here. Happy to take a look at the model if you'd like. Send me a DM ... View more

If a formula is too long to read and format in the Anaplan editor then there is a good chance that formula may be complex in its calculation. My advice would be to separate parts of the long formula out into new line items, this is definitelty recommended if any parts of the formula are repeated. The separation should make the formula and module more readable and maintanable and should reduce the calculation cost / improve performance. As with all performance changes, test before and after (stopwatch time) to know the change has helped... Example This formula: IF ISNOTBLANK(Promotion) THEN IF NOT Promotions.Finished? THEN IF MAX(Product.Costs[LOOKUP: Promotion.Category] - Shipping.Expense[LOOKUP: Shipping Date] + Promo Cost, 0) <> 0 THEN MAX(Shipping.Expense[LOOKUP: Shipping Date] - Product.Costs[LOOKUP: Promotion.Category], 0) ELSE Promo Cost ELSE IF MAX(Product.Costs[LOOKUP: Promotion.Category] - Shipping.Expense[LOOKUP: Shipping Date] + Promo Cost, 0) <> 0 THEN MAX(Shipping.Expense[LOOKUP: Shipping Date] - Storage.Cost[LOOKUP: Export.Location], 0) ELSE Promo Cost ELSE IF MAX(Storage.Cost[LOOKUP: Export.Location] - Shipping.Expense[LOOKUP: Shipping Date] + Promo Cost, 0) <> 0 THEN MAX(Shipping.Expense[LOOKUP: Shipping Date] - Storage.Cost[LOOKUP: Export.Location], 0) ELSE Promo Cost   Can be written as: IF ISNOTBLANK(Promotion) THEN IF NOT Promotions.Finished? THEN if_a ELSE if_b ELSE IF MAX(lookup_c - lookup_b + Promo Cost, 0) <> 0 THEN MAX(lookup_b - lookup_c, 0) ELSE Promo Cost where: if_a = IF MAX(lookup_a - lookup_b + Promo Cost, 0) <> 0 THEN MAX(lookup_b - lookup_a, 0) ELSE Promo Cost if_b = IF MAX(lookup_a - lookup_b + Promo Cost, 0) <> 0 THEN MAX(lookup_b - lookup_c, 0) ELSE Promo Cost if_c = IF MAX(lookup_c - lookup_b + Promo Cost, 0) <> 0 THEN MAX(lookup_b - lookup_c, 0) ELSE Promo Cost lookup_a = Product.Costs[LOOKUP: Promotion.Category] lookup_b = Shipping.Expense[LOOKUP: Shipping Date] lookup_c = Storage.Cost[LOOKUP: Export.Location]       ... View more