Disconnected List Control / Detail View - List remains dirty after sync

[frankiez]

Out of 300 successful logins in 2 days, I had 2 users who could not sync the list to the server.
My policy is to automatically sync when saving data to the detail view.
The sync button remained enabled and despite repeated syncs, the list remained dirty on the device.
The solution was to delete all keys from local storage.
I removed all write conflict settings so the mobile device is always the winner.
Is there any setting I should check or a way to force the sync so the user is not trapped with a dirty list.

Note: I don't want to refresh and lose any changes that have been made on the device. I prevent refresh method if the list is dirty.

[frankiez]

Re: Disconnected List Control / Detail View - List remains dirty after sync

After more research, I found there was a server-side validation error since the red triangle appeared on the dirty list row.
Question: Is there a list property to indicate there is a server data issue so I can provide option to refresh the list.
I could check for the detail view global error place holder, but I found this only populates when you tap the row that is in question. If I can test for a property to confirm there is a data problem, I can allow the user to correct the problem to take necessary steps to correct.

[Davidk]

Re: Disconnected List Control / Detail View - List remains dirty after sync

The List Detail View Client-side Event, "afterSynchronzeList" will give you a number of properties in it's "e" object. One of them is "recordsWithErrors" which is a count of the errors.

Based on the count, you could run something like the code below, which will have a look at the List Data array and pick out the error rows.
I can't see other List properties or methods that might return this info.


This is code which will give you an array of List errors...

var lData = {dialog.Object}.getListData('LIST1');
var listErrors = [];

//errors are available in the List Data Array row Object property _globalErrors
//listErrors is an array of objects.  Each object is a List row which has an error.
//you can put as much or a little into each object as you want.  You really just the lData array index.
lData.forEach(function(item,index){
	if(item.hasOwnProperty("_globalErrors")){
		listErrors.push({listRow:index,listError:item._globalErrors});		
	}
});

for(i=0;i<listErrors.length;i++){
	console.log("Zero based List Row : " + listErrors[i].listRow + " : Row Error : " + listErrors[i].listError);
}

[Sarah Mitchell]

Re: Disconnected List Control / Detail View - List remains dirty after sync

The List Detail View Client-side Event, "afterSynchronzeList" will give you a number of properties in it's "e" object. One of them is "recordsWithErrors" which is a count of the errors.

Based on the count, you could run something like the code below, which will have a look at the List Data array and pick out the error rows.
I can't see other List properties or methods that might return this info.


This is code which will give you an array of List errors...

var lData = {dialog.Object}.getListData('LIST1');
var listErrors = [];

//errors are available in the List Data Array row Object property _globalErrors
//listErrors is an array of objects.  Each object is a List row which has an error.
//you can put as much or a little into each object as you want.  You really just the lData array index.
lData.forEach(function(item,index){
	if(item.hasOwnProperty("_globalErrors")){
		listErrors.push({listRow:index,listError:item._globalErrors});		
	}
});

for(i=0;i<listErrors.length;i++){
	console.log("Zero based List Row : " + listErrors[i].listRow + " : Row Error : " + listErrors[i].listError);
}

You could also use the <listObj>.getAllErrors() method.

[Davidk]

Re: Disconnected List Control / Detail View - List remains dirty after sync

Nice... thanks Sarah. I've got to remember to look for methods first.

[frankiez]

Re: Disconnected List Control / Detail View - List remains dirty after sync

Thank you David and Sarah for your replies.
Another scenario I have encountered is the deletion of a record on the server AFTER the list is loaded on the device. if the record is changed on the device, the list remains dirty with a red triangle marker indicating a server data error. I can use the code above to error handle the situation.