Filters - Changing parameter values from client side

[sojan1]

Hi
I want the sync to only synchronise the current parameters set in the client.
how can i change the parameter?

link i am refering to [https://dotmimsync.readthedocs.io/Filters.html]

Client side
var parameters = new SyncParameters
{
{ "CLNT_ID", "D4" }
};

if i want to change D4 With D5? i.e. i dont want to synchronise D4.. how can i do it?

Server side
var setup = new SyncSetup("_clnt", "PROJECT");

        var clntFilter = new SetupFilter("_clnt");
        clntFilter.AddParameter("CLNT_ID", "_clnt", true);
        clntFilter.AddWhere("CLNT_ID", "_clnt", "CLNT_ID");
        setup.Filters.Add(clntFilter);

        var projFilter = new SetupFilter("PROJECT");
        projFilter.AddParameter("CLNT_ID", "PROJECT", true);
        projFilter.AddWhere("CLNT_ID", "PROJECT", "CLNT_ID");
        setup.Filters.Add(projFilter);

        builder.Services.AddSyncServer<SqlSyncProvider>(connectionString, setup, options);

Thanks

[Mimetis]

You can change D4 to D5

[Mimetis]

are you using SQLite on client side ?
If yes, SQLIte is not applying any filter locally, even if they are defined, since SQLite is only a client database, and filter are applied on server side.

Maybe this is something we need to reconsider

[Mimetis]

I remember we had this conversation with @gentledepp, but I dont remember exactly why we changed this behavior

[sojan1]

Yes, i am using SQLite on client side.

[Mimetis]

I've published a new beta version 1.0.0-beta-1514
You should try it, I've added the filter on the sqlite side

[sojan1]

Hi,

It works very well. :) Thank you very much.

Can i ask you few more questions.

1. Is it possible to add a new CLNT_ID (eg: D7) on client's SQLite and have that D7 added in the filter parameters to push it to the Server. Or how can i add a new record(new clnt_id) on client side and synchronize it with the server.

2. is there a way to have more than one value(D4, D6) filtered against same field (CLNT_ID ) . ? Will multiple parameters work if i put something like below ?

Server Side-
var clntFilter = new SetupFilter("_clnt");
clntFilter.AddParameter("CLNT_ID", "_clnt", true);
clntFilter.AddCustomWhere("{{{CLNT_ID}}} IN (@CLNT_ID)");
setup.Filters.Add(clntFilter);

Client Side-
var parameters = new SyncParameters
{
{ "CLNT_ID",( "D4, D6" )}
};

3. What is your opinion on do the provisioning using a windows application on a server machine, and only perform the synchonisation using the web api http://localhost:81/api/sync.
(meaning not to trigger a provisioning job using client device, instead do the provisioning always on server side using a windows form or console application.)

Thanks

[Mimetis]

1) Adding a new parameter "on the fly"

Yes it's possible. It's an advanced scenario, so be sure you understand what you are doing here.
Here is small piece of code as demo:

// classic sync for A_BIKES
var paramsABikes = new SyncParameters { { "ProductCategoryId", "A_BIKES" } };

// Sync server. Create the local schema, Get all the A_BIKES rows, and apply them locally
var s1 = await agent.SynchronizeAsync(setup, paramsABikes, progress);
Console.WriteLine(s1);

// Adding a R_BIKES product category, and we want to upload it, despite the fact we don't have yet a correct scope
await DBHelper.AddProductCategoryRowAsync(agent.LocalOrchestrator.Provider,  "R_BIKES", default, "R Bikes category");

// the params to use                
var paramsRBikes = new SyncParameters { { "ProductCategoryId", "R_BIKES" } };

// You need to do this trick only ONE TIME.
// Once it's done, you don't have to do it on every sync, of course
// -----------------------------------------------------------------
// Get the scope client for R_BIKES from local storage
// The GetScopeInfoClientAsync method will create the scope if it does not exists in the local database
var scopeClientRBikes = await agent.LocalOrchestrator.GetScopeInfoClientAsync(syncParameters: paramsRBikes);
// hack the last sync datetime
scopeClientRBikes.LastSyncTimestamp = 0;
scopeClientRBikes.LastSync = DateTime.Now.AddDays(-1);
// Save it
await agent.LocalOrchestrator.SaveScopeInfoClientAsync(scopeClientRBikes);
// -----------------------------------------------------------------

// now sync
var s2 = await agent.SynchronizeAsync(setup, paramsRBikes, progress);
Console.WriteLine(s2);

2 AddCustomWhere()

AddCustomWhere is your best bet, I guess.
Be careful on using it, and check the documentation about AddCustomWhere.

Especially, be careful about sync_row_is_tombstone

Be careful also to use a SQL statement that will work on both client & server databases (SQL Server / SQLite)

Honestly, I would prefer to go with several parameters and one sync per parameter, and not using the AddCustomWhere method.

At the end, you will have N sync, for N parameters, but you will be more in control.
Just my opinion

3 Provisionining

If yo have access to the client through a TCP connection for the provision step, it will be way faster, and it's a good thing.

[sojan1]

1. Adding a new parameters on the fly-
   Will 2 scopes solve the problem one with filters and one without filters just for the main tables?

[Mimetis]

Probably, I think you should test it :)

[sojan1]

It worked the way you proposed in the above post :) - Adding a new parameter "on the fly".

Only thing is it is adding an extra scope on the client's Scope_Info_Client table with the name DefaultScope

[sojan1]

Hi @Mimetis, Does the latest version [1.0.0-beta-1517] have all the changes made in 1.0.0-beta-1514 ?

Thanks,

[Mimetis]

yes