Anaplan is issuing a new Anaplan certificate on December 8, 2018. You will need to take action based on the integration client and authentication method you are using:
Integration Client
Authentication
Action Required?
Anaplan Connect 1.3.3.5 or lower
Anaplan Certificate
Yes
Anaplan Connect 1.4
CA Certificate
No
Informatica Anaplan Connector
Anaplan Certificate
Yes
Informatica Anaplan Connector
CA Certificate
No
Mulesoft 2.x
CA Certificate
No
SnapLogic 1.x
Anaplan Certificate
Yes
Boomi x.x
Basic Authentication
No
Tableau 1.0
Anaplan Certificate
Yes
Any client
Basic Authentication
No
If your integration client and authentication method has a "Yes" in the "Action Required" column, then you must take action on December 8 to prevent disruption to your integrations.
Note that web login, web SSO, and basic authentication to integrations are not impacted by this event.
This FAQ covers the following topics:
Anaplan-Issued New Certificate on December 8
What is happening?
Anaplan is issuing a new certificate used for integrations on December 8, 2018.
This new certificate is intended to be used for existing clients on the legacy certificate authentication (such as Anaplan Connect 1.3.3.5). This certificate will not work on clients using the CA certificates (such as Anaplan Connect 1.4). Customers will now have two options to continue using certificate authentication with integrations:
Continue using your existing client (e.g., Anaplan Connect 1.3.3.5) by downloading a new certificate on December 8, 2018 after the maintenance window.
Use a client that supports CA certificates (e.g., Anaplan Connect 1.4) by implementing this before December 8, 2018.
Although customers will now have two options to choose from, Anaplan recommends that customers update their integration clients to a version that supports Certificate Authentication 2.0, which uses a CA certificate.
Why is this change happening?
The current Anaplan certificate used by some customers for their integrations is set to expire in December. Customers who are impacted have been updating their clients to use CA certificates. However, we have received feedback that customers need more time to complete these updates and wanted to continue to use their existing clients. In order to support the existing clients, Anaplan will be issuing a new certificate on December 8, 2018 which can be used for certificate authentication. The benefit of this option is that customers can continue to use their existing clients and will have more time to update their clients to use CA certificates after December 2018.
How can you check if this impacts you and what steps do you need to take?
See the Update to Integration Certificate Expiration blog post for information on impact and any steps to take.
Is it possible for you to edit the expiration date on your existing certificates?
No, the expiration date for a certificate cannot be changed. However, you can download a new Anaplan-issued certificate with a 1-year expiration date following the maintenance window on December 8, 2018, and use that with your existing integration client.
How do you apply the certificate issued on December 8?
Assuming that you are using a supported integration client, complete the following steps on December 8:
Anaplan has a planned maintenance window on December 8, 2018. After this window is complete, you can obtain a new certificate.
Log in to Anaplan and go to the My Account page
Click on the Certificates tab, then click the Create new Certificate button. This procedure is documented in Anapedia.
Once you have the certificate, apply it to your integration client. Instructions for applying them are different for every client
Anaplan Connect 1.3.3.5
Informatica Anaplan Connector
Tableau
SnapLogic (SnapLogic maintains the 1.x version of the connector that support Anaplan certs. Please contact SnapLogic for the details of how to apply the certificate)
Certificate Authority (CA) Certificates
Why this change to CA certificates?
As the Anaplan platform evolves, we are always looking to provide our customers with more features and ways to integrate with Anaplan. The new Anaplan APIs and integration connectors leverage Certificate Authority (CA) -issued certificates. CA authentication offers a certificate hierarchy known as the "chain of trust" that enables you to verify the validity of a certificate issuer. This aligns with industry standards and provides a higher level of security for Anaplan customers.
Customers can leverage their own certificates from a trusted Certificate Authority that ends with a supported Root CA Certificate.
Customers can now specify the expiration dates for their certificates.
Customers have the ability to disable the cert themselves through a new interface on Administration.
These certificates can be obtained through your company's intermediary CA (typically issued by IT) or by purchasing it from a trusted Certificate Authority.
This method of authentication also supports Anaplan's new authentication framework which provides for a more secure method for sending credentials on API calls
Which currently available clients support CA certificates?
Anaplan Connect 1.4
Informatica Anaplan Connector
Mulesoft 2.0.1
How do Customers use the CA (Certificate Authentication 2.0) option?
The following links will guide you through the procurement and registration of CA-issued certificates in Anaplan:
How to procure certificates.
How to manage them in Anaplan.
Please note that you can use certificates issued by an Intermediary CA with any of these supported Root CAs . Note that certificates from an Intermediary CA are typically managed by staff in your organization. If you are unsure about whether your intermediary certificate uses a supported Root CA, contact your internal technical staff.
What are the benefits of moving to CA Certificates?
CA certificates align with industry standards and provide a higher level of security for Anaplan customers. For more information, see Administration: Security - Certificates in Anapedia.
Is there a cost to your company for using CA Certificates?
You can obtain a CA certificate from your internal intermediary CA or purchase certificates from a Certificate Authority. If you have an intermediate CA, you can issue the certificate yourself. Your IT team can advise on your internal processes for obtaining certificates based on an intermediate CA.
Integrations and APIs
What integration options and APIs are available to you?
The current Anaplan Production REST API version is v1.3. v2.0 of the Integration API has recently been released. Authentication mechanisms with both API versions are:
v1.3 API:
Basic Authentication
Authentication with Anaplan Certificates
v2.0 API:
Basic Authentication
CA Certificate based authentication
NOTE: Both API versions support Basic Authentication.
Anaplan Integration clients use one or both APIs. For more information on available integrations, see the Update to Integration Certificate Expiration blog post.
What if you are using a custom integration client?
If you have developed your own integration client to Anaplan, or are using a custom integration client developed by a partner or system integrator, the impact depends on what API version was used to develop your connector. If you are using basic authentication to authenticate to Anaplan via integrations, you're not impacted.
If your custom integration client was developed using API v1.3 and you authenticate with Anaplan-issued certificates, you can download the new certificate on December 8, 2018, if you wish to continue using this integration client with certificate authentication. If you want to use a CA certificate, you need to update your custom client to use API v2.0.
If your custom integration client was developed using API 2.0 and you authenticate with CA certificates, you'll be unable to use the new Anaplan-issued certificate on December 8, 2018. You are already using a CA-issued certificate as API 2.0 only supports certificates issued by a CA.
More information about the v2.0 Integration API can be found here: https://anaplanbulkapi20.docs.apiary.io
What should you do if you don't want to upgrade to latest API clients or switch to Basic Auth?
If you want to continue with existing Integration clients or custom integrations, you must switch over to Basic Auth for authentication or download a new certificate on December 8, 2018. With Basic Auth, you will use a user ID and password in your integrations instead of Anaplan Certificates.
You can continue to use your existing integrations with certificate authentication if you download a new Anaplan certificate on December 8, 2018. However, we are encouraging customers to migrate to a new client that supports CA certificates as that is our intended certificate authentication method.
Anaplan Connect
What if you are using Anaplan Connect (AC) for Integrations?
If you are using Basic Auth (user ID and password) in AC 1.3.x.x. scripts, you can continue to do so. You can upgrade to AC 1.4, at your convenience.
If you are using Anaplan certificates for authentication, you can download a new certificate on December 8, 2018. You can keep both AC 1.3.x.x and AC 1.4 installed at the same time, and migrate your integration scripts one-by-one to AC 1.4.
AC 1.4 supports authentication with CA Certificates and Basic Auth. Existing Anaplan Certificates (downloaded from Anaplan UI) are not compatible with AC 1.4. Please review this blog post for steps to port AC 1.3.x.x Integration scripts to AC 1.4: https://community.anaplan.com/t5/Knowledge-Base/Migrating-from-Anaplan-Connect-1-3-x-x-to-Anaplan-Co...
You can take the Anaplan Connect online training from Anaplan Academy: https://community.anaplan.com/t5/Academy-Classes/Data-Related-Training-Classes/ta-p/19566
How do you update Anaplan certificates in Anaplan Connect 1.3.x.x Integrations?
If you are using Anaplan Connect 1.3.x.x. Integrations with Anaplan certificates, you can update the certificates by editing your Integration script files.
Open your Anaplan Connect integration script files (Windows .bat or Unix .sh scripts) in a text editor.
Look for -certificate option in the script. The option is followed by file path to your current Anaplan Certificate.
Download updated Anaplan Certificate from the Certificate tab in your Anaplan My Account page
Copy it to the file destination on the machine where Anaplan Connect 1.3.x.x is installed. You can place it in the same folder as your current Anaplan Certificate.
Edit your integration script and replace file path to old Certificate with file path to new Certificate.
Example
In this example, the previous certificate is: certificate-123456789.cer. The new certificate is: certificate-new4567890.cer. The destination folder where the certificates are placed is: C:\anaplan-connect-1-3-3-5
Open your Anaplan Connect integration script in a text editor.
set Operation - certificate “C:\anaplan-connect-1-3-3-5\certificate-123456789.cer”
Log into Anaplan, click on My Account, then navigate to the Certificate tab and download the updated Anaplan Certificate (certificate-new4567890.cer).
Copy certificate-new4567890.cer to C:\anaplan-connect-1-3-3-5\.
In your integration script, change the line from step 2 to: C:\anaplan-connect-1-3-3-5\certificate-new4567890.cer
As an alternative, you can also rename your new certificate to use the same name as your old certificate and avoid the need to update your Anaplan Connect 1.3.x.x. scripts.
Example In this example, the old certificate is certificate-123456789.cer and the new certificate is certificate-new4567890.cer.
Log into Anaplan, click on My Account, then navigate to the Certificate tab and download the updated Anaplan Certificate (certificate-new4567890.cer).
Go to the folder on your machine where old certificates is located.
Rename your old certificate certificate-123456789.cer to backup-certificate-123456789.cer
Copy certificate-new4567890.cer to C:\anaplan-connect-1-3-3-5\, and rename it to certificate-123456789.cer
Run your integration scripts. You don’t need to edit your scripts.
You can find the Anaplan Connect 1.3.3.5 user guide here.
How do you create a JAVA keystore for use with Anaplan Connect 1.4?
You can refer to following sources for information on creating JAVA keystore for use with Anaplan Connect v1.4:
Refer to section "Certificate Authentication using Keystore" in https://s3.amazonaws.com/anaplanenablement/Community/Anapedia/Anaplan_Connect.pdf
Refer to "Certificate Authentication Process" video recording at https://community.anaplan.com/t5/Videos/bg-p/Videos
Additionally, you can refer to the full Anaplan Connect online training at Anaplan Academy: https://community.anaplan.com/t5/Academy-Classes/Data-Related-Training-Classes/ta-p/19566
Single Sign-On (SSO)
Does this impact Anaplan Single Sign-on (SSO)?
No. There is no impact on Anaplan Single Sign-on (SSO). The impact is only on the Anaplan data Integration API and Integration connector authentication.
What if you’re using SSO and need to integrate with Anaplan?
Accessing Anaplan via a browser with standard login or with SSO is not impacted by this change. The certificate used in SSO is unrelated to the certificates used for integration certificate authentication.
Customers who are configured to use SSO have two options to authenticate their integrations with Anaplan:
If the actions you want Anaplan Connect to run are for models in a workspace using single sign-on, you can use certificate authentication. We recommend using the new certificate authentication 2.0 if possible which supports CA Authentication .
If you are configured for Single Sign-on (SSO), but have a requirement for a user to bypass it and use basic authentication (username and password) instead, then the user must be configured as an Exception User. An Exception User can authenticate by username and password or by certificate, rather than through SAML. For more information, see Assign Exception Users in Anapedia.
More Questions?
Who should you contact in case of more questions?
Please post your questions in the Forum . Alternatively, you can contact your Anaplan Customer Success (CS) Business Partner.
... View more

Based on customer feedback and to allow admins additional time to transition to new integration clients, Anaplan will be issuing a new Anaplan certificate on December 8, 2018. You will need to take action based on the integration client and authentication method you are using:
Integration Client
Authentication
Action Required?
Anaplan Connect 1.3.3.5 or lower
Anaplan Certificate
Yes
Anaplan Connect 1.4
CA Certificate
No
Informatica Anaplan Connector
Anaplan Certificate
Yes
Informatica Anaplan Connector
CA Certificate
No
Mulesoft 2.x
CA Certificate
No
SnapLogic 1.x
Anaplan Certificate
Yes
Boomi x.x
Basic Authentication
No
Tableau 1.0
Anaplan Certificate
Yes
Any client
Basic Authentication
No
If your integration client and authentication method has a "Yes" in the "Action Required" column, then you must take action on December 8 to prevent disruption to your integrations.
By December 8, 2018 you have two options:
Continue using your existing client (e.g. Anaplan Connect 1.3.3.5) by downloading a new certificate on December 8, 2018
Use a client that supports CA certificates (e.g. Anaplan Connect 1.4) by implementing this before December 8, 2018
Anaplan is extending the deadline to migrate to Certificate Authority (CA) certificates to December 2019. In order to support this, on December 8, 2018, Anaplan will update our production certificate. This will replace validation for Anaplan certificates and existing Anaplan certificates will cease to work once this certificate has been issued.
This new certificate is intended to be used for existing clients on the legacy certificate authentication (such as Anaplan Connect 1.3.3.5). This certificate will not work on clients using the CA certificates (such as Anaplan Connect 1.4).
Although customers will now have two options to choose from, Anaplan recommends that customers update their integration clients to a version that supports Certificate Authentication 2.0 which uses a CA certificate.
Note that web login, web SSO, and basic authentication to integrations are not impacted by this event.
Why is this change happening?
The current Anaplan certificate used by some customers for their integrations is set to expire in December. Customers who are impacted have been updating their clients to use CA certificates. However, we have received feedback that customers need more time to complete these updates and wanted to continue to use their existing clients. In order to support the existing clients, Anaplan will be issuing a new certificate on December 8, 2018 which can be used for certificate authentication. The benefit of this option is that customers can continue to use their existing clients and will have more time to update their clients to use CA certificates after December 2018.
What is the impact on customers?
If you are using basic authentication (username and password) to authenticate to Anaplan Integrations:
Basic authentication does not use a certificate, meaning the certificate expiration doesn't impact you. You can continue to use whatever integration client that you are using today.
If you have already transitioned to a new integration client:
Customers who have already implemented a new integration client (such as Anaplan Connect 1.4 or Informatica Anaplan Connector) can avoid the impact of the certificate expiration by using Certificate Authentication 2.0 or basic authentication. These clients support this new type of authentication which requires customers to provide their own Certificate Authority (CA) certificate. This is the recommended route for customers as Certificate Authentication 2.0 is the expected and future method for using certificate authentications with Anaplan integration clients. As you will be using your own provided CA certificate, you are not impacted by the Anaplan-issued certificate expiration and cannot use the new Anaplan-issued certificate. However, you must implement before December 8, 2018.
If you are still on a legacy client:
You should download new certificate on December 8, 2018 and apply it to your integration client. Only after you download a new certificate and update your integration client will your integration continue to function. You can obtain this new certificate by generating it from the My Account page starting on December 8, 2018, following the planned maintenance window. You'll also be able to download additional certificates after this date.
To obtain a new certificate:
Anaplan has a planned maintenance window on December 8, 2018. After this window is complete, you can obtain a new certificate.
Login to Anaplan on December 8, 2018.
Navigate to My Account > Certificates tab and download the new Anaplan Certificate. For more information, see Certificates in Anapedia.
Replace your existing Anaplan Certificate with the new one in your Integrations
Copy new Certificate to the location where your Integration client needs it to be present (for example, the folder on server where Anaplan Connect is installed).
Modify your Integration scripts or connection settings to point to the new Certificate file
Your Integrations will run after making above changes. Every integration client will have different steps to apply a certificate.
Note: Some new integration clients, like Informatica Anaplan Connector, support both certificate authentication methods. If you use Informatica to integrate with Anaplan using certificates and are unable to switch to using a CA certificate at this time, you can obtain a new Anaplan-issued certificate on December 8, 2018, and use that with your Informatica integration.
Which authentication method does an integration client support?
This change only impacts certificate authentication with integration clients. Logging in to Anaplan via the web with standard login or SSO is not impacted. Integration authentication with basic authentication is also not impacted. The CA certificate that customers provide for Certificate Authentication 2.0 is not compatible with Certificate Authentication 1.0.
What is important is what version your integration client supports.
Integration Client
Basic Auth.
Certificate Auth. 1.0 (Anaplan certs)
Certificate Auth. 2.0 (CA certs)
Note
Anaplan Connect 1.3.3.5
X
X
Anaplan Connect 1.4
X
X
Informatica Anaplan Connector
X
X
X
Mulesoft 2.0.1
X
X
Boomi 1.x
X
This version of the client never supported certificate authentication
Boomi 2.x
X
X
Boomi has informed Anaplan that this is scheduled for Q1 2019
SnapLogic 1.x
X
X
SnapLogic 2.x
X
X
Snaplogic has informed Anaplan that this is scheduled for Nov 10
Tableau 1.x
X
X
Tableau 2.x
X
X
This has not yet been released
Workiva
X
Workiva has confirmed that existing Anaplan integrations are not impacted
Docusign Integration
N/A
N/A
N/A
Docusign integration is not impacted
Note: Consult individual user guides for any additional steps required to implement CA authentication with an individual connector.
If your integration client supports Certificate Authentication 1.0, then you can use this client with the new certificate that will be available on December 8.
If your integration client supports Certificate Authentication 2.0, then you can use this client with a CA certificate that you will provide.
How do I apply the certificate issued on December 8?
Assuming that you are using a supported integration client, complete the following steps on December 8:
Log in to Anaplan and go to the My Account page
Click on the Certificates tab, then click the Create new Certificate button. This procedure is documented in Anapedia.
Once you have the certificate, apply it to your integration client. Instructions for applying them are different for every client
Anaplan Connect 1.3.3.5
Informatica Anaplan Connector
Tableau
Snaplogic (Snaplogic maintains the 1.x version of the connector that supports Anaplan certs. Please contact Snaplogic for the details of how to apply the certificate)
What if I'm using a custom integration client?
If you have developed your own integration client to Anaplan or are using a custom integration client developed by a partner or system integrator, the impact depends on what API version was used to develop your connector. If you are using basic authentication to authenticate to Anaplan via integrations, you're not impacted.
If your custom integration client was developed using API 1.3 and you authenticate with Anaplan certificates, you can download the new certificate on December 8 if you wish to continue using this integration client with certificate authentication. If you want to use a CA certificate, you need to update your custom client to use API 2.0.
If your custom integration client was developed using API 2.0 and you authenticate with CA certificates , you'll be unable to use the new Anaplan-issued certificate on December 8, 2018. You are already using a CA-issued certificate as API 2.0 only supports certificates issued by a CA.
More information about API 2.0 can be found here: https://anaplanbulkapi20.docs.apiary.io/#
How long will this new Certificate Authentication 1.0 certificate last?
The new certificates issued on December 8, 2018 will expire after 1 year. However, the expectation is that you will use this time period to migrate to Certificate Authentication 2.0 as soon as you can. We are issuing this new 1.0 certificate in order to give customers the time to make the switch - all new development will be based on Certificate Authentication 2.0.
For example, Anaplan has recently released an API as part of the new Audit feature. This API has only ever supported Certificate Authentication 2.0.
What if I have more questions?
Review our Certificate Expiration FAQs.
Questions, Comments, or Concerns?
Do you have feedback or questions on the “Update to Integration Certificate Expiration” blog post? Share your thoughts on our Anaplan generated Certificates to expire Dec 10, 2018 Community thread.
... View more

Hi @UpaliW, the keystore alias & password must be saved in the script file. This allows AC 1.4 to extract the Private Key & Public Certificate. Alias & password are standard features on JAVA keystores.
Customer must install AC 1.4 & its Integration scripts on a secure server & limit access to that server.
... View more

Hi @winstonquan, if you are looking to create custom integration by directly invoking REST APIs, please wait for Anaplan to release the v2.0 API & user guide. If you are interested in Anaplan Connect v.14, you can use it without needing to refer to the API guide. Thanks.
... View more

Hi @winstonquan, I believe your query is about Anaplan Connect (AC) v1.4 availability. We released it on yesterday, Sep 21st. Please refer to Anaplan blog posts. You can download AC v1.4 from Anaplan Community and start building integrations with CA certificates.
... View more

Hi @DeveloperCYT, we are planning to release an updated Anaplan Connect (AC) v1.4 in the near term. This provides support for CA certificates. You can migrate your AC 1.3.x.x integration scripts to AC 1.4 at your convenience. Please watch the Anaplan product releases page.
... View more

Hi @winstonquan, please refer to https://anaplanauthentication.docs.apiary.io/# for mechanism for API authentication using CA certificates. We will release the v2.0 Integration APIs in near-term and you should find more information in the updated API user guide.
... View more

Hi Upali, with Basic Auth, user name & password are saved in the Anaplan Connect integration batch file. We cannot encrypt the user name & password. If client is SSO enabled, they must identify an integration user ID & set it up as an Exception user.
More information is available at this link: https://community.anaplan.com/t5/Internal-Release-Notes/Anaplan-generated-Certificates-to-Expire-December-10-2018/ba-p/36175
... View more

Update (Nov 7, 2018)
Based on customer feedback and to allow admins additional time to transition to new integration clients, Anaplan will be issuing a new Anaplan certificate on December 8, 2018. The current Anaplan certificate will stop working on December 8. You will need to take action based on your integration client and authentication.
Please refer to the Update to Integration Certificate Expiration blog post and Certificate Expiration FAQs for more information.
Do you have questions about the new Anaplan-generated certificates? Share your thoughts below. Click the Reply button below to post.
... View more

This article outlines the requirements for Anaplan Technology Partners who want to integrate with Anaplan using Anaplan v2.0 REST APIs.
Use Cases
The following use cases are covered:
Allow users to run integrations from the partner technology or application with or without an external integration tool to move data to and from Anaplan.
Provide the ability to import data into Anaplan for planning and dashboarding and extract the planning results from Anaplan into the partner technology or application.
Provide the ability to extract data from Anaplan modules and lists or import data into Anaplan modules and lists.
Provide the ability to extract data from Anaplan into the partner technology or application to run specific planning scenarios or calculations.
Requirements
To integrate with Anaplan:
Users must have a license for the partner technology and credentials to log in to Anaplan. Basic authentication or certificate authentication methods are supported.
Users must have Import and/or Export actions configured in Anaplan or have the ability to create these actions in Anaplan.
Assumptions
Technology partners are familiar with Anaplan modelling concepts and Anaplan APIs. Information can be found on anaplan.com , help.anaplan.com , Anaplan Academy and Anaplan API reference material .
Anaplan supports the deletion of items from very long lists using the Delete from List using Selection This can be invoked via a REST API.
Import chunks are between 1 MB and 50 MB in size. Export chunks are 10 MB in size.
Anaplan data exports and imports will run in batch mode.
All Anaplan exports will be generated as .csv or .txt (tab delimited files). Anaplan imports will similarly accept .csv or .txt formatted data.
All data movements will follow format and rules defined in Anaplan actions.
Constraints
Users can create an Anaplan Process to chain multiple Import / Export actions together and execute them in sequence. However, some functionality is not supported, e.g. files will not be output to UI for Export actions.
Not in Scope
Process action support is not required.
OAuth
File types other than .csv and tab-delimited files.
Changes to Anaplan UI, login mechanism or Anaplan APIs.
Guidelines
Authentication
Support for Basic Authentication (user name and password).
Support for Certificate Authentication (uploading an x509 cert).
A custom header will be sent in the header for every API call to Anaplan to uniquely identify the partner technology and its version. For example, format "{Partner Prod name} {version}".
Behavior
The partner technology or application must allow users to log in to Anaplan with credentials and present list of Export or Import actions for user to select from:
Get the workspace that the user has access to (present workspace name, not ID).
Get the models that the user has access to (present model name, not ID)
Workspace and model are used in the URL for other endpoints.
Export and Import actions
Based on the Workspace and Model selected, present the Export / Import actions, with the name, to the user for selection. This list of actions will match what is presented in the Anaplan UI.
Each action is associated with a Module or List in Anaplan.
Execute the Export / Import action; by posting a task against the action, the action is run.
Export action: getting the file
Assuming that the task succeeded, pull down the file (in some cases, in chunks).
If the file is in chunks, Partner code will need to concatenate the chunks together.
Export action: parse the exported file
The file should be in .csv or .txt format.
Invoke Anaplan Export API endpoint "GET https://api.anaplan.com/.../exports/<export id>" to get fields for the Export action.
Export action: analyze exported data
Most users will want to analyze multiple modules and lists.
Each export is for one module or list.
Users will need to be able to execute more than one export in order to populate their partner technology environment.
Export action: multiple exports
In Anaplan, a Process is a wrapper of multiple actions that are executed in sequential order. It is not possible to pull the export files using a process so individual exports are required.
The partner technology must allow for more than one export to be selected by the user.
The calls will need to be made independently as each export will need its own task ID. (This is assuming that exports run on different modules or lists.)
Export action: get the files from multiple exports
This is the same as pulling files from a single export call, except that the code needs to ensure that it is pulling the correct file after the export is called.
Files for all defined exports should already exist in the system so calling them will not result in the failure. However, calling them without executing a new export task or before the export task completes successfully can lead to downloading outdated information.
If tasks are created against a single model in parallel, the actions will be queued and run in sequence.
Check that the task completes successfully before pulling the related file.
Import action: uploading data
The Technology Partner will split data to be uploaded into chunks of certain size. Anaplan APIs support upload chunk sizes from 1MB to 50MB.
These chunks will be uploaded to Anaplan in sequential manner.
Once all chunks are uploaded, the Import action will be triggered by a separate REST API call.
Error handling
The Anaplan API is REST so expect standard HTTP error codes for API failures.
Import action failures are found by doing a GET on the TASK endpoint. The JSON response will have a summary and for error conditions, there will be a dump file that can be pulled to get more details.
The partner technology or application will need to fetch the dump file via a REST API call, save the file, and then process it.
Export dump files are unusual - they are more common for imports.
Ensuring that the task completes successfully before retrieving the file will avoid receiving outdated information from Anaplan.
If a task fails, report the errors back to the user.
Any automatic restarts should be very limited in scope and user configurable to prevent infinite loops and performance degradation of the model.
Labeling
Labels should follow Anaplan naming conventions:
Export
Workspace
Model
File
For example, executing an Export action should be called ‘Export’ not ‘Read’.
Definitions
Workspace
Each company (or autonomous workgroup) has its own Workspace. A workspace has its own set of users and may contain any number of models.
Model
A structure where a user can conduct planning. It contains all the objects needed for planning, such as modules and lists, but also the data values.
Module
Components of each Anaplan model, built up using line items, timescales, list dimensions, and pages. A module contains the metrics for planning.
Lists
Groups of similar items, such as people, products, and regions. They can be combined into Modules.
Actions
Operations defined by users to execute certain functions, such as imports, exports, or processes. Actions must be defined in Anaplan before they can be called in the API.
Process
Groups actions and executes them in sequential order.
Data Source Definition
The configuration of an action that details how the data is handled.
Task
The job that executes actions and contains metadata regarding the job itself.
... View more

We are pleased to announce Sep-2017 release of Anaplan Connector for Informatica Cloud. This release fixes Success/Error row counts in Monitor Log for Data Synchronization Tasks (DST).
Success/Error row logic for modules is given below
Module Import Action - Success rows indicates number of Line Items with ALL cells accepted for Insert / Update by Anaplan - Error rows indicates number of Line Items with atleast 1 cell ignored/rejected by Anaplan Module Export Action - Success rows indicates number of Line Items exported by Anaplan - Error rows should always show 0
You should note that, for modules, Success/Error numbers in DST Monitor Log means number of Line Items. If a line item has any cell that is ignored or rejected by Anaplan, that Line Item will be counted as an Error row. For e.g. if your module has 10 Line Items, and 3 Line Items have 1 or more data cells that are rejected or ignored by Anaplan, the Success/Error count will be 7 & 3 respectively.
Tip
Anaplan ignores cells at Parent hierarchy level, e.g. parent Qtr/Year for Time dimension. Remove such parent columns from your input data before running Anaplan Import. Else, these Line Items will be marked as Error in DST Monitor Log.
Success/Error row logic for Lists is given below
List Import Action - Success rows indicates number of List Items accepted by Anaplan for Insert / Update - Error Rows indicates number of List Items ignored/rejected by Anaplan List Export Action - Success rows indicates number of List Items exported by Anaplan - Error Rows should always show 0
... View more