What if I want to pass attributes instead of flowfile content? ... View more

Some progress: I've modified the transformation like this: [{ "operation": "shift", "spec": { "Orders": { "*": { "Headers": { "*": "header.&" }, "Locations": { "Shipper": { "*": "sender.&" }, "Consignee": { "*": "consignee.&" }, "Unload": { "*": "unload.&" } }, "Goods": { "*": { "GoodsDetails": { "*": { "@(2,GoodsTypeName)": "rows.GoodsTypeName", "@(4,Locations.Consignee.ConsigneeName)": "rows.ConsigneeName", "@(4,Locations.Consignee.IdPlanToLocCUS)": "rows.IdPlanToLocCUS", "@(4,Locations.Consignee.ConsigneeAddress)": "rows.ConsigneeAddress", "@(4,Locations.Consignee.ConsigneeCountry)": "rows.ConsigneeCountry", "@(4,Locations.Consignee.ConsigneeEmail)": "rows.ConsigneeEmail", "@(4,Locations.Consignee.ConsigneeNotes)": "rows.ConsigneeNotes", "@(4,Locations.Consignee.ConsigneeReference)": "rows.ConsigneeReference", "@(4,Locations.Consignee.ConsigneeRegion)": "rows.ConsigneeRegion", "@(4,Locations.Consignee.ConsigneeTel)": "rows.ConsigneeTel", "@(4,Locations.Consignee.ConsigneeTown)": "rows.ConsigneeTown", "@(4,Locations.Consignee.ConsigneeZipCode)": "rows.ConsigneeZipCode", "Packs": "rows.Packs", "NetWeight": "rows.NetWeight", "GrossWeight": "rows.GrossWeight", "Cube": "rows.Cube", "Meters": "rows.Meters", "CodiceUnivocoCollo_1": "rows.CodiceUnivocoCollo_1", "CodiceMaster": "rows.CodiceMaster", "ItemCode": "rows.ItemCode", "Seats": "rows.Seats", "Height": "rows.Height", "Width": "rows.Width", "Depth": "rows.Depth", "Note": "rows.Note", "@(4,Locations.Unload.UnloadName)": "rows.UnloadName", "@(4,Locations.Unload.IdShipToLocCUS)": "rows.IdShipToLocCUS", "@(4,Locations.Unload.UnloadAddress)": "rows.UnloadAddress", "@(4,Locations.Unload.UnloadCalendarNote)": "rows.UnloadCalendarNote", "@(4,Locations.Unload.UnloadCountry)": "rows.UnloadCountry", "@(4,Locations.Unload.UnloadDate)": "rows.UnloadDate", "@(4,Locations.Unload.UnloadEmail)": "rows.UnloadEmail", "@(4,Locations.Unload.UnloadNotes)": "rows.UnloadNotes", "@(4,Locations.Unload.UnloadReference)": "rows.UnloadReference", "@(4,Locations.Unload.UnloadRegion)": "rows.UnloadRegion", "@(4,Locations.Unload.UnloadTel)": "rows.UnloadTel", "@(4,Locations.Unload.UnloadTime)": "rows.UnloadTime", "@(4,Locations.Unload.UnloadTown)": "rows.UnloadTown", "@(4,Locations.Unload.UnloadZipCode)": "rows.UnloadZipCode", "@(4,Locations.Unload.ObbligatoryUnloadDate)": "rows.ObbligatoryUnloadDate", "@(4,References)": { "*": { "TypeReference": { "OC": { "@(2,ValueReference)": "rows.info1[]" }, "CM": { "@(2,ValueReference)": "rows.info7[]" } } } } } } } } } } } }, { "operation": "cardinality", "spec": { "header": { "*": "ONE" }, "sender": { "*": "ONE" }, "consignee": { "*": "ONE" }, "unload": { "*": "ONE" } } }, { "operation": "shift", "spec": { "header": { "*": "header.&" }, "sender": { "*": "sender.&" }, "consignee": { "*": "consignee.&" }, "unload": { "*": "unload.&" }, "rows": { "*" : { "*" : { "@": "rows[&1].&2" } } } } }]   Everything works as expected when i have multiple elements in GoodDetails like this: "GoodsDetails": [ { "Packs": 1, "NetWeight": 3.800000, "GrossWeight": 4.800000, "Cube": 0.693000, "Meters": 0.000000, "Note": "good note" }, { "Packs": 1, "NetWeight": 3.800000, "GrossWeight": 4.800000, "Cube": 0.693000, "Meters": 0.000000, "Note": "good note" } ]   However, when the element is only one like this: { "Packs": 1, "NetWeight": 3.800000, "GrossWeight": 4.800000, "Cube": 0.693000, "Meters": 0.000000, "Note": "good note" } The result is really bad: rows": [{ "ConsigneeZipCode": null, "UnloadZipCode": null, "info7": "230500003530", "info1": "V6157-0360", "Seats": null }, { "Packs": null }] It seems that when the element is only one, the first shift transformation does not consider resulting rows[ {}, {} ] as an array.... but something like: row{ name1: value1 name1: value2 ... }   Any suggestion really appreciate.   ... View more

Yes correct....the file is read in the first fragment, updated and then saved into a local folder....and so on for every fragment.    I want to be sure that every updare is saved without loosing data. ... View more

Hey, Generally JOLT tries to maintain the input order. The only way that I can think about is an hard-coded approach. Add this after the default spec: { "operation": "shift", "spec": { "Order": { "*": { "top-level": { "ProcessType": "[&2].ProcessType", "FreightTerm": "[&2].FreightTerm", "OrderNumber2": "[&2].OrderNumber2", "TransmissionCommand": "[&2].TransmissionCommand", "SequenceNumber": "[&2].SequenceNumber", "SenderAbbreviation": "[&2].SenderAbbreviation" }, "CustomerAddress": "[&1].CustomerAddress", "ShipmentAddress": "[&1].ShipmentAdress", "Volume": "[&1].Volume", "Weight": "[&1].Weight" } } } }   Also, are you trying to "duplicate" the value of "OrderNumber2"?   The other solution I can remember to "replace" JOLT is by using FasterXML/Jackson ... View more

Many thanks, it works like a charm!     ... View more