Process for run import/export csv (then automate by scheduler or WF)

Description

i suggest to implement a new process can handle import/export csv automated way. useful for e.g. barcode scanners like cipherlab.

parameters should be
1. Import/export (define its import or export)
2. ad_table
3. file type
4. charset
5. import mode (insert/update/merge)
6. filename (including OS path)

Requirements: process must works from scheduler and workflow.

forum: https://groups.google.com/forum/#!searchin/idempiere/scheduler/idempiere/vbmvdvDVRw4/Tz1Pfnj-7X8J

Environment

None

Attachments

4
  • 01 Aug 2014, 10:14 AM
  • 01 Aug 2014, 10:14 AM
  • 01 Aug 2014, 08:15 AM
  • 01 Aug 2014, 08:02 AM

Activity

Carlos Ruiz 
July 13, 2018 at 9:59 AM

Closing as implemented

Norbert Bede 
October 7, 2014 at 9:27 AM

I can imagine the follow: add as parameters to process
1 window: e.g. select sales order
2. SavedQuery drodown - select saved query before created by user.

one workaround limit our possibilities we cant manage relative date ranges (e.g. last 7 days,) this was mentioned in issues https://idempiere.atlassian.net/browse/IDEMPIERE-1062 and https://idempiere.atlassian.net/browse/IDEMPIERE-1936

Hiep Lq 
August 1, 2014 at 10:14 AM

pack and 2pack just for test ability.
limit:
1. must add way to filter record will export
2. must add way to limit detail tab will export

this limit can easy remove, just need a design.
example: extend scheduler window to define parameter for 1, 2

Norbert Bede 
August 1, 2014 at 8:15 AM

,

i prepare 2 days ago - for better explanation - how we are using (plan partially) cipherlab 8000 scanners for AIDC (http://en.wikipedia.org/wiki/Automatic_identification_and_data_capture).

Lot you wrote above are mentioned are described or just idea on my worflow - illustrates simple scheduled exports/imports.

n

Carlos Ruiz 
August 1, 2014 at 8:02 AM
(edited)

Hi, we made a proof of concept with a simple process (ImportCSVProcess.java attached) - it worked fine importing Freight Categories after a minor fix for a bug we found on GridTable (will commit it next).

We also checked the code attached by at IDEMPIERE-1976. These patches can be a good foundation for the suggested process here.

I think is worthy to discuss more in detail the goal and parameters of this process, and maybe we can try also some additional processes.

What we have analyzed with is something like:

  • ImportCSVProcess parameters:

    • Window (we just allow to load on first tab on the window, loading from a detail tab would require a parent record - this can also be added using a Record_ID reference, but also can be easily workarounded if you create a new window for the load)

    • File

    • Folder to save the log processed file

    • Folder to save the error file

Also we could have a process for end-users if we add the template parameter related to ticket https://idempiere.atlassian.net/browse/IDEMPIERE-2113#icft=IDEMPIERE-2113

An additional process that we think can be worthy is to ask for a folder instead of a file, and then process all files from a specified folder and at the end move the file to a "ProcessedFolder".

Regards,

Carlos Ruiz

Fixed

Details

Assignee

Reporter

Labels

Priority

Created July 28, 2014 at 7:31 AM
Updated September 1, 2018 at 11:01 AM
Resolved July 13, 2018 at 9:59 AM