@Mahi123    Just to make sure i understand your use case correctly, you want to change the content only of your NiFi FlowFile? You have a NiFi FlowFile with following json content: { "name": "Jon", "title": "king of the nights watch" } and you want to modify it to: { "name": "Jon_<current date>", "title": "king of the nights watch" } I read your statement "I want to change the name of the file" as wanting to edit the filename and not the content of the file itself.  Which is something totally different than above. Assuming you are looking to modify content and not the filename itself, you can do this using the ReplaceText processor after your EvaluateJsonPath processor.   Search Value = ("name": "${name}") Replacement Value = "name": "${name}_${now():format('yyyy-MM-dd-HH-mm-ss')}" Replacement Strategy = Regex Replace Evaluation Mode = Line-by-Line NiFi typically has more than one way to satisfy the use case and there may be better option than the above using the various available record based processors.  You may want to explore those as well. If you found this addressed your query, please take a moment to login and click "Accept" on this solution. Thank you, Matt ... View more

@techNerd  Questions for you: 1. Is Computer B consuming all the files LocalFolder and from every sub-directory within c:\users\LocalFolder?  If yes, then your SFTP processor should be configured to Search Recursively. 2. Once consumed by computer B, are the original file being left on Computer A?  If yes, you do NOT want to use the GetSFTP processor as it will refetch the same files over and over again each time it executes since they are not being removed from Computer A.   A typical dataflow here would look like this: The ListSFTP processor would be configured to use as follows: The "Tracking Entities" listing strategy will help when source files may have older timestamps than files previously listed from a different directory.  Using this listing strategy requires you to set a "Entity Tracking State Cache".  There are multiple cache services to choose from.  I simply used the "DistirbutedMapCacheClientService" controller service which gets configured to point at a "DistributedMapCacheServer"controller service I also setup within the same NiFi. The "Remote Path" is set to the top most folder you want to start listing files from ( C:\User\LocalFolder\ ). The "Search Recursively" property is set to "True" so that any random new sub folders added are also searched. The "Success" relationship is then routed via a connection from the ListSFTP to the FetchSFTP processor.   The FlowFiles produced by the ListSFTP processor will have numerous FlowFile Attributes set on them that will be used later to persist your directory structure and to fetch the content via the FetchSFTP processor. You can list the flowfiles on a queue and click the "view details" icon next to nay listed FlowFile to see the attributes currently assigned to that FlowFile. For example:   filename = testfile-32.txt path = /tmp/LocalFolder sftp.remote.host = <SFTP server hostname> sftp.remote.port = 22   Then if you look at attributes for file from an added SubFolder:   filename = testfile-31.txt path = /tmp/LocalFolder/SubFolder sftp.remote.host = <SFTP server hostname> sftp.remote.port = 22     The FetchSFTP processor then uses these attributes set on each FlowFile to fetch the actual content from the source SFTP server: Downstream in your dataflow after you have fetched the content, you can still use the Attributes on each FlowFile when working with yoru FlowFiles. For example using the "path" attribute to dynamically control where a FlowFile will be written on a target system (might be the local NiFi via PutFile processor,  another SFTP server somewhere else, etc.). If you found this addressed your query, please take a moment to login and click "Accept" on all provided solutions that helped. Thank you, Matt ... View more

@techNerd  Based on yoru example, you can actually modify your XML using the ReplaceText [1] processor. The processor can be configured with Java regex that would match on the string you want to remove and the replacement value would be set to an empty string. Your regex pattern in this case would need to match on (don't forget the spaces): ( unit = ".*?") The parenthesis mark the java regex capture group. .*? is a non greedy match on any character for zero or more characters until the very next quote.  This allows this to match on any variety of unit strings ( meter, kilogram, and lb) from your example This will result in the following: <particular> <name>Nicholas</name> <height unit = "meter">183</height> <weight unit = "kilogram" unit = "lb">75</weight> </particular> <particular> <name>Debbie</name> <height unit = "meter">163</height> <weight unit = "kilogram" unit = "lb">45</weight> </particular> being converted to: <particular> <name>Nicholas</name> <height>183</height> <weight>75</weight> </particular> <particular> <name>Debbie</name> <height>163</height> <weight>45</weight> </particular>   [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.13.2/org.apache.nifi.processors.standard.ReplaceText/index.html If you found this addressed your query, please take a moment to login and click "Accept" on this solution. Thank you, Matt ... View more