Controlling what data is syncd back to the server

All replies

• 

  

  0

  Sign in to vote

  your SqlCeClientSyncProvider would run just fine in 2.1 and you dont have to change it to SqlSyncProvider. the providers work differently and its not just a matter of changing the provider.

  if you want to manipulate client changes before they are uploaded and applied to the server, you can subscribe to the ChangesSelected event on the client side and go thru the change dataset and manipulate it.

  here's a sample:

  void LocalDataCache1ServerSyncProvider_ChangesSelected(object sender, Microsoft.Synchronization.Data.ChangesSelectedEventArgs e)
          {
              //let's check if we're synching the table we're interested
              if (e.Context.DataSet.Tables.Contains("WorkOrders"))
              {
                  var dataTable = e.Context.DataSet.Tables["WorkOrders"];
                  for (int j = 0; j < dataTable.Rows.Count; j++)
                  {
                      DataRow row = dataTable.Rows[j];

                      // we're only interested in updates
                      if (row.RowState == DataRowState.Modified)
                      {
                          // check if the status is Completed
                          if (row["Status"].ToString() == "Completed")
                          {
                             // let's delete the row so it gets applied as a delete instead of applying it as an update
                              dataTable.Rows[j].Delete();
                          }
                      }
                  }
              }
         }

  • Marked as answer by Kyle LeckieEditor Wednesday, November 10, 2010 1:23 AM

  Tuesday, November 9, 2010 4:24 PM
• 

  

  0

  Sign in to vote

  Thanks. That gives me something to work with.

  I'm working through the sample provided at: http://msdn.microsoft.com/en-us/library/ff928701(v=SQL.110).aspx

  After data is synched to the client, I insert a new record on the client and sync this back to the server. All is ok.

  I then delete the record from the client and attempt to block the deletion from synching to the server using:

  SqlCeClientSyncProvider csp = new SqlCeClientSyncProvider(Utility.ConnStr_SqlCeClientSync);
  csp.AcceptChanges("Sales.Customer");

  This fails with error:

  System.Data.SqlServerCe.SqlCeException was unhandled
    Message=Column or constraint could not be dropped because it is referenced by a dependent view or constraint. [ __sysChangeTxBsn ]
    Source=SQL Server Compact ADO.NET Data Provider
    HResult=-2147217776
    NativeError=0
    StackTrace:
         at System.Data.SqlServerCe.SqlCeChangeTracking.ProcessResults(Int32 hr)
         at System.Data.SqlServerCe.SqlCeChangeTracking.DisableTracking(String tableName)
         at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.DisableOcsTracking(String tableName)
         at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.EnableOcsTracking(String tableName, TrackingKeyType seTrackingType)
         at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.CreateOcsTable(String fmtTableName, Boolean createTable, SyncTable syncTable, SyncSchema syncSchema, SqlCeCommand cmdUtil)
         at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.CreateSchema(SyncTable syncTable, SyncSchema syncSchema)
         at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.GetChanges(IEnumerable`1 tableNames)
         at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.AcceptChanges(IEnumerable`1 tableNames)
         at Microsoft.Synchronization.Data.SqlServerCe.SqlCeClientSyncProvider.AcceptChanges(String tableName)
         at SyncExampleConsoleForDelete.Program.Main(String[] args) in D:\Projects\LSIORDbProvision\SyncExampleConsoleForDelete\Program.cs:line 30
    InnerException:

  So there appears to be some issue with SqlCeClientSyncProvider calling into SqlCeChangeTracking.

  Anyhoo, I took your advice and used event code to trap the deletion at the client. It appears to work. The deletion on the client is not synched to the server.

  static void ClientSyncProvider_ChangesSelected(object sender, DbChangesSelectedEventArgs e)
  {
   if (e.Context.DataSet.Tables.Contains("Sales.Customer"))
   {
    DataTable dt = e.Context.DataSet.Tables["Sales.Customer"];
    for (int j = 0; j < dt.Rows.Count; j++)
    {
     DataRow row = dt.Rows[j];
     if (row.RowState == DataRowState.Deleted)
     {
      row.AcceptChanges();
     }
    }
   }
  }

  I have a lot of tables to deal with, so I'm not keen on looping thru a bunch of rows, but the client won't have a lot of entries in the tables.

   

  Thanks again.

   

   

   

   

  Tuesday, November 9, 2010 8:43 PM