Unnecessary `documentId` in config sync causing lots off diffs

[radoslavzeman]

Bug report

Describe the bug

After migrating to Strapi v5 and strapi-plugin-config-sync v3, the plugin started to export documentIds all over the configs.
The problem is that they are often changed, even tho nothing else changes in the config file and it's causing lots of diffs in git and it's hard to check the changes. The changes happen when more people are working on the same strapi/repo. But I'm not sure this is the only way.

Why are documentIds exported, what are they for in configs and why are they changing?

Steps to reproduce the behavior

Try to make some changes in config (e.g. in Configure View) and commit them on two different machines.

Expected behavior

Only real changes are reflected in config files. No documentIds are exported in config files.

Screenshots

For example, simple config file for EN locale:

But also config files witch loads of changed documentIds:

Code snippets

If applicable, add code samples to help explain your problem.

System

• Node.js version: 20.19.0
• NPM version: 10.8.1
• Strapi version: v5.18.0
• Plugin version: 3.1.2
• Database: PostgreSQL
• Operating system: macOS, Windows, Linux

Additional context

I know these are not exact reproduction steps, but it happens during standard development process when people are fetching new commits from master, making PRs etc.

[boazpoolman]

Hi @radoslavzeman,

Thank you for submitting this issue.

We need to do some research on the behavior of the documentId when it's imported / exported with this plugin.

My idea was that if we include the documentId in the config files that they can be the same on all environments. That's a huge plus. But it seems that there is some unexpected behavior, I will do some research on this and get back to you.