- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and dashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources

Process Mining
Cause
This error is displayed when creating an output dataset. The created output dataset cannot be saved to temporary files and folders. Most likely, access to the files and folders is blocked by a virus scanner.
Solution
Update to the latest version of Process Mining. Make sure to update both the Superadmin and the Dispatcher build. Select this build as the build version for the connector.
Cause
This warning is displayed when the connector was opened with an input dataset, without reloading the table. The dataset is locally updated in this session, but the input dataset will not have that new reloaded data.
Solution
Select Workspace from the Dataset list in the Open Application dialog when opening the connector. See illustration below.
Go to the Data tab in the development environment, right click on the table list and select Reload all data from the context menu. See illustration below.
Cause
Most likely the connector was opened with an input dataset, or the tables were not reloaded.
Solution
Select Workspace from the Dataset list in the Open Application dialog when opening the connector. Go to the Data tab in the development environment, right click on the table list and select Reload all data from the context menu.
If reloading a table does not show errors but also does not load data, check whether the table scope of the table is set to the correct value.
See Table Scope.
Cause
A ghost is created when an attribute was deleted which still had references, i.e. it was still being used in for example, another expression. You can recognize a ghost by the icon.
Solution
Check the references of the ghost to determine the places where the ghost is still being used. These must be resolved before the ghost can be deleted.
Cause
The wrong delimiter is set in the connection string, for example, “,” instead of “;”.
Solution
Check the delimiter of the input file and set it correctly in the connection string.
Cause
The type or the parse format of the attribute is not set correctly.
Solution
Either change the type to match the attribute or change the parse format to the formatting in the input file.
Cause
mvscript
driver, the script handler needed to execute the script is not defined (properly).
Solution
Configure the script handler in the Server Settings.
- Connector
- Error: Failed to Move TempDir Into Final Location
- Cause
- Solution
- Warning: Table … Has Been Reloaded/updated Locally.
- Cause
- Solution
- No Data Visible in the Connector
- Cause
- Solution
- A Ghost Has Been Created
- Cause
- Solution
- Only One Attribute Found With All the Column Names in It
- Cause
- Solution
- The Attribute Shows Only “Error” as Value
- Cause
- Solution
- Error: The Script Handler for Py Is Invalid, Executable Does Not Exist
- Cause
- Solution