Hi @piyush7829 , Glad it worked and you were able to do the post. If I understood your question correctly then you need to pass the series_id to the post:form:series_id multipart form property dynamically, right? If that is the case then its easy since the InvokeHttp multipart dynamic properties allows for expression language you can reference the series_id attribute you have extracted using the EvaluateJsonPath and assign it as follows: post:form:series_id: ${series_id} Every time the invokeHttp is triggered it would evaluate the series_id expression from the incoming flowfile and assign its value before making the api invokation. Hope that helps.   ... View more

Thank you @SAMSAL , I tried using JOLT, but when it didn't work, I resorted to using the UpdateRecords process. However, this is ultimately what I need. ... View more

Hi @cotopaul , Thanks for your help. Actually you are right. Im not sure what I was thinking when I posted this or under what circumstances I was getting this error but I retried what I posted and it work so I apologize if I wasted your and the community time. However, what if I want to store the schema in the ValidateRecord processor itself as I would think that would be the proper way to use. Notice how in that processor there is no such field for setting the Date\Time format , and if I provide my schema to it by setting (Use Schema Text Property) I dont get an error but my flowfile goes to the "invalid" relationship complaining that the dob filed doesnt have the valid type!     In this case I did not use any schema def in the record reader\write but I kept the data format set to MM/dd/yyyy. Is there a way to fix this or am I using the processor the wrong way? Thanks again for your help.   ... View more

Dear @SAMSAL , Thank you so much for helping, we tried different ways, and we decided to use the solution that you mention above by concatenating those columns. ... View more

No error when I write the flow file but in the super onTrigger session.get() returns a null. So I have tried to transfer to the same queue using session.transfer(ff) but that gives an error saying Cannot transfer FlowFiles that are created in this Session back to self`. Finally I have decided to write a custom processor from scratch using the code from invokeHttp for my usecase. Thank you all for the inputs. ... View more

I had a need for multiple Lookups...custom Groovy processor with several LookUp services as a part of it...consolidated that, routed accordingly, and performed faster.   ... View more

Hi, The processor sure changed in 2.0 from before , so few things I will check : - Make sure the Request Bondy Enabled is set to true - Make sure the Request Content-Type is set to : multipart/form-data - Make sure to set the Request Multipart Form-Data Name to: file - Once you set the property above, the property Request Multipart Form-Data Filename Enabled becomes visible , make sure it sets to true and it will use the filename attribute in the Content-Disposition header. - Make sure to set the  Response Generation Required property to: true (default false) - Finally, I dont think you need the Content-Disposition dynamic property since its already been set through the above properties. I honestly dont like how in 2.0 there is a lot of visibility dependency with some of the properties where their visibility depends on setting the value of others. It makes it confusing specially when you read the documentation and struggle to find all the mentioned properties until you set the right values. I would rather if its all showing  or at least less visibility dependency on some of them.  Let me know if that works for you or not. If it does, please accept solution. Thanks         ... View more

Hi @jkkk , Can you please post screenshots  of the configurations of the  the InvokeHttp processor and upstream processor\s that creates the json? Also since you mentioned that you are using the evaluateJsonPath  processor make sure that the Destination property is set to flowfile-attribute and not flowfile-content.   ... View more

Hi, Have you looked into the EnforceOrder processor : https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.23.2/org.apache.nifi.processors.standard.EnforceOrder/index.html Based on your description it should do the job. One thing to keep in mind if you want this to work is what is stating in the description : "... [IMPORTANT] In order to take effect of EnforceOrder, FirstInFirstOutPrioritizer should be used at EVERY downstream relationship UNTIL the order of FlowFiles physically get FIXED by operation such as MergeContent or being stored to the final destination. " The group identifier will be in this case the value of the fragment.identifier: ${fragment.identifie} The Order Attribute will be the name of the fragment.index: fragment.index If you find this helpful please accept the solution. Thanks ... View more

Thanks! This scripting approach looks to be working. I'll be sure to look into the ExecuteScript processor more 🙂 ... View more