Jump to main content

# Failed Import 6: Importing a Process Template having a custom field with the same name and a different type than the CASH Workflow field in the target account

In this scenario, the import fails because a process template has a custom field with the same name and different type than the field in the target account.

Example: A process template has a custom field with Address for the name and Number for the type. The target account has a custom field created in CASH Workflow with Address for the name and String for the type.

As a result, the import fails and a message displays with an explanation of the failure.

Note: Select Download to download the log file with detailed information about the failure.

How do I solve this issue?

Update the custom field on the Process Template to match the field on the target account. Repeat the Import process. (Example: Remove the custom field in the Process Template (e.g. Address/Number). Replace the field with a field that matches the field name and type in CASH Workflow. (e.g. Address/String) Repeat the Import process.

You can also update the custom field on the target account to match the field in the process template. Repeat the import process.
Note: The custom field in the target account must be in the 'Never Used' state and not in any inflight processes.