I found out this solution but when I apply it on nifi it returns an error saying " is invalid because specification not valid for the selected transformation but it works on jolttransformation demo (https://jolt-demo.appspot.com/#inception😞 [ { "operation": "shift", "spec": { "*": { "id": "id" }, "#1": { "&": "result" } } } ] I don't understand why ... View more

It seems that you were able to split the problem in the two key steps: 1. Define the attribute 2. Route on the attribute   First question: Is defining the attribute succesful? Please check your message in the queue directly after doing this evaluatejsonpath. Look carefully (not sure if it is case sensitive/what it does with quotes).   Second question: Are you able to make any attribute based routing work? Perhaps just try some things till anything works and see what the difference is with your flow. The only thing I could think of are trivial points such as case sentivity (maybe), or extra quotes/spaces. You may try something even simpler like route if it contains the letter c, for your first test. ... View more

 Hi alexmarco,   I did not find the 'Upload/Attach' option to upload the template file . Could you please follow the steps/screenshots mentioned , it should work for your example well.   thanks   ... View more

@alexmarco it seems like you resolved your issue. If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future.      ... View more