Skip to content

Commit 8a773b6

Browse files
Update faq.md
1 parent a444d1d commit 8a773b6

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

src/protocols/faq.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -162,10 +162,11 @@ Blocking events within a [Source Schema](/docs/connections/sources/schema/) or [
162162

163163
Warehouse connectors don't use data type definitions for schema creation. The [data types](/docs/connections/storage/warehouses/schema/#data-types) for columns are inferred from the first event that comes in from the source.
164164

165-
### I've blocked events in my Schema Configuration why are they not showing up as blocked in my Source Schema?
166-
Within your [Schema Configuration](https://segment.com/docs/protocols/enforce/schema-configuration/) you'll notice there are two columns next to the Event Name titled Allowed and Blocked. If you've selected Omit Properties under Unplanned Properties/Traits then the Source Schema will only show a property as block if it is present when the whole event is blocked. This setting will only be enforced if the property is an unplanned name but not an unplanned value.
165+
### Why are unplanned properties not showing up as blocked in my Source Schema, even though I've set the Schema Configuration to omit them?
167166

168-
In order to show a blocked value for an property/trait within your Source Schema, you'll need to trigger a violaiton which can only be done using JSON Schema. Once you enforce your Schema Configuration to Omit Properties this will show as blocked.
167+
Within your [Source Schema](https://segment.com/docs/connections/sources/schema/), you'll notice two columns next to the Event Name column: Allowed and Blocked. If you've set the [Schema Configuration](https://segment.com/docs/protocols/enforce/schema-configuration/) to **Block Unplanned Events** and **Omit Properties** unplanned properties/traits, the Source Schema will only show a property/trait as blocked when the entire event is blocked because it’s unplanned and not part of the Tracking Plan, and the property was part of the event payload. This setting will only be enforced if the property is an unplanned name, not an unplanned value.
168+
169+
To show a blocked value for a property/trait within your Source Schema, you'll need to trigger a violation, which can only be done using JSON Schema. Once you enforce your Schema Configuration to Omit Properties, this will show as blocked.
169170

170171
See an example payload below:
171172

0 commit comments

Comments
 (0)