Jump to:
| Project: | Ubercart EDI |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | kussmaul |
| Status: | closed (duplicate) |
Issue Summary
More enhancements, for which I'd appreciate feedback and suggestions:
1. My EDI partner requires the header record in one file and each detail record in a separate file.
I could a) split the record in the non-Drupal script that uploads files to the FTP site,
or b) add a "file break" syntax to uc_edi.
2. Some of my products are not shippable, and should not be included in the EDI files.
I could a) filter these out in the non-Drupal upload script, or b) filter them out in uc_edi.
In this particular case I could use the "Product and its derivatives are shippable." setting,
but this might not be appropriate for other EDI applications.
If other people would find these useful, I'm happy to add them to uc_edi
(I'm using a 6.x version, but changes could also be applied to 5.x).
Otherwise, I can use approach b) on my own.
Thanks,
Clif
Comments
#1
1) Since FTP is generally considered to be insecure, the second method sounds better
2) Me too, and this seems like an extremely common use case that should definitely be fulfilled by this module. I made this change for a client, but their version of uc_edi is unhacked and needs to be generalized so I can merge development efforts here. I found that some of the code flow could be optimized a bit, since it seemed inconsistent and was hard to follow.
#2
1) I don't have much choice in uploading via FTP. Now the EDI partner wants 2 files - one with all of the header records, and one with all of the detail records. If we can't find a general way to handle multiple possibilities, it might be better
to create a single file and use separate code to sort lines into appropriate files.
2) This would be great - I guess the module needs some way to indicate whether or not to export non-shippable products, or products need an option indicating whether they should be exported.
#3
This is the first I have heard of splitting the data into two separate files and seems like a extremely rare case. I think this would be best handled in custom code. I am open to suggestions.
FTP capability is on the roadmap for the 6.x-1.1 release. I am curious as to how you solved this and would appreciate some suggestions. Supporting SFTP would be a must.
Another issues exists for selecting which products to export here: #453280: Enhance settings to allow the specification of which products will be exported.
Marking this as "closed (won't fix)" per the title. Product filtering already has another issue. You can open a separate FTP issue if one does not already exist.
Cheers,
Antoine
#4
I wrote a short (non-Drupal) script that opened the Drupal export file, separated content for header & detail files, and did some other custom cleanup. I agree that this seems the best approach for now.
Thank you for followup.
Clif
#5
Splitting files is actually a pretty common use-case:
Having individual orders as unique xml files is quite common for import into big business systems. In my case, I'm having my orders exported using uc_edi to a single xml file and then using a custom module to split out the children into their own xml files for import into the business system.
I will be doing the same sort of thing that kussmaul did as well.
#6
Hi illepic,
Thanks for you input on the issue. I think I misunderstood kussmaul's original issue. I do believe there is a use case for each order being put into its own file. I just finished a patch that offers real-time exports by exporting every order after checkout via conditional actions into its own file using the order id as the unique filename. It could really use a review: #949690: Integrate export functionality with Conditional Actions. Hope this eliminates the need for a second custom module. I'd be interested to hear your thoughts.
Cheers,
Antoine
#7
Wow, Antoine! I will be happily giving this patch a shot today and will report back.