Inconsistency between report and import process

[wtct]

Generated report in the uSync dashboard is informing about possible updates by a handler which is set to the create only mode. In my opinion it's confusing and not strict to the real action which takes place during importing.

I mean that the report is informing about changes, but finally they are not applied during the import process if a specific handler is set to the create only mode.

Steps to reproduce the behavior:

1. Set the CreateOnly option to true for the DictionaryHandler as documented here: https://docs.jumoo.co.uk/usync/13.x/uSync/guides/dictionary#make-the-dictionary-handler-create-only
2. Apply changes in any existing dictionary entry.
3. Discard changes in the updated .config file related to the modified dictionary entry.
4. Run report in the uSync dashboard.

Expected behavior
Report doesn't present updates in dictionary items once the CreateOnly option is enabled. Only missing dictionary entries should be included in the report.

Screenshots
A screenshot and more details you can find in the conclusion of our article which is about recommended uSync configuration in regards of the Dictionary synchronization.

About your Site (please complete the following information):

• Umbraco Version: 13.9.2
• uSync Version: 13.3.2

Additional context
In our case the DictionaryHandler is assigned to the Settings tab.

BTW, As you may notice, we are also wondering whether the CreateOnly option should be enabled by default.

cc: @piotrbach

[KevinJump]

yep we will fix that - the checks in report should respect the rules before they run. (i think dictionaries are 'special' and might have been missed for this)

I am not sure we would enable create by default, especially only on one thing. the generic and expected behavior is a "sync", everything is synced. so i think we would want that to be what happens for all.

We are considering some "simpler" setting flags, that basically map to these common setups, so you don't need to do all the set, default, settings stuff. that's hopefully something we will get in the next major release.

[KevinJump]

Put the right branch in now, and this should be fixed for the next release. (and we will check v16 also)