Welcome, Guest
Social Extensions Integration

TOPIC: CB's Field Data Mapping

CB's Field Data Mapping 6 months 1 week ago #1

  • saman
  • saman's Avatar
  • Online
  • تماس با من : samansamani2[at]yahoo.com
  • Karma: 1
If we mapping :
  • system field (like firstname and lastname and etc) of the CB (additional data source for user profile integration) to Moodle's original field
  • and CB new field whose name begins with "cb_" to Moodle's custom field
Synchronous editing these fields of the CB from Joomla's side (Front-end and Backend) will result in the CB new field changes being ignored.


For example, consider this scenario :

Joomdle Mappings list :
Joomla componentJoomla fieldMoodle field
cbfirstnamefirstname
cbcb_father_namefather_name

assume the above fields have these values in the following tables :
  • first name = a
  • last name = b
  • father name = c
  • `joomla_users` table :
    idname
    1a b
  • `joomla_joomdle_field_mappings` table :
    idjoomla_appjoomla_fieldmoodle_field
    1cbfirstnamefirstname
    2cbcb_father_namecf_1
  • `joomla_comprofiler` table :
    idfirstnamelastnamecb_father_name
    1abc
  • `moodle_user` table :
    idauthfirstnamelastname
    1joomdleab
  • `moodle_user_info_field` table :
    idshortnamenamedatatype
    1fathernamefather_nametext
  • `moodle_user_info_data` table :
    iduseridfieldiddata
    111c

Now we modify the user data from the Joomla's side with the following values :
  • first name = aa
  • last name = bb
  • father name = cc
And the result in the tables :
  • `joomla_users` table :
    idname
    1aa bb
  • `joomla_comprofiler` table :
    idfirstnamelastnamecb_father_name
    1aabbc
  • `moodle_user` table :
    idauthfirstnamelastname
    1joomdleaabb
  • `moodle_user_info_data` table :
    iduseridfieldiddata
    111cc
The administrator has disabled public write access.

CB's Field Data Mapping 6 months 1 week ago #2

  • Antonio Durán
  • Antonio Durán's Avatar
  • Offline
  • Karma: 159
Hi.

I replicated the described setup locally, but could not reproduce the problem: data is stored in comprofiler table just fine.
So, problem must be coming from something that it's different between our testing enviroments.
Please send email with info on how to check this on your server, and I will try to take a look.
The administrator has disabled public write access.