# How Do I Edit a ClearCase Dynamic View Config Spec to Select Versions as of a Specific Build Date?

**URL:** <https://community.abs-consulting.com/t/how-do-i-edit-a-clearcase-dynamic-view-config-spec-to-select-versions-as-of-a-specific-build-date/862>\
**Category:** IBM Products\
**Created:** [February 3, 2025, 3:06pm UTC](https://community.abs-consulting.com/t/how-do-i-edit-a-clearcase-dynamic-view-config-spec-to-select-versions-as-of-a-specific-build-date/862 "2025-02-03T15:06:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ali](https://community.abs-consulting.com/user_avatar/community.abs-consulting.com/ali/32/512_2.png) [@ali](https://community.abs-consulting.com/u/ali)\
**Post date:** [February 3, 2025, 3:06pm UTC](https://community.abs-consulting.com/t/how-do-i-edit-a-clearcase-dynamic-view-config-spec-to-select-versions-as-of-a-specific-build-date/862/1 "2025-02-03T15:06:59Z")

</div>

Hey everyone,

I’m trying to configure my ClearCase dynamic view so that it only selects versions as they existed at a specific build date. I want to ensure that my view reflects the exact state of the repository at that point in time.

How can I modify my config spec to achieve this? Any help would be appreciated!

---

<div class="post-metadata">

**Author:** ![sue](https://community.abs-consulting.com/user_avatar/community.abs-consulting.com/sue/32/507_2.png) [@sue](https://community.abs-consulting.com/u/sue)\
**Post date:** [February 3, 2025, 5:25pm UTC](https://community.abs-consulting.com/t/how-do-i-edit-a-clearcase-dynamic-view-config-spec-to-select-versions-as-of-a-specific-build-date/862/2 "2025-02-03T17:25:10Z")

</div>

You can use the `-time` rule in your config spec to achieve this. Here’s an example of how you can structure it:

```auto
element * CHECKEDOUT  
element * /main/LATEST -time "31-Jan-2025 12:00:00"  
element * /main/0  

```

The key part is `-time "31-Jan-2025 12:00:00"`, which ensures that your view only includes the versions that existed at that exact time.

---

<div class="post-metadata">

**Author:** ![ali](https://community.abs-consulting.com/user_avatar/community.abs-consulting.com/ali/32/512_2.png) [@ali](https://community.abs-consulting.com/u/ali)\
**Post date:** [February 3, 2025, 7:13pm UTC](https://community.abs-consulting.com/t/how-do-i-edit-a-clearcase-dynamic-view-config-spec-to-select-versions-as-of-a-specific-build-date/862/3 "2025-02-03T19:13:00Z")

</div>

That worked great.

Quick follow-up, how can I extend this to include feature branches that come off the main branch while still sticking to a specific build date?

---

<div class="post-metadata">

**Author:** ![sue](https://community.abs-consulting.com/user_avatar/community.abs-consulting.com/sue/32/507_2.png) [@sue](https://community.abs-consulting.com/u/sue)\
**Post date:** [February 3, 2025, 10:02pm UTC](https://community.abs-consulting.com/t/how-do-i-edit-a-clearcase-dynamic-view-config-spec-to-select-versions-as-of-a-specific-build-date/862/4 "2025-02-03T22:02:16Z")

</div>

To include feature branches that originate from the `main` branch, you need to reference those branches explicitly while maintaining the `-time` restriction. Here’s how you can modify your config spec:

```auto
element * CHECKEDOUT  
element * /main/LATEST -time "31-Jan-2025 12:00:00"  
element * /main/feature_branch/LATEST -time "31-Jan-2025 12:00:00"  
element * /main/0  

```

This setup ensures that you’re pulling in versions from both `main` and the `feature_branch` as they existed at the specified timestamp. If you have multiple feature branches off `main`, just duplicate the third line for each branch.
