Transformer ID's within the transformer editor and logging

Transformer debugging is quite challenging at the moment because when you have multiple transformers that require a parameter it does not show which one gets an argument error. It would be very nice if all transformers each have their unique identifier which gets posted back with the error message.

For example we got this:

We got an transformer and while testing we get the following error:
Exception while testing transformer

In the error details we see this:

"file": "/resources/fileshare/deployer/releases/2023-02-08-14-23-58-f371381/vendor/mtdowling/jmespath.php/src/FnDispatcher.php:287",
"message": "Argument 0 of length must be one of the following types: string, array, object. null found",
"class": "RuntimeException"

We got multiple transformers in our setup. It would be nice if we could get identifiers for all nested transformers.

For example maybe something like this:

1 - Chain miltiple entity transformes

1.1 - Data, transform data using mappers and conditions

1.1.1 - Set value

1.1.2 - Move using pattern

1.2 - Data, transform data using mappers and conditions

1.2.1 - Set value

1.2.2 - Move using pattern

1.2.3 - Set value

1.3 - Data, transform data using mappers and conditions

1.3.1 - Conditional transformer

1.3.1.1.1 - Set then value

1.3.1.2.1 - Set else value

With the following error message:

"file": "/resources/fileshare/deployer/releases/2023-02-08-14-23-58-f371381/vendor/mtdowling/jmespath.php/src/FnDispatcher.php:287",
"message": "Argument 0 of length must be one of the following types: string, array, object. null found",
"transformer-id": "1.2.1",
"class": "RuntimeException"

This would help to find the exception and look at the right places.

Hi @Rickvzanden,

Thank you for taking the time to send us your idea. Your feedback is very valuable to us and we appreciate your input.

We would like to evaluate your suggestion more thoroughly before providing a final response. Our team will take some time to review the feasibility and potential impact on our product roadmap. We will get back to you as soon as possible with an update on whether we will move forward with this request or not.

Thank you again for your suggestion and for being a valued customer. If you have any further feedback or questions, please do not hesitate to contact us.

Best regards

1 Like

Hi @Rickvzanden

Thank you for your patience. We discussed your idea with the team and we found that we already have a story to work on related to your idea.

This solution won’t give a transformer ID in the error message, but instead, we will highlight in the UI in which transformer the error occurred, and try to automatically focus on/scroll to the offending transformer.

Would this solution work for you?

3 Likes

Hi Gugi,

This sounds even better!
Great to hear that it is already in a story.

Thank you for the reply.