Comments
3 comments
-
@Bugmeister - Hmmm. The only solution I can think of is if you programmatically update the filter.scpf based on querying the extended properties.
-
Ok cool, that was at the back of my mind as well and is likely the way we'll go but it was worthwhile checking I wasn't overlooking something more obvious or easier. Thanks.
-
Normally we'd encourage grouping objects using schemas or via a naming convention that a single filter rule would capture. If you come up with a solution using extended properties, this might be something worth sharing with other users who have the same issue!
Add comment
Please sign in to leave a comment.
For some of our objects, they are automatically scripted in and kept up-to-date from another system, whereas the remainder of the objects are source-controlled manually via SSC.
The objects that are controlled by the non-SSC can have any schema/object name etc, however they all have a particular extended property set on them (and we have control to add more etc.).
At the moment I need to manually edit the SSC filters and filter out any of these objects based on their schema/name as new one come into the database.
Would be way easier if I could just filter out objects that have an extended property set against them.
Is there any out-of-the-box or workaround to achieve that in SSC?
Thanks
Peter