Just to add a bit more info, below is the job that we submit. The lo_completion_date field is submitted with the correct date. The LMS records that date for the attempt, but then changes the session/course completion date to today’s date instead of the original completion date that was previously recorded for the session/course.
{
"name": "Import Learning Object Completions",
"endpoint": "/learn/v1/lo/tracks/batch",
"method": "POST",
"chunk_size": 100,
"type": "importer",
"data_source": {
"datasource_params": {
"skip_first_row": true,
"charset": "UTF-8",
"delimiter_type": "autodetect",
"delimiter": "",
"filename": "{{filename_hashed}}"
},
"mapping": >
{
"code": "username",
"name": "username",
"index": 0
},
{
"code": "course_code",
"name": "course_code",
"index": 1
},
{
"code": "lo_name",
"name": "lo_name",
"index": 2
},
{
"code": "lo_code",
"name": "lo_code",
"index": 3
},
{
"code": "lo_user_status",
"name": "lo_user_status",
"index": 4
},
{
"code": "lo_type",
"name": "lo_type",
"index": 5
},
{
"code": "lo_completion_date",
"name": "lo_completion_date",
"index": 6
},
{
"code": "lo_score",
"name": "lo_score",
"index": 7
}
],
"type": "csv_user_import"
},
"notify": true,
"notify_email": "{{notify_email}}"
}
I can’t confirm, but I feel like I saw this behavior about a year ago when playing with this. I think ended up basically double processing, updating the LO and then updating the course completion directly, annoying.
I can’t confirm, but I feel like I saw this behavior about a year ago when playing with this. I think ended up basically double processing, updating the LO and then updating the course completion directly, annoying.
Yes. Very annoying and time-wasting. It doesn’t make any sense since we’re already telling the system what date to apply the score to and the users are already in a completed status. I opened a ticket to see if we can get some action on it.
I can’t confirm, but I feel like I saw this behavior about a year ago when playing with this. I think ended up basically double processing, updating the LO and then updating the course completion directly, annoying.
Yes. Very annoying and time-wasting. It doesn’t make any sense since we’re already telling the system what date to apply the score to and the users are already in a completed status. I opened a ticket to see if we can get some action on it.
Guess is it is an overwrite thing instead of just an update diff thing, gets you to this process.
Just got notification that a fix to this is scheduled for April 26th.
Ah nevermind…. It was another bug that will be fixed. Still waiting on this one. 
