Skip Aggregation for EDI Missing
For EDI Imports, the advanced "skip aggregation" option is missing. It is available on JSON, XML, XLSX, CSV, but on EDIFACT, EDIX12, of Fixed Width. Having it available would make sending files easier because if you want to use the multiple ST transactions, then you need a SINGLE record to run through the flow, then an array of the transactions as an array within that single record object. If you have more than one record in the page, then you all put multiple ISA and GS headers in a single edi file which isn't correct.
JSON options:
EDI options:
-
Katarina Brunnestom not sure if you can help here. Seems like a big gap for edi transactions.
Here is an example where there are multiple records in the page, you all export it like this which isn't valid edi.
0 -
I'll follow up on the missing "skip aggregation" option for these file types EDIFACT, EDIX12, of Fixed Width and add it if it is not by design.
On the 2nd comment about the edi gap transaction, would you log a support ticket so the team can investigate further?
Thanks
0 -
I have one ticket open for UI preview working for multiple ST transaction, but not actually exporting on ticket #105904. I followed this documentation and it works in preview, but not in actual flow run.
0 -
1) The "Skip Aggregation" option is not available for the user in the UI for the reason that structured file imports (e.g. EDI, EDIFACT, Fixed Width) consisting of filedefinitions does not have aggregation supported on IO Imports, since we generate one file for each page.
However, we are setting this option to true by default for these file types in the backend, this enhancement will be available to our clients by 15th-Feb-2022. If you want to set the "Skip Aggregation" there is a workaround where you can set this field in the EDI Imports in the backend with IO API. Here is the link to configure Import fields in the backend using IO API. Please let me know if you need any help with this.
2) Regarding your comment "Noticing multiple ISA and GS segments in a single header file". I would like to know if there are multiple records in a single EDI file or only one record per EDI file because aggregation is done at the page level and not at the record level. If multiple records are being exported on a single page then we need to investigate this issue further from our side.
0 -
Pridhvi #1 makes sense, but if it's defaulted to true, then I shouldn't be having this issue.
I set my flow to have 1 record per page, but am still having this happen:
0 -
Thank you for your confirmation, After a meeting with the engineering team, the team confirmed that this is a known issue and the fix for this will be released to clients by 15th-Feb-2022. Until the issue is fixed I would recommend you to use the workaround that I suggested in my previous comment to complete the step in the process. I will keep you posted once the issue is released. Please let us know if you need any help while working on the workaround.
0 -
Pridhvi I may need some help. I don't see a field for that in the get request.
0 -
I believe you should add the following line of code ("skipAggregation":true,) at the pointed location. Could you please try this and let me know if that helps.Thank you
0 -
Pridhvi I need skip aggregation to be true though so that only 1 file is made per page. You said it's set to true by default so I'm not sure how this helps me?
0 -
My sincere apologies for the confusion I created here, it should be set to true, I made a mistake. I have updated my previous comment.
0 -
Pridhvi that worked, but now I still have another issue which I have a ticket open for. In my mapping to edi, everything previews fine, but none of the mappings actually export. The support team didn't see anything wrong, but maybe we could meet real quick to review? I need to get this integration up and going.
0 -
I'm glad to see the workaround helped in fixing the issue. Our team had investigated the issue (#105904) and found out that the issue is with the file definition and requires a modification, we are currently working on building the file definition rules. I will keep you updated with the progress on this, thank you.
0 -
There is an easier workaround for this without having to go through the API, just temporarily set the filetype to CSV, check the skip aggregation box, set the filetype back to EDI and Save the import.
Works and is non-destructive to any of the EDI-specific settings.
0
Please sign in to leave a comment.
Comments
13 comments