Importing and exporting analytics
Analytics are imported as part of an ACL project or packaged analysis app. When you import an ACL project that contains one or more analytics, it is identified as an analysis app and placed in the Analysis Apps sub-folder.
You can then export the analysis app out of AX Server to work with the analytics in an ACL project.
Importing analytics
To import analytics, you must import the ACL project that contains them. You can import an ACL project (.acl file) directly into the Analysis Apps sub-folder, or import a packaged analysis app (.aclapp file) that also contains interpretations.
Whichever method you choose, your project must contain at least one analytic script to run as an analysis app on AX Server.
For steps and additional information, see Import a folder item.
Note
To import interpretations, you must first repackage the analysis app (.aclx file) that contains them with the related ACL project (.acl file) as a packaged analysis app (.aclapp file).
Importing ACL projects directly (.acl)
ACL projects with a .acl file extension contain analytic scripts, tables, and data files. You can import these projects directly without packaging them, but they cannot be run in the Analysis App window.
Importing packaged analysis apps (.aclapp)
Packaged analysis apps (.aclapp file) contain analytic scripts, tables, and data files. You can also include interpretations that you created in a related analysis app (.aclx file) using the Analysis App window.
For more information about packaging analysis apps for import into AX Server, see Packaging analysis apps.
Exporting analytics
To export analytics, you must export the entire analysis app that contains them as an ACL project. All analytics and scripts within the analysis app are exported as a single ACL project.
For steps and additional information, see Export a folder item.