Anaplan CoModeler tips

Make targeted and actionable requests. As CoModeler conversations take place within a model, limit your prompts to that model.
Take a step-by-step approach.
Test and iterate. Where possible, test simple, resolve issues, and then add complexity.
Read through implementation plans for accuracy.
Follow your existing change-management and governance processes. Develop, test, and validate development models before promoting changes into production.

Be upfront with context. If you need to give a lot of context, consider using a specification file. This approach has the added advantage of then being available for use in new conversations.
Structure requests as logically as possible using Anaplan terminology. For example: Add a list named Size and populate it with 5 items from 100g to 500g. Add All Sizes as the top level.
Be clear and explicit, and consider giving CoModeler an example.
Try different vocabulary if what you are using isn't giving results.
If you have a preferred or better method of implementing a task, include it in your prompt.

If CoModeler mentions unauthorized or no access to the GraphQL schema, it usually means the request has timed out. Review your prompt and try again.
If you don't like where the conversation is going, start a new conversation and review your approach to explaining what you want to achieve.
If you manually edit a model CoModeler made, start a new conversation to make sure CoModeler doesn't undo what you've done.

Understand the model you are extending. Ask CoModeler to explain it.
Where possible, extend by adding. Build new components that integrate with what you have. This enables you to test the new logic safely, and maintain clear separation. If you are extending an Anaplan application, this also helps ensure manageability and upgradability.
Clearly name any extensions. For example, prefix new modules with EXT_.
Use what you have. For example, don't build a new product hierarchy if you have one you can use.
If existing content needs to reference new content, make the references manually. For example, manually adjust an existing line item formula to incorporate the new extension.
Document your extensions. Ask CoModeler to explain your extension, and then incorporate the explanation in your internal documentation.

Use text-based inputs only in CSV format.
Ensure that any structure in the input file remains consistent across the input file.
When you have input files that work well for you, save them as examples that you can rework and reuse.

Bulk changes are only possible within the model that you are having the conversation about. If you need to make bulk changes across several models, do them one by one.

General