Hi, The path you specified seems to be correct according to the XML you provided. Since you did not provide the full XML I was only able to test it on the following:   <?xml version="1.0" encoding="UTF-8"?> <SalesOrder> <MessageProcessingInformation> <SendingSystemID>SMS_0175</SendingSystemID> </MessageProcessingInformation> <Header> <SalesDocumentType>YPO0</SalesDocumentType> <SalesOrganization>7002</SalesOrganization> <DistributionChannel>00</DistributionChannel> <RequestedDeliveryDate>2023-06-15</RequestedDeliveryDate> <CustomerPurchaseOrderDate>2023-06-15</CustomerPurchaseOrderDate> <Incoterms1>EXW</Incoterms1> <Incoterms2>Ex Works</Incoterms2> <PaymentTerms>E007</PaymentTerms> <CustomerPurchaseOrderNumber>990831 </CustomerPurchaseOrderNumber> <ReferenceDocumentNumber>SI-000000614</ReferenceDocumentNumber> <ServicesRenderedDate>2023-06-15</ServicesRenderedDate> <LogisticData> <SourceReferenceDocumentNumber>SI-000000614</SourceReferenceDocumentNumber> <SourceSalesOrderNumber>SO-000050562</SourceSalesOrderNumber> </LogisticData> </Header> </SalesOrder> and I was able to get the ReferenceDocumentNumber using the Path: /SalesOrder/Header/ReferenceDocumentNumber Notice I had to remove the following line because I was getting Parsing Error: <ns1:SalesOrderMessages mlns:ns1="http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/SalesOrder" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> What are you seeing exactly? Are you seeing an error or the value is not populated in the FileName  attribute ? Can you please provide more info on that? Thanks   ... View more

To be honest I do not really understand your question. If you split your original file into smaller chunks, you will have X flowfiles instead of a single flowfile. Those flowfiles will then go sequentially in your HTTP response Processor, based on your load balance strategy. ... View more

@kumsath  I'm happy to see you resolved your issue. 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

@kumsath Yes, when i saw your post I started digging around too.  The issue here is number manipulation and type casting a "number" versus a "string". That easy gets complicated in attributes and with nifi expression language functions.   The solution i referenced would take the "number" and make a number in which the visual representation should then be correct.  Its worth a try since that execute script should be very easy to test.    The alternative is to do your "math" upstream or in an execute script processor not in updateattribute. ... View more

For Site to Site , NiFi nodes to which data needs to be send or received should be part of polices , proxy and retrieve site-to-site details and send/receive  data  site-to-site. ... View more