You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

in v5... each mapping is equal to a input name 
if the field is in subform, then the field id need to prefix with the id of subform lah
this allow u to import to several tables based on the form binder in the form 
tht y i told u ..u can even import user.. or using bean shell for import
becoz the import is handle by the form binder
the validation is handle by form as well
account_id is the field id
account_crm is the subform id
it is follow the form input name
when u check the input field in ur subform using firebug.. u can see this

 

NameDescription
File Upload FormSpecify the source Form where File Upload element resides.
Upload Field IDFile Upload element ID in the specified form above.
Store Data Form

Specify on where to store the data by choosing a target form.

How storing works?

The target form's store binder will be called upon for data storage.

Column Mappings

Map the source file's CSV values to the target form fields.

NameDescription
Column NumberRefers to the column number in the source CSV. Integer only, starts from 0.
Field Name

Must be a element ID in the target form specified above, "Store Data Form".

If you are referring to a Subform in the target form, remember to prepend the field name with subform element ID followed by an underscore.

Example

Subform ID: account_crm

Field ID: account_id

Field Name: account_crm_account_id

Key Column Number

Column number that holds the primary key value.

If nothing is defined, a UUID will be assigned when importing.

Start From Row NumberRow number to start importing data. Integer only, starts from 1.
Foreign Keys

Define other values that can not be found in the CSV file such as Foreign Key value associations data. You may also define hard-coded value here too.

NameDescription
Field NameField name in the target form.
Value

Value to be set.

Hash Variable is accepted.

  • No labels