-
Notifications
You must be signed in to change notification settings - Fork 2
Added: Suite scripts to export store to store transfer orders Json file #197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…d json respectively.
|
||
var connection = sftp.createConnection({ | ||
username: sftpUserName, | ||
keyId: sftpKeyId, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Shinde-nutan, We are not using keyId while setting up the connection with SFTP. Please use secret instead of keyId
}; | ||
|
||
mapContext.write({ | ||
key: internalid, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Shinde-nutan, we should append the line ID with the internal ID to make the key ID unique.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When creating a Transfer Order in JSON format, we use "internalId" as the key. This allows the subsequent method (shuffle) to group all maps with the same key. This grouping will assist us in the reduce method, enabling the creation of a nested JSON structure for the transfer order.
Additionally, as we discussed, I checked and confirmed that while preparing the JSON files, we are not encountering any discrepancies with the items. However, when we attempt to create a CSV file, the execution control does not enter the reduce state, which results in the transfer order not being exported.
Related issue: #194