You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Is your feature request related to a problem?
We are showing queried, success and failed count in the sync run listing. In incremental refresh we skip the rows based on the primary key and creates confusion for user eg:total queried is 1000, success =2, failed = 0. The question is where the other 998 records are. why it is not showing in the sync run list metrics.
Describe the solution you'd like
We need to show a new metrics called skipped which states how many records in the sync due to duplicate primary of the model.
Good to have
We need to show skipped rowns count in the reporting dashboard.
The text was updated successfully, but these errors were encountered:
**Is your feature request related to a problem?
We are showing queried, success and failed count in the sync run listing. In incremental refresh we skip the rows based on the primary key and creates confusion for user eg:total queried is 1000, success =2, failed = 0. The question is where the other 998 records are. why it is not showing in the sync run list metrics.
Describe the solution you'd like
We need to show a new metrics called skipped which states how many records in the sync due to duplicate primary of the model.
Good to have
We need to show skipped rowns count in the reporting dashboard.
The text was updated successfully, but these errors were encountered: