When Index and SIFT are removed either on new table or on the extended table the dropping of Index, SIFT (Index view) on SQL needs to be automatic rather than relying on
ForceSync Operation. Like in C/SIDE ForceSync Operation should only require handling schema changes which involves dropping field and change in data type and reduction of field length

When any of the following property associated with the key is set the Index/Indexed View should be dropped from SQL automatically.

Enabled = false;
MaintainSqlIndex = false;
MaintainSiftIndex = false;

/* When the SIFT is disabled by setting MaintainSiftIndex = false; Index View is not removed on SQL backend and the following query is issued */

SELECT SUM("37_e2"."K3Outstanding Quantity")
FROM "Cronusgb".dbo."Cronus UK$Sales Line$437dbf0e-84ff-417a-965d-ed2bb9650972" "37" WITH(READUNCOMMITTED)
JOIN "Cronusgb".dbo."Cronus UK$Sales Line$ef933c61-34d2-4d4e-ada4-6fdf714541ab" "37_e2" WITH(READUNCOMMITTED) ON("37"."Document Type" = "37_e2"."Document Type")
AND ("37"."Document No_" = "37_e2"."Document No_")
AND ("37"."Line No_" = "37_e2"."Line No_")
WHERE("37_e2"."Status" = @0
AND "37_e2"."K3 Type" = @1
AND "37_e2"."K3 No_" = @2) OPTION(OPTIMIZE FOR UNKNOWN);


/* Reference to the Base table needs to be removed from the above query. The query should be as follows as well as the Index view needs to be dropped by the system on SQL Backend automatically rather than relying on "schemaUpdateMode": "ForceSync" setting or waiting for a Force Sync operation*/

SELECT SUM("37_e2"."K3Outstanding Quantity")
FROM "Cronusgb".dbo."Cronus UK$Sales Line$ef933c61-34d2-4d4e-ada4-6fdf714541ab" "37_e2" WITH(READUNCOMMITTED)
WHERE("37_e2"."Status" = @0
AND "37_e2"."K3 Type" = @1
AND "37_e2"."K3 No_" = @2) OPTION(OPTIMIZE FOR UNKNOWN);