Frequently asked questions
Common questions and solutions to the most frequent problems in iPaaS.
General
Do I need to know how to code to use iPaaS?
Not to configure it. The integration is created in the Partner's Portal, and the mapping is suggested by the AI. Your system only needs to make an authenticated HTTP call to the integration's Endpoint URL.
Can I update or cancel documents with the Document Creation (Inbound) template?
Not yet. The template only creates documents (POST). Update (PUT/PATCH), cancellation and deletion are not available yet.
Does the Document Search (Outbound) template send the document to my ERP?
No. It returns the converted document in the response to the call. The caller, usually your middleware or the ERP itself, writes the result to the destination.
What is the difference between an integration and a connector?
The integration is the flow configured from a template, with mapping, credential and Endpoint URL. The connector is the registration of an external API (URL, authentication and resources) that a Product Search integration uses to call the provider. The same connector can be used by several integrations.
Can I use one integration for more than one document type?
No. Each integration handles a single document type. Create one integration for each type.
Credential and authentication
I lost the integration's Secret. How do I recover it?
The full Secret is only available while the creation wizard is open, in the same tab: in the Parameters step and on the Integration activated successfully screen. Once you leave the wizard, it cannot be recovered. Create a new integration, which will have a new credential.
Does editing the integration change the Key or the Secret?
No. Editing and publishing an integration again keeps the same Key and Secret. Your system does not need to change the credential.
I get 401 Unauthorized when executing.
The token is missing, invalid or expired. Generate a new token with the Key and the Secret. See Authentication.
I get 403 Forbidden when executing.
The token was generated with the credential of another integration. Each credential only executes its own integration: check that the {flowId} in the URL matches the Key used (integrationhub-{flowId}).
Execution
I get 422 saying the integration cannot be executed.
The integration is not in a status that allows execution: it is Suspended, Draft or Validated (not published yet; only Product Search can be tested in this status). Check the status in Integrations > My Integrations. See My Integrations.
The Inbound call returned 202, but the document did not appear in ME.
The 202 only confirms delivery. Processing in ME is asynchronous. In Monitoring > Executions, filter by Correlation ID:
- In progress: ME is still processing. If the execution stays In progress for a long time, ME did not return the result: open a support ticket with the Correlation ID.
- Error: open the timeline. The
DOCUMENT_PROCESSINGstep shows the rejection reason reported by ME.
I get 400 with document validation errors.
The converted document did not pass the ME API validation. The errors list brings the fields and the messages. Usually a required field is missing from the mapping, or a value is in the wrong format (date, number). Adjust the mapping: suspend, edit, test and publish again.
I sent the same document twice and it was created twice.
iPaaS does not deduplicate, and x-me-correlation-id does not prevent resends. Control resends in your system.
I get 400 on Order delivery.
The Order delivery type requires the orderId parameter in the query string: .../execute?orderId={order id}.
I get 400 because of a duplicate key in the JSON.
The body has the same key repeated in the same object, for example two "C7_NUM" fields. Fix the JSON generated by your system.
How do I find a specific execution?
Always send the x-me-correlation-id header with an identifier from your system and use the Correlation ID filter in Monitoring > Executions. See Correlation ID.
Mapping
The AI did not map some required fields.
The AI only links fields that have a match in the source and does not make up values. Link them manually, enter a fixed value or use the Assistant ("field X is Y"). If the field exists in your system but was not in the example, use Swap payload with a more complete example.
"Source not found in the sample payload" appears.
The link points to a field that does not exist in the current example, which is common after Swap payload. Link the field again or remove the link.
"Incompatible types" appears.
Source and target have different types, for example text and number. Click the warning and apply a conversion transformation. See Type conversion.
The document items came out "mixed up" or in separate lists.
The fields of the same target list must iterate over the same source list, written exactly the same way. See List to list.
A single ERP field receives the wrong value from an ME list.
The link probably chooses the item by position, and the order of the list changed. Choose the item by a field that identifies it, such as virtualEntityField = 'EMPRESA'. See Choosing one item from a list.
The mapping worked in the test, but fails with some documents in production.
Usually a field that was filled in the example arrives empty (null) in other documents. Make sure the fields used in text functions are protected. See Protection against empty fields.
The AI analysis did not finish.
Very large examples can exceed the analysis time. Use Try again or reduce the example, keeping all the fields but with few items in each list.
Connectors and Product Search
The connector authentication test fails.
Check the base URL, the credentials and, in OAuth 2.0, the token URL, the scope and how the credentials are sent (Advanced > Send credentials via). If you changed the URL host, enter all credentials again.
Product search returns a provider error.
The response passes on the status and the details returned by the provider, with failedAtStep = API_REQUEST. Check that the resource (method and path) is correct and that the request mapping sends the parameters in the format the provider expects.
I cannot delete a connector.
iPaaS blocks the deletion of a connector that is still used by any integration, in any status (including draft or suspended), so that those integrations do not stop working. Switch the connector in those integrations (suspend, edit, test and publish) or delete the integrations you no longer use. Then delete the connector.