What is Production Data? — Part 2
Part 2: Production Imports and Import Data Sources
If you are working in Anaplan and came across that “Production Data” checkbox in the Imports or Import Data Sources(IDS) tabs of Actions, you might wonder how an import or IDS can be production data. What does it even do? And why is it usually unchecked?
In one sentence, that checkbox provides flexibility to the end users with imports and IDSs.
What is Production Data?
Production data is the data that you can change in live models without needing to go back to your development models.
In Part 1 of this article, I explained production data and production lists in more detail.
Imports as Production Data
When an import is marked as production data, model users (not just model builders!) can change:
- The order of that import among other imports
- Import mappings
- Items uniquely identified by
- Treatment of duplicate identifiers in source and target
Import Data Sources as Production Data
When an import data source (IDS) is marked as production data, users can change:
- The order of that data source among other data sources
- The import csv file or the saved view.
Heads-Up: If you change a file with a differently formatted file without remapping the columns import actions will fail. Same for saved views.
If you consider flagging imports or import data sources as production data, mark both as production data. This will decrease confusion.
Flexibility vs. Safety
Marking an import or an IDS as production data gives your users flexibility, but it takes away a layer of safety.
Get Seyma - Anaplan for everyone!’s stories in your inbox
Join Medium for free to get updates from this writer.
If your users are technical, it can be ok, If they are not, you can end up with a broken import and a late-night Teams message about why the numbers don’t add up.
And if you open that door, you also reduce the control power of your development model, because now some changes are happening directly in production instead of through dev and test.
Should you use it?
In most projects, we leave the checkbox unchecked. Why? Because it’s safer. When everything flows from dev to test and prod, you catch mistakes earlier.
But if you do need flexibility, maybe you have power users managing region-specific imports, it can be a lifesaver.
Still, I recommend using a testing model in deployed mode before you let changes loose in prod.
TL;DR:
- Production Data = changeable directly in the live model
- Marking imports/data sources as production data gives users more control — but adds risk
- Only use if you have tech-savvy users or a strong need for flexibility
- If you use it, mark both the import and the data source
- Test, test, test before pushing anything to prod
In the end, it’s a balancing act.
More flexibility = more risk.
More structure = more safety.
And as the Planual says:
“Just because you can doesn’t mean you should.”
How about you?
- Have you ever marked an import or data source as production data in one of your models?
- Did it make things easier or cause unexpected issues?
- What’s your personal rule of thumb for balancing flexibility vs. safety in production?
Let’s chat in the comments, I’d love to hear how your team handles this trade-off.
Want to connect or have a question?
Let’s connect on LinkedIn: https://www.linkedin.com/in/seyma-tas/
Or reach me by email: seymatas@gmail.com
