Connector Improvement: ServiceNow connector - Include display values for 'choice' and 'reference' fields
CompletedPlease include the option to de-normalize choice and reference fields ingested from ServiceNow so that 'display values' are made available for consumers.
ServiceNow stores data in a format where foreign keys provide a reference between tables - for example the 'Caller' field on the 'Incident' table is a reference to the 'User' table. Only the key (sys_id) of the user is stored on the Incident table, but user name is what is displayed in the tool (UI). This display value is the expected format for anyone pulling Incident data.
Completing connectors provide the ability to de-normalize choice and reference fields with a simple configuration however, with the Fivetran connector - the onus is on the customers to build joins for each reference and choice field to make the Snowflake views consumable. This logic is consistent and available through sys_dictionary for example:
incident.caller_id is a reference to User table
...and on the User table, 'name' is identified as the 'display' value
Similar logic can be applied to return display values for choice fields (which are all stored on a common table).
These should be added to existing columns with a consistent prefix such as 'dv_'
-
Official comment
Hi all,
We support display values for ServiceNow tables in our dbt models. Please see our change log for more details. Link to ServiceNow transformations.
Thanks,
Frank
-
Hi,
Thanks for sending this request in. It's part of Fivetran's core principles that we offer normalized data where available. See our blog post on this for more details on why we normalize our data. Hope that helps.
Frank
Please sign in to leave a comment.
Comments
2 comments