v17: Report for Content CreateOnly keeps showing as 1 pending change

[joepvtl]

Describe the bug
We have some content we only want to be created when it is not there yet. When the content has been created, but the node gets a new name later on, the uSync report shows that there is a pending update for the CreateOnly content.

To Reproduce
Steps to reproduce the behavior:

1. Create a Content node on root
2. Import it with CreateOnly enabled
3. Change the name of that node
4. Run report and see that there is a pending change

Expected behavior
If the content is already imported, don't show a pending change.

About your Site (please complete the following information):

• Umbraco Version: v17.3.3
• uSync Version: v17.3.1

[KevinJump]

Hi just checking this , can you confirm the config for create only.

as an example i have this (create only on all handlers).

  "uSync": {
    "Sets": {
      "Default": {
        "HandlerDefaults": {
          "Settings": {
            "CreateOnly": true, 
          }
        }
      }
    }
  }

[joepvtl]

Hi Kevin,

This is the configuration we are using:

"uSync": {
    "Settings": {
      "ImportAtStartup": "None",
      "ExportOnSave": "None",
      "RootFolder": "uSync/v17/"
    },
    "Sets": {
      "Default": {
        "HandlerDefaults": {
          "UseFlatStructure": false,
          "Settings": {
            "CreateOnly": "false"
          }
        },
        "Handlers": {
          "ContentHandler": {
            "Settings": {
              "CreateOnly": "true"
            }
          },
          "DictionaryHandler": {
            "Group": "Settings",
            "Settings": {
              "CreateOnly": "true"
            }
          }
        }
      }
    }
  }

[paria1420]

Hi, I’d like to take a look at this one. I’ll try to reproduce it locally on Umbraco v17/uSync v17 by creating content with CreateOnly enabled, renaming the node, then checking why the report still marks it as pending. If I can confirm the cause, I’ll open a small PR.

[joepvtl]

Hi @paria1420 , did you manage to reproduce this issue?