Eduard
08/15/2023, 2:54 PMlocationquantityavailable
And then save all this as JSON to a custom record or txt file with one property per item internalid (7K+) and the corresponding current stock as value.
{
"1":5,
"2":4
...
}
so it can be compare every 15 minutes and updated with changes.
Now both methods seem a bit overkill.
Any thoughts or experience with the same usecase?Nathan L
08/15/2023, 4:10 PMbattk
08/15/2023, 4:50 PMbattk
08/15/2023, 4:50 PMbattk
08/15/2023, 4:50 PMbattk
08/15/2023, 4:52 PMlocationquantityavailable
battk
08/15/2023, 4:53 PMbattk
08/15/2023, 4:53 PMEduard
08/16/2023, 7:16 AMEduard
08/16/2023, 7:44 AMconst transactionSearchObj = search.create({
type: "transaction",
filters:
[
["linelastmodifieddate","within","14/08/2023 0:00","16/08/2023 11:00"],
"AND",
["type","anyof","ItemShip","ItemRcpt","InvAdjst"]
"AND",
["mainline","is","F"],
"AND",
["min(accounttype)","isnotempty",""]
],
columns:
[
search.createColumn({
name: "item",
summary: "GROUP"
}),
search.createColumn({
name: "location",
join: "item",
summary: "GROUP",
label: "Location"
}),
search.createColumn({
name: "locationquantityavailable",
join: "item",
summary: "MAX",
sort: search.Sort.ASC
})
]
});
Eduard
08/16/2023, 8:10 AM