hi @Ytch , To use the PutDatabaseRecord you need to have the column names defined in whatever input format you have (CSV, Json....etc.) and the column name should match what is in the DB table ( see also the "Translate Field Option" if not exactly the same). If you know the column order in the CSV file you can add a header using the ReplaceText processor as described here: https://community.cloudera.com/t5/Support-Questions/How-to-add-customer-headers-to-csv-file-in-NIFI/m-p/285457   If you find this is helpful please accept solution. Thanks ... View more

Hi @CommanderLaus , If you do anything manually with the processor you are trying to change its Running State through the API, then yes the revision will be updated. In my case what I do is basically the first API InvokeHttp is to get the latest revision using the following GET API:   https://localhost:8443/nifi-api/processors/${pipeline.start.processor.id}   This will give the following response where you can parse the latest "version" value using something like EvaluateJsonPath processor and store the value in an attribute:   { "revision": { "clientId": "value", "version": 0, "lastModifier": "value" }, "id": "value", "uri": "value", "position": {…}, "permissions": {…}, "bulletins": [{…}], "disconnectedNodeAcknowledged": true, "component": {…}, "inputRequirement": "value", "status": {…}, "operatePermissions": {…} }   Then use extracted version attribute to build the next API post Body , for example in my case I use ReplaceText processor to generate the post body :   { "revision": { "clientId": "${pipeline.start.processor.id}", "version": ${processorVersion} }, "state": "...", "disconnectedNodeAcknowledged": true }   Hope that helps.       ... View more

@MattWho, @steven-matison , @cotopaul ...Can you guys help with this? ... View more

Hi @ShaniKumar , Can you please identify clearly with the issue is to help you better? Basically the InvokeHTTP processors allows you to use dynamic invocation using Nifi Expression Language (EL). You can set a flowfile attribute with the intended url before  calling the InvokeHttp processor , for example: you can use UpdateAttribute to set the url to attribute name "UrlAttr" and then reference this attribute in the InvokeHttp "Remote URL" property value as ${UrlAttr}. Other InvokeHttp properties allows to use EL to set the value dynamically and so on as long as the property allows it. Hope that helps. Thanks  ... View more

@PradNiFi1236, Is the invoice number unique? If the filename matches between the two format, have you tried using this instead? Of course you have to derive just the filename without the extension in another attribute first and then use the new attribute for the Correlation Attribute. Also try resetting the "Minimum Number of Entries" to 1 . If none of that helped can you please post screenshot of the mergeContent processor configurations with other critical processors configurations as well. Thanks ... View more