Hello,

I observed the following thing :

If for the Workflow of a Page, I modify the Unique Key of a Custom Field, the modification takes place in the _social_fields table.

Then if I edit this Page on the front-end (without changing the data) and finally I click on "Save".
Then there is only one change in the _social_fields_data table.
And this change is the value "id".

This means that at the time of saving the Page, EasySocial deletes the original line in _social_fields_data (corresponding to the Page), to recreate a new one (with a new "id" ).

I want to understand why EasySocial bothers to regenerate an new id ?
What's the point ? The field_id remains the same.

Because, even if I modify a Unique Key, the search for a Custom Field (front-end) works very well (even if the page has not been re-save). The field_id is the value used to identify a Custom Field.

Thank you,
Philippe

You can see captures in attachments.