# Sync dataset not updating if changes are made

**URL:** <https://forum.seatable.com/t/sync-dataset-not-updating-if-changes-are-made/1033>\
**Category:** Common dataset\
**Created:** [February 1, 2022, 7:32am UTC](https://forum.seatable.com/t/sync-dataset-not-updating-if-changes-are-made/1033 "2022-02-01T07:32:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![htoolin](https://forum.seatable.com/letter_avatar_proxy/v4/letter/h/d9b06d/32.png) [@htoolin](https://forum.seatable.com/u/htoolin)\
**Post date:** [February 1, 2022, 7:32am UTC](https://forum.seatable.com/t/sync-dataset-not-updating-if-changes-are-made/1033/1 "2022-02-01T07:32:32Z")

</div>

Hello, I realize an issue with sync common dataset.

At my common data set, the leave duration is 0.5

 ![image](https://forum.seatable.io/uploads/default/original/2X/d/dc046f343f62a839f4904fd3cf4f4052d8c89b3c.png)

when i create a new table using common dataset, the values are correct. however, if i “accidentally” make change to leave duration from 0.5 to 1 as shown below.

 ![image](https://forum.seatable.io/uploads/default/original/2X/1/182a07af637f178fb84be99e1d8ce28dba5bbd38.png)

and when i manually sync the data again as shown below, the leave duration does not change back to 0.5

 ![image](https://forum.seatable.io/uploads/default/original/2X/d/d1adea9c4889c3b8ebafaaf3f67546b0f46c40f9.png)

---

<div class="post-metadata">

**Author:** ![rdb](https://forum.seatable.com/user_avatar/forum.seatable.com/rdb/32/1869_2.png) [@rdb](https://forum.seatable.com/u/rdb)\
**Post date:** [February 1, 2022, 8:43am UTC](https://forum.seatable.com/t/sync-dataset-not-updating-if-changes-are-made/1033/2 "2022-02-01T08:43:53Z")

</div>

This is not a bug, this is the intended design.

A common dataset (CDS) is only synced when the source table was changed. Before moving data around, the sync algorithm checks if there have been any changes since the last sync. This is a measure to save system resources. The sync process is resource-heavy.

In order to prevent imported columns from being accidently modified, please lock them using the column permissions.

---

<div class="post-metadata">

**Author:** ![htoolin](https://forum.seatable.com/letter_avatar_proxy/v4/letter/h/d9b06d/32.png) [@htoolin](https://forum.seatable.com/u/htoolin)\
**Post date:** [February 1, 2022, 9:15am UTC](https://forum.seatable.com/t/sync-dataset-not-updating-if-changes-are-made/1033/3 "2022-02-01T09:15:08Z")

</div>

Hello @rdb thanks for your explanation. I am using developer edition, so i guess i could not lock the columns…

---

<div class="post-metadata">

**Author:** ![rdb](https://forum.seatable.com/user_avatar/forum.seatable.com/rdb/32/1869_2.png) [@rdb](https://forum.seatable.com/u/rdb)\
**Post date:** [February 1, 2022, 10:12am UTC](https://forum.seatable.com/t/sync-dataset-not-updating-if-changes-are-made/1033/4 "2022-02-01T10:12:30Z")

</div>

Column permissions are part of the advanced permissions, so no, you cannot lock columns.

---

<div class="post-metadata">

**Author:** ![system](https://forum.seatable.com/uploads/default/original/1X/04603423fe81a46c321283663086c475429e8ccb.png) [@system](https://forum.seatable.com/u/system)\
**Post date:** [February 3, 2022, 10:12am UTC](https://forum.seatable.com/t/sync-dataset-not-updating-if-changes-are-made/1033/5 "2022-02-03T10:12:44Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.