This proposal allow import DMS content based on CSV files, by using a defined import loader format and import tables.
FIELDS
isImported, yes, no
error message
ad_table => We will attach to this table
record_id => We will attach this content to a specific database record id (if known)
record_value - eg. product key, bpartner search key, document no for c_order etc.
content_source - this is the source of the content - can be local, remote file, or url - if no HTTP(s): or S3 prefix then we assume this is a file
content type - we would like to select this content type
attribute_values -- various attributes importable/definable for a content attr1=10 | attr2=B etc.
DMS content => This will be set after successfully imported. when isImported=Y
PROCESS
- delete all
- source: storage provider OR URL
- storage provider - where data are stored
- move files to - folder /backup - string allow define.
This proposal allow import DMS content based on CSV files, by using a defined import loader format and import tables.
FIELDS
isImported, yes, no
error message
ad_table => We will attach to this table
record_id => We will attach this content to a specific database record id (if known)
record_value - eg. product key, bpartner search key, document no for c_order etc.
content_source - this is the source of the content - can be local, remote file, or url - if no HTTP(s): or S3 prefix then we assume this is a file
content type - we would like to select this content type
attribute_values -- various attributes importable/definable for a content attr1=10 | attr2=B etc.
DMS content => This will be set after successfully imported. when isImported=Y
PROCESS